What problem does it solve? Setting up and maintaining a persistent Jupyter kernel connection for an AI agent is error-prone: kernels die after laptop sleep, symlinks break across machines, and stale connection files crash MCP servers silently. This Skill documents the installation, registration, and recovery procedures for a lightweight stdio MCP server that speaks the Jupyter wire protocol over ZMQ with no HTTP or open ports. ## Core Features & Use Cases - Kernel lifecycle tools: start_kernel, connect_to_kernel, list_kernels, restart_kernel, and run_python let an agent execute code in persistent Python or R kernels. - Attach to existing kernels: Connect to whichever kernel VS Code or JupyterLab is already running by passing a connection file path or grabbing the newest one. - Sleep/drop recovery: Reconnect to a surviving kernel process after lid-close sleep instead of losing in-memory state by relaunching. - Use Case: On a new Linux machine, stow the agents dotfiles package, symlink the script onto $PATH, register the MCP server, then have the agent start a py_general kernel and verify it with run_python. ## Quick Start Ask the agent to start a py_general Jupyter kernel and verify the connection by running a quick Python snippet that prints the interpreter path.