| name | jupyterlab-mcp-connector |
| description | MCP connector for JupyterLab – enables AI-powered notebook management, kernel operations, and interactive computing through Claude |
| license | BSD |
| tags | ["data","jupyter","mcp","notebook","science"] |
| difficulty | intermediate |
| time_to_master | 4-8 weeks |
| version | 1.0.0 |
Jupyterlab MCP Connector
Overview
This skill enables Claude to interact with Jupyterlab through the Model Context Protocol (MCP). It provides a bridge between Claude's AI capabilities and Jupyterlab's REST API, allowing natural language control of Jupyterlab operations, intelligent automation, and AI-powered assistance for Jupyterlab workflows.
When to Use This Skill
- Notebook creation and cell management via AI
- Kernel lifecycle and environment management
- Extension installation and configuration
- Terminal and file manager operations
- Notebook conversion and export
Architecture
┌─────────────┐ ┌─────────────────┐ ┌──────────────────┐
│ Claude │────▶│ MCP Server │────▶│ Jupyterlab │
│ (Client) │◀────│ (TypeScript) │◀────│ (REST API )│
└─────────────┘ └─────────────────┘ └──────────────────┘
Core Concepts
MCP Server Setup
The connector implements an MCP server that exposes Jupyterlab operations as tools Claude can invoke. The server translates natural language intentions into REST API calls.
Key Endpoints/Interfaces
/api/contents, /api/sessions, /api/kernels, /api/terminals, /api/nbconvert
Implementation
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";
const server = new McpServer({
name: "jupyterlab-mcp-connector",
version: "1.0.0",
});
server.tool(
"list_resources",
"List and query Jupyterlab resources with optional filters",
{
query: z.string().optional().describe("Search query or filter"),
limit: z.number().optional().describe("Max results to return"),
},
async ({ query, limit }) => {
const response = await fetch(`${BASE_URL}/api/contents`, {
headers: { "Authorization": `Bearer ${API_KEY}` },
});
const data = await response.json();
return {
: [{ : , : .(data, , ) }],
};
}
);
server.(
,
,
{
: z.().(),
: z.({}).().().(),
},
({ name, config }) => {
response = (, {
: ,
: {
: ,
: ,
},
: .({ name, ...config }),
});
data = response.();
{
: [{ : , : }],
};
}
);
server.(
,
,
{
: z.().(),
: z.().().(),
},
({ , timeframe }) => {
response = (, {
: { : },
});
data = response.();
{
: [{ : , : .(data, , ) }],
};
}
);
transport = ();
server.(transport);
Claude Desktop Configuration
{
"mcpServers": {
"jupyterlab-mcp-connector": {
"command": "node",
"args": ["path/to/jupyterlab-mcp-connector/index.js"],
"env": {
"JUPYTERLAB_API_KEY": "your-api-key",
"JUPYTERLAB_BASE_URL": "https://your-instance-url"
}
}
}
}
Best Practices
- Authentication: Store API keys securely using environment variables; never hardcode credentials
- Rate Limiting: Implement request throttling to respect Jupyterlab API rate limits
- Error Handling: Provide clear, actionable error messages for common failure scenarios
- Pagination: Handle paginated responses for large datasets efficiently
- Caching: Cache frequently accessed read-only data to reduce API calls
- Security: Validate all inputs before passing to the Jupyterlab API; sanitize outputs
- Logging: Log all API interactions for debugging and audit purposes
Example Prompts
"Create a new notebook with data loading, EDA, and model training sections with code templates"
Security Considerations
- All API credentials must be stored as environment variables
- Implement input validation and sanitization for all tool parameters
- Use HTTPS for all API communications
- Follow the principle of least privilege for API token permissions
- Audit log all write operations for compliance tracking
Resources
Changelog
| Version | Date | Changes |
|---|
| 1.0.0 | 2026-04-01 | Initial MCP connector skill |
Part of SkillGalaxy - 10,000+ comprehensive skills for AI-assisted development.
