Skip to main content
Glama
SebastianGilPinzon

colab-mcp (enhanced fork)

Related Servers

Alternatives to colab-mcp (enhanced fork)

  • A
    license
    A
    quality
    D
    maintenance
    Bridges a local agent to a Colab session in the browser, enabling seamless interaction with Colab from local clients.
    1
    1,357
    Apache 2.0

Related Servers

  • A
    license
    B
    quality
    D
    maintenance
    Local-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.
    59
    8
    Apache 2.0
  • A
    license
    A
    quality
    D
    maintenance
    Enables 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.
    10
    3
    MIT
  • A
    license
    B
    quality
    A
    maintenance
    Enables AI agents to drive Google Colab end to end through Google's official Colab CLI: creating and stopping GPU/TPU runtimes, executing code, editing local notebooks cell by cell, launching long background jobs, and uploading or downloading files and folders. Optionally adds opt-in Google Drive tools for signing in, managing project folders, and creating, editing or trashing notebooks, plus mounting Drive on the VM for large datasets.
    42
    45 PyPI
    4
    Apache 2.0
  • A
    license
    A
    quality
    D
    maintenance
    MCP 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.
    3
    9
    MIT
  • F
    license
    Not graded
    quality
    D
    maintenance
    Enables MCP clients to execute Python code on Google Colab GPU/TPU runtimes via the official Colab CLI, with session, file, and package management capabilities.
    -

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