Skip to main content
Glama
Sign In
colab-mcp

colab-mcp

by mohammednuruddin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to colab-mcp

No user-submitted related servers found.

    Related Servers

    • colab-mcp

      kamalrana22
      A
      license
      A
      quality
      D
      maintenance
      Bridges a local AI agent to a Colab session in the browser, enabling code execution and file operations through the Model Context Protocol.
      2
      9
      Apache 2.0
    • colab-mcp

      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,429
      Apache 2.0

    • 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

    • colab-cli-mcp

      nmt3325
      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.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (connect, check status, outline, job list, cancel, upload, download, export). The only real overlap is the execution trio run_cells, run_notebook, and run_code — run_cells explicitly accepts 'all', which duplicates run_notebook — but the descriptions spell out the difference well enough for an agent to choose correctly.

    Naming Consistency4/5

    Nearly all names are snake_case and follow verb_noun (get_notebook_outline, run_cells, list_jobs, cancel_job, upload_file, download_file, export_notebook). Minor deviations: the status queries job_status and colab_connection_status are noun-only, and open_colab_browser_connection redundantly embeds 'colab' while its sibling tools do not.

    Tool Count5/5

    Twelve tools is a well-scoped set for remote Colab notebook control: connection handling, execution, job management, file transfer, and export each get a small number of dedicated tools. Nothing appears padded or redundant beyond the mild execution overlap.

    Completeness3/5

    Core run lifecycle (connect, inspect cells, execute, poll, cancel, transfer files, export) is covered with no dead ends. However, the notebook-editing tools that open_colab_browser_connection promises to 'unlock' are absent from the surface, and there is no way to insert, delete, or edit cell source or to disconnect a session — notable gaps for a notebook-control server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources