Skip to main content
Glama
amgallego8

Colab-MCP

by amgallego8
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Colab-MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • 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
    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.2/5.0

    Scored across 42 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and descriptions carefully distinguish near-pairs (colab_exec vs colab_run vs colab_job_start; colab_upload vs colab_upload_dir). Some boundary blur remains between session-inspection tools (colab_sessions, colab_status, colab_runtime_info) and between colab_new and colab_ensure_session, but guidance is generally clear.

    Naming Consistency4/5

    All tools share the colab_ prefix and snake_case, with clear resource-grouping (colab_notebook_*, colab_job_*, colab_drive_*). Minor deviation: a mix of noun-style (colab_sessions, colab_status) and verb-style (colab_new, colab_stop) names, and colab_new is less descriptive than its siblings.

    Tool Count2/5

    42 tools is well above the comfortable range for a single server. Although the domain is broad (sessions, exec, jobs, notebooks, files, Drive), the granular cell-level notebook surface (create, add/edit/delete/move/clear/run_cell/run_all/read/list/to_script) plus parallel file vs directory transfer tools inflate the count considerably.

    Completeness4/5

    Coverage is broad and lifecycle-complete: session create/ensure/status/stop, exec and one-shot runs, background jobs with status/logs/cancel/list, full notebook and cell CRUD, upload/download for files and directories, and Drive mount/status/project-dir. Minor gaps like no kernel interrupt (only restart) and no directory-delete operation are easy to work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources