A JupyterLab extension to manage MCP servers.
A JupyterLab extension to manage MCP servers. That is what the jupyter mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
This extension provides a user interface and backend infrastructure to configure and manage MCP servers directly within JupyterLab. It allows you to define which MCP servers are available for use by other JupyterLab extensions or AI assistants.
The Model Context Protocol (MCP) is an open standard that enables AI assistants and other clients to interact with various data sources, tools, and services through a unified interface. MCP servers expose resources, tools, and prompts that AI models can query and use during conversations.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
{
"mcpServers": {
"jupyter-2": {
"command": "uvx",
"args": ["jupyter_mcp_manager"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
The original Chromium automation reference server — simple, screenshot-driven browser control.
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.