Skip to main content

Getting Started

To use Jupyter MCP Server, you first need to decide which setup fits your needs:

This guide will help you set up a Jupyter MCP Server to connect your preferred MCP client to a JupyterLab instance.

The Jupyter MCP Server acts as a bridge between the MCP client and the JupyterLab server, allowing you to interact with Jupyter notebooks seamlessly.

You can customize the setup further based on your requirements. Refer to the server configuration for more details on the possible configurations.

Choosing Your Transport​

Jupyter MCP Server supports two types of transport to connect to your MCP client: STDIO and Streamable HTTP. Choose the one that best fits your needs.

For more details on the different transports, refer to the official MCP documentation here.

STDIO Transport​

Best for: Desktop applications, Docker deployments, single-user setups

  • ✅ Simple configuration
  • ✅ Works with most MCP clients (Claude Desktop, Cursor, Windsurf, VS Code)
  • ✅ No additional server ports needed
  • ❌ One client connection at a time

👉 Get started with STDIO Transport

Streamable HTTP Transport​

Best for: Web applications, multiple concurrent clients, production deployments

  • ✅ Multiple clients can connect simultaneously
  • ✅ Web-based access
  • ✅ Can run as Jupyter Server Extension (no separate MCP server process)
  • ❌ Requires opening network ports

If you choose Streamable HTTP transport, you can also choose to run the MCP server:

Code Sandbox Options​

Choose where notebook code runs. The MCP tools remain the same whichever backend you use; the provider-specific pages explain credentials and setup.

Code sandboxBest suited forSetup
Jupyter Server (local or remote)Standard JupyterLab and Jupyter Notebook serversJupyter Server documentation
JupyterHubMulti-user deployments with authentication and resource managementJupyterHub setup guide
DatalayerHosted Jupyter with collaboration and security featuresDatalayer documentation
KaggleKaggle interactive notebook runtimesKaggle documentation
MontySecure, in-process execution of lightweight Python snippetsMonty documentation
Google ColabGoogle Colab notebook runtimes (experimental)Google Colab documentation
ModalIsolated, on-demand cloud executionModal documentation
DaytonaCloud sandboxes with GPU and preemptible GPU capacityDaytona documentation
E2BSandboxes where each context is a Jupyter kernel with rich outputsE2B documentation
CoreWeaveContainers running on CoreWeave's GPU cloudCoreWeave documentation
CloudflareSandboxes reached through the sandbox bridge WorkerCloudflare documentation

With Jupyter Server, you can use STDIO, Streamable HTTP as a standalone server, or Streamable HTTP as a Jupyter Server extension.

Multi-User Deployments

If you're deploying for multiple users, see the Multi-User Documentation for architecture patterns and best practices.

MCP Client Configuration​

Once you've set up your MCP server, you need to configure your MCP client. Choose your client:

Next Steps​

After setting up your MCP server and client:

🔧 Explore Available Tools - Learn about the MCP tools for interacting with notebooks

📝 Use Prompts - Discover prompt features for citing and referencing notebooks

🔒 Secure Your Deployment - Review authentication and security best practices for token management and authentication

📚 Learn More - Check out the Resources section for tutorials, videos, and community content

Additional Resources​