All supported MCP clients use the same JSON configuration block to describe theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/googlecolab/colab-mcp/llms.txt
Use this file to discover all available pages before exploring further.
colab-mcp server, but the file path and the mechanism for loading that file differ between clients. The sections below walk through the exact steps for each supported client.
- Gemini CLI
- Claude Code
- Windsurf
Gemini CLI reads MCP server definitions from Googlers: If your environment points to a non-standard default PyPI index,
~/.gemini/settings.json for user-wide configuration, or from a project-level mcp.json file in the current working directory.Add the following block to whichever file you prefer:uvx may fail to resolve the package. Add "--index" and "https://pypi.org/simple" to the args array to force resolution against the public index:The
timeout: 30000 value (30 seconds) is intentional and important. When an MCP client first starts colab-mcp, the server process must launch, open a local WebSocket port, and wait for you to open the Colab notebook in your browser and establish the browser-side connection. This handshake can take several seconds, and a shorter timeout may cause the client to give up before the connection is fully established.Local development config
If you have cloned thecolab-mcp repository locally and want to run directly from source (for example, to test a change), use uv run instead of uvx:
/path/to/github/colab-mcp with the absolute path to your local clone. The cwd field tells the client where to invoke uv run so it picks up the project’s pyproject.toml and virtual environment.