mcpField
M
mcp-server-colab-exec

mcp-server-colab-exec

Local
github.com/pdwi2020Developer Tools9Updated 33w ago

About mcp-server-colab-exec

mcp-server-colab-exec lets MCP clients allocate Google Colab GPU runtimes and run Python code. It is for AI assistants that need CUDA, PyTorch, or TensorFlow execution without local GPU hardware.

Key features

  1. 01Run inline Python on Colab GPUs
  2. 02Execute workspace .py files
  3. 03Download generated artifacts
  4. 04Choose T4 or L4 accelerators

Use cases

  1. 01Run CUDA or PyTorch code remotely
  2. 02Execute a local script and inspect output and errors
  3. 03Train a model and download its weights

MCP support

The server exposes code execution tools to MCP clients and accesses Colab GPU runtimes through Google OAuth2.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"pdwi2020-mcp-server-colab-exec": {
"command": "uvx",
"args": [
"mcp-server-colab-exec"
]
}
}
}
Run commanduvx mcp-server-colab-exec

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypimcp-server-colab-exec0.1.0

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

mcp-server-colab-exec

MCP server that allocates Google Colab GPU runtimes (T4/L4) and executes Python code on them. Lets any MCP-compatible AI assistant — Claude Code, Claude Desktop, Gemini CLI, Cline, and others — run GPU-accelerated code (CUDA, PyTorch, TensorFlow) without local GPU hardware.

Prerequisites

  • Python 3.10+
  • A Google account with access to Google Colab
  • On first run, a browser window opens for OAuth2 consent. The token is cached at ~/.config/colab-exec/token.json for subsequent runs.

Installation

pip install mcp-server-colab-exec

Or run directly with uvx:

uvx mcp-server-colab-exec

Configuration

Claude Code

Add to your project's .mcp.json or ~/.claude/.mcp.json:

{
  "mcpServers": {
    "colab-exec": {
      "command": "mcp-server-colab-exec"
    }
  }
}

Or via the CLI:

claude mcp add colab-exec mcp-server-colab-exec
Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "colab-exec": {
      "command": "mcp-server-colab-exec"
    }
  }
}
Gemini CLI
gemini mcp add colab-exec -- mcp-server-colab-exec

Tools

colab_execute

Execute inline Python code on a Colab GPU runtime.

ParameterTypeDefaultDescription
codestring—Python code to execute (required)
acceleratorstring"T4"GPU type: "T4" (free) or "L4" (premium)
timeoutint300Max execution time in seconds

Returns JSON with per-cell output, errors, and stderr.

colab_execute_file

Execute a local .py file on a Colab GPU runtime.

ParameterTypeDefaultDescription
file_pathstring—Path to a local .py file (required)
acceleratorstring"T4"GPU type: "T4" (free) or "L4" (premium)
timeoutint300Max execution time in seconds

Security policy: file_path must be a .py file inside the current workspace (cwd).

colab_execute_notebook

Execute code and collect all generated artifacts (images, CSVs, models, etc.).

ParameterTypeDefaultDescription
codestring—Python code to execute (required)
output_dirstring—Local directory for downloaded artifacts (required)
acceleratorstring"T4"GPU type: "T4" (free) or "L4" (premium)
timeoutint300Max execution time in seconds

Artifacts are downloaded as a zip and extracted into output_dir. Zip members are validated before extraction to prevent path traversal and special-file writes.

Examples

Check GPU availability:

colab_execute(code="import torch; print(torch.cuda.is_available()); print(torch.cuda.get_device_name(0))")

Run nvidia-smi:

colab_execute(code="import subprocess; print(subprocess.run(['nvidia-smi'], capture_output=True, text=True).stdout)")

Train a model and download weights:

colab_execute_notebook(
    code="import torch; model = torch.nn.Linear(10, 1); torch.save(model.state_dict(), '/tmp/model.pt')",
    output_dir="./outputs"
)

Authentication

On first use, the server opens a browser window for Google OAuth2 consent. The access token and refresh token are cached at ~/.config/colab-exec/token.json. Subsequent runs use the cached token and refresh it automatically.

The OAuth2 client credentials are the same ones used by the official Google Colab VS Code extension ([email protected]). They are intentionally public.

Troubleshooting

"GPU quota exceeded" — Colab has usage limits. Wait and retry, or use a different Google account.

"Timed out creating kernel session" — The runtime took too long to start. Retry — Colab sometimes has delays during peak usage.

"Authentication failed" — Delete ~/.config/colab-exec/token.json and re-authenticate.

OAuth browser window doesn't open — Ensure you're running in an environment with a browser. For headless servers, authenticate on a machine with a browser first and copy the token file.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.