colab-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 targets a distinct action: connection setup, adding code/text cells, reading cells, running code, updating, deleting, moving cells, and changing runtime. There is no overlap in purpose, and the descriptions clearly differentiate these operations.
All tool names follow a consistent verb_noun snake_case pattern (e.g., add_code_cell, get_cells, delete_cell). The naming is uniform and predictable, making it easy to infer each tool's function.
With 9 tools, the server is well-scoped for Colab notebook management. Each tool covers a necessary operation without redundancy, making the count appropriate for its purpose.
The tool set covers the full lifecycle of notebook editing: connecting, adding cells, reading state, executing, updating, deleting, moving, and changing runtime. There are no obvious missing operations for the stated purpose.