Skip to main content
Glama
anluin

Colab MCP

by anluin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Colab MCP

No user-submitted related servers found.

    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

    • Colab MCP

      KumarDev7
      F
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol server that enables users to control and interact with Google Colab instances via a reverse proxy. It supports executing shell commands, running persistent Python code, and monitoring system resources like CPU, GPU, and RAM.
      -

    • 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.
      -

    • 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
    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

    B3.2/5.0

    Scored across 35 tools

    Disambiguation3/5

    Many tools address similar operations (e.g., colab_execute, colab_run_command, colab_process_start; colab_stop vs colab_pause_notebook), though the detailed descriptions help clarify boundaries. Some tools are compatibility aliases (colab_upload/download), adding redundant surface. Overall, the distinctions are present but subtle, requiring careful reading.

    Naming Consistency4/5

    Most tools follow a consistent colab_<action>_<object> pattern using snake_case, such as colab_create_notebook, colab_fs_read, and colab_transfer_upload. A few are nouns like colab_health and colab_sessions, which breaks the strict verb-noun convention but remains predictable.

    Tool Count2/5

    With 35 tools, the server exceeds the recommended range for a well-scoped MCP, and many operations (process, file, transfer, notebook) overlap in conceptual functionality. While the domain is broad, this many tools creates unnecessary complexity, and some compatibility aliases could be removed.

    Completeness4/5

    The tool set covers the full lifecycle of notebook execution, file management, process management, and data transfers, including edge-case handling for retries and idempotency. Minor gaps exist, such as no explicit notebook deletion or versioning, but most workflows are supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources