colab-mcpofficial
A
licenseA
qualityD
maintenanceBridges a local agent to a Colab session in the browser, enabling seamless interaction with Colab from local clients.
1
987
Apache 2.0
colab-mcp (enhanced fork)
Related Servers
Alternatives to colab-mcp (enhanced fork)
Related Servers
- AlicenseBqualityDmaintenanceLocal-first MCP server for controlling Google Colab as a development, shell, file, and training runtime, with tools for notebook editing, GPU acceleration, and file transfer.598Apache 2.0
- AlicenseAqualityCmaintenanceEnables MCP-compatible AI assistants to run Python code on Google Colab GPU/TPU runtimes, supporting accelerators like T4, A100, H100, with background execution and Google Drive integration.103MIT
- AlicenseNot gradedqualityCmaintenanceEnables offloading heavy CPU/ML workloads to free Google Colab from any MCP client, with automatic job management and free-tier enforcement.17MIT
- AlicenseAqualityFmaintenanceMCP server that allocates Google Colab GPU runtimes (T4/L4) and executes Python code on them. Lets any MCP-compatible AI assistant run GPU-accelerated code without local GPU hardware.39MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP clients to execute Python code on Google Colab GPU/TPU runtimes via the official Colab CLI, with session, file, and package management capabilities.-
- FlicenseNot gradedqualityBmaintenanceEnables persistent execution of Python and shell commands on Google Colab's cloud GPU via a single background daemon, offering a web dashboard and REST API for AI agents without opening new tabs.-
TDQS
A3.7/5.0
Scored across 9 tools
Disambiguation5/5
Each tool has a clear and distinct purpose, targeting specific actions like adding, deleting, moving, or running cells, with no overlapping functionality. The consistent requirement for an active browser connection via open_colab_browser_connection further clarifies dependencies.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case (e.g., add_code_cell, get_cells, run_code_cell), making it easy for an agent to infer functionality from the name.
Tool Count5/5
With 9 tools, the server is well-scoped for its purpose of managing Google Colab notebooks. It covers essential operations without being overwhelming or too minimal.
Completeness4/5
The tool set covers core notebook interactions: connection, cell CRUD, execution, and runtime changes. Minor gaps exist, such as missing functions to clear output or restart the kernel, but the surface is sufficient for most workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues