Main
Start with the uvx quick-start and a single notebook: validate
list_files+ a simple cell execution before adding more tools.Use the built-in observability hooks (README mentions OpenTelemetry) when you need reproducible traces for notebook runs and tool calls.
Keep tokens under control by asking the agent to cite specific cells (README documents prompts/tools) instead of pasting full notebooks into chat.
Source-backed notes
- README documents uvx and Docker client configuration for MCP, and notes a breaking change requiring
MCP_TOKENin v1.0.0+. - README lists notebook tools (file/kernels/cell execution) and mentions multimodal outputs (plots/images/text).
- README highlights built-in observability via hooks + OpenTelemetry integration for tracing tool calls and kernel execution.
FAQ
- Do I need Docker to use it?: No — README provides a uvx quick start; Docker is recommended for production isolation.
- What do I need to configure first?: A running Jupyter server + your MCP client config (JUPYTER_URL/TOKEN); README also notes
MCP_TOKENfor newer versions. - Does it support tracing?: Yes — README mentions OpenTelemetry hooks for notebook/tool execution traces.