Colab Exec MCP server
io.github.pdwi2020/mcp-server-colab-exec·v0.1.0·9 starsExecute Python code on Google Colab GPU runtimes (T4/L4) from any MCP client
9 stars39 downloads/wk
Reviews
Write oneNobody has reviewed Colab Exec yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Colab Exec tools (3, 3 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
colab_executewrite actionExecute Python code on a Google Colab GPU runtime.
colab_execute_filewrite actionExecute a local Python file on a Google Colab GPU runtime.
colab_execute_notebookwrite actionExecute Python code on Colab GPU and collect generated artifacts.
Public scan report
scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it
- Code scan6 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 201 days ago4/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Colab Exec compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 75/100
- higher than 45% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 100%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 9
- more than 87% of 28,688 servers
- Downloads a week
- 39
- more than 30% of 12,191 servers with a package
What its tools let an agent do: 3 change
Install Colab Exec in Claude Code, Cursor or VS Code
claude mcp add mcp-server-colab-exec -- uvx mcp-server-colab-exec
What the publisher says
From the Colab Exec repository's README, as published. We do not edit it. Read it on GitHub
mcp-server-colab-exec
<!-- mcp-name: io.github.pdwi2020/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-execOr run directly with uvx:
uvx mcp-server-colab-execConfiguration
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-execClaude Desktop
Add to claudedesktopconfig.json:
{
"mcpServers": {
"colab-exec": {
"command": "mcp-server-colab-exec"
}
}
}Gemini CLI
gemini mcp add colab-exec -- mcp-server-colab-execTools
colab_execute
Execute inline Python code on a Colab GPU runtime.
Returns JSON with per-cell output, errors, and stderr.
colabexecutefile
Execute a local .py file on a Colab GPU runtime.
Security policy: file_path must be a .py file inside the current workspace (cwd).
colabexecutenotebook
Execute code and collect all generated artifacts (images, CSVs, models, etc.).
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.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Colab Exec: common questions
- Is Colab Exec MCP server safe?
- Mostly: it is graded B (75/100). Read the Colab Exec safety report
- How do I install Colab Exec?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Colab Exec need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Colab Exec maintained?
- The last commit was 238 days ago (2026-03-11). The latest release is v0.1.0.
- How does Colab Exec compare with other MCP servers?
- safety score 75/100 (higher than 45% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 100% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.