Colab Compute MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COLAB_MCP_MAX_VMS | No | Maximum concurrent Colab VMs in the pool. | 2 |
| COLAB_MCP_STATE_DIR | No | Private socket, SSH key, and session state directory. | ~/.colab-compute-mcp |
| COLAB_MCP_MAX_JOBS_PER_CPU_VM | No | Concurrent jobs per `cpu` VM. | 2 |
| COLAB_MCP_IDLE_TIMEOUT_SECONDS | No | Idle VM auto-stop timeout (10 min). | 600 |
| COLAB_MCP_MAX_JOBS_PER_HIGH_MEM_VM | No | Concurrent jobs per `cpu-high-mem` VM. | 4 |
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 |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| colab_run_jobA | Build or test on a shared Colab VM. Defaults to CPU, syncing an absolute local workspace, and waiting up to 300 seconds. Async returns a job ID. cwd and artifactPaths are workspace-relative. |
| colab_job_statusB | Get one of this client's Colab jobs, including its state, exit code, log tails, and artifacts. |
| colab_cancel_jobA | Cancel one of this client's queued or running Colab jobs. |
| colab_pool_statusA | List shared Colab VMs, available slots, queued jobs, and the compute-unit balance. |
| colab_pool_stopA | Stop idle VMs, optionally by session name. Force can also cancel this client's jobs on selected VMs. |
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 5 tools
The tools mostly target distinct concepts: pool status/stopping versus job run/status/cancel. There is some overlap because colab_pool_stop can force-cancel this client's jobs on selected VMs, which touches the same operation space as colab_cancel_job, but the descriptions make the intended boundaries reasonably clear.
All names use a consistent colab_ prefix and snake_case, which is readable and predictable. However, the patterns mix resource_action (pool_status, pool_stop, job_status) with action_resource (run_job, cancel_job), so it is not a single uniform verb_noun convention throughout.
Five tools is well-scoped for a Colab compute server: pool visibility/management and job execution lifecycle are covered without excessive surface area. Each tool earns its place and there is no obvious padding.
The set covers the core lifecycle: inspect pool, stop idle VMs, run jobs, check job status, and cancel jobs. Minor gaps exist, such as no explicit tool to list all of the client's jobs or manage artifacts beyond status reporting, but agents can work around these using returned job IDs and status details.