Skip to main content
Glama
404F0X

colab-mcp

by 404F0X
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to colab-mcp

No user-submitted related servers found.

    Related Servers

    • Colab MCP

      anluin
      A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol server that gives Codex and other MCP clients access to Google Colab runtimes—allowing session allocation, command execution, notebook management, file operations, and data transfers.
      35
      2
      Apache 2.0

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

    • 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

    B3/5.0

    Scored across 59 tools

    Disambiguation4/5

    Most tools have distinct purposes, but aliases like download_notebook/export_notebook and upload_notebook/import_notebook could confuse an agent. Additionally, multiple run cell tools (run_code_cell, run_code_cells, run_cell_range, run_all_cells) have overlapping functionality.

    Naming Consistency4/5

    Tool names consistently use snake_case, but the verb patterns vary (e.g., run_ vs. start_ vs. watch_). Aliases like download_notebook vs. export_notebook break the pattern slightly.

    Tool Count2/5

    59 tools is excessive for a Colab notebook server. The scope, though broad, could be covered with fewer tools by merging similar ones (e.g., file upload/download variants). This exceeds the 'too many' threshold of 25+.

    Completeness4/5

    The toolset covers notebook cell operations, runtime management, file handling, environment variables, GPU monitoring, and background commands. Minor gaps exist, such as a tool to list all notebooks or retrieve runtime metadata.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources