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. Optionally pass notebook_url to connect to an existing notebook instead of a new scratch notebook. Returns a boolean representing whether the connection attempt succeeded |
| get_colab_connection_infoA | Returns this server's connection token, port and a ready-to-use connect URL for manually connecting a Colab notebook (eg via the Colab command palette) when opening a browser directly is not possible |
| reconnect_colab_sessionA | Re-opens the most recently used Colab notebook with the persisted session token and port, resuming the connection after this MCP server has restarted. Returns a boolean representing whether the reconnection succeeded |
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 3 tools
Each tool has a clearly distinct purpose: opening a new connection, retrieving connection metadata, and reconnecting a previous session. No overlap exists, as the actions are complementary and easily distinguishable.
All tool names follow a consistent verb_noun pattern (open, get, reconnect) with snake_case, maintaining a uniform and predictable structure throughout the set.
With only 3 tools, the server is tightly scoped to connection management, and each tool is essential for that purpose. This is well within the ideal range for a focused server.
The surface covers the core connection workflow (open, info, reconnect) but lacks an explicit close/disconnect tool. However, this is a minor gap that does not break the primary use case of establishing and resuming connections.