jupyterlab-collab-mcp-setup
Skill42 starsChanged 50 days agoNo licenceView on GitHub
Set up and verify the jupyterlab-collab-mcp MCP server so an agent can read/edit/execute Jupyter notebooks with real-time collaboration. Use when the user says 'connect to the jupyter MCP server', 'check the jupyterlab collab mcp', 'jlabx extensions aren't working', 'verify the MCP server is installed', the agent has no jupyter MCP tools despite expecting them, or notebook edits via MCP fail or return connection errors. THREE-LAYER architecture (opencode <-stdio-> MCP server <-y-websocket-> JupyterLab), three independent break points: (1) jlabx is a LAUNCHER, not the MCP server; (2) jupyter-collaboration must be installed in the SAME env JupyterLab runs from; (3) the MCP server must be registered in opencode.json mcp config (no auto-discovery; restart after changes). Verification: (a) 'jupyter server extension list' shows jupyter_server_ydoc enabled, (b) opencode.json has the jupyter entry, (c) the session actually has jupyter MCP tools. Full gotchas and the confirmed-working config in the body.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-md-improverSkill
- atomic-commitsSkill
- audit-before-rewriteSkill
- awesome-marimo-notebookSkill
- blog-explainer-prose-dedupSkill
- codebase-study-parallel-reportersSkill
- coherent-writingSkill
- cybersecurity-reviewSkill
- data-visualization-masterSkill
- debug-github-ciSkill
- design-driven-devSkill
- docker-offline-verificationSkill
- dom-anchored-svg-connectorsSkill
- epistemic-resourcefulnessSkill
- evident-chartsSkill
- gh-activity-summarySkill
- gh-cliSkill
- gh-pr-code-reviewSkill
- github-auto-merge-setupSkill
- git-rebase-noninteractive-editorSkill
- html-presentationsSkill
- large-file-edit-truncation-guardrailSkill
- marimo-notebook-patternsSkill
- marimoSkill
- mempalaceSkill
- ml-experimentationSkill
- motion-graphics-videoSkill
- npm-trusted-publishing-oidc-setupSkill
- obsidian-landing-pageSkill
- opencode-bash-background-process-survivalSkill
- opencode-mcp-server-setupSkill
- opencode-ollama-provider-setupSkill
- opencode-plugin-authoringSkill
- pdf-form-fillerSkill
- plaud-ingestionSkill
- prompt-cardSkill
- publish-to-google-docsSkill
- python-importtime-optimizationSkill
- remotion-videoSkill
- scientific-edaSkill
- skill-creatorSkill
- slack-cliSkill
- stacked-pr-decompositionSkill
- typewriter-videoSkill
- video-script-writingSkill
- voss-advisorSkill
- webfetch-empty-use-agent-browserSkill
- xarray-linked-dataSkill
- youtubeSkill
The file
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

