colab-mcp (enhanced fork)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLIENT_OAUTH_CONFIG | No | Path to OAuth client-secrets JSON file. Required for the change_runtime tool. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| open_colab_browser_connectionA | Opens a connection to a Google Colab browser session and unlocks notebook editing tools. Returns whether the connection attempt succeeded. |
| add_code_cellB | Add a new code cell to the Colab notebook. Requires an active browser connection via open_colab_browser_connection. |
| add_text_cellA | Add a new text/markdown cell to the Colab notebook. Requires an active browser connection via open_colab_browser_connection. |
| get_cellsA | Read the current notebook state: list of cells with their IDs, contents, and outputs. Essential for iterative work (write -> run -> read -> adjust). Requires an active browser connection via open_colab_browser_connection. |
| run_code_cellA | Execute a code cell in the Colab notebook by cellId (from add_code_cell or get_cells). Requires an active browser connection via open_colab_browser_connection. |
| update_cellB | Update the contents of an existing cell in the Colab notebook. Requires an active browser connection via open_colab_browser_connection. |
| delete_cellB | Delete a cell from the Colab notebook by cellId. Requires an active browser connection via open_colab_browser_connection. |
| move_cellA | Move a cell to a new position in the Colab notebook by cellId and target index. Requires an active browser connection via open_colab_browser_connection. |
| change_runtimeA | Change the Colab runtime to use a specific GPU accelerator. Valid values: NONE, T4, L4, A100. Requires OAuth setup (first time opens browser for consent). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a clear and distinct purpose, targeting specific actions like adding, deleting, moving, or running cells, with no overlapping functionality. The consistent requirement for an active browser connection via open_colab_browser_connection further clarifies dependencies.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_code_cell, get_cells, run_code_cell), making it easy for an agent to infer functionality from the name.
With 9 tools, the server is well-scoped for its purpose of managing Google Colab notebooks. It covers essential operations without being overwhelming or too minimal.
The tool set covers core notebook interactions: connection, cell CRUD, execution, and runtime changes. Minor gaps exist, such as missing functions to clear output or restart the kernel, but the surface is sufficient for most workflows.