Skip to main content
Glama
SebastianGilPinzon

colab-mcp (enhanced fork)

by SebastianGilPinzon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to colab-mcp (enhanced fork)

  • colab-mcp by googlecolab

    colab-mcpofficial

    googlecolab
    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,148
    Apache 2.0

Related Servers

  • colab-mcp

    404F0X
    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

  • mcp-colab-gpu

    mio-github
    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

  • mcp-server-colab-exec

    pdwi2020
    A
    license
    A
    quality
    F
    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

  • colab-cli-mcp

    nmt3325
    F
    license
    Not graded
    quality
    B
    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.
    -

  • Google Colab MCP Server

    MOT1209
    A
    license
    B
    quality
    C
    maintenance
    Lets any MCP-compatible agent use Google Colab or Jupyter runtimes as an execution backend, enabling code execution, notebook management, package installation, hardware introspection, training jobs, and file handling.
    40
    1
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

Resources