Skip to main content
Glama
Sign In
Colab MCP Adapter

Colab MCP Adapter

by suniltnngl-gm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Colab MCP Adapter

No user-submitted related servers found.

    Related Servers

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

    • Colab-MCP

      amgallego8
      A
      license
      B
      quality
      A
      maintenance
      Enables AI agents to drive Google Colab end to end through Google's official Colab CLI: creating and stopping GPU/TPU runtimes, executing code, editing local notebooks cell by cell, launching long background jobs, and uploading or downloading files and folders. Optionally adds opt-in Google Drive tools for signing in, managing project folders, and creating, editing or trashing notebooks, plus mounting Drive on the VM for large datasets.
      42
      45 PyPI
      4
      Apache 2.0

    • colab-mcp

      mohammednuruddin
      A
      license
      B
      quality
      C
      maintenance
      Bridges a locally running coding agent to a Colab session in the browser, letting it inspect, edit, run, and export notebooks, execute ad-hoc Python, transfer files to and from the runtime, and poll or cancel background jobs.
      12
      Apache 2.0

    • 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
      9
      Apache 2.0
    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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Session lifecycle tools are clearly separated by action and target, and read-only helpers like get_url and log have distinct purposes. The only mild ambiguity is between code_execute and file_execute, which both execute Python in a session but differ by input form and are clarified in their descriptions.

    Naming Consistency4/5

    All tools use snake_case with a consistent colab_ prefix and mostly follow a resource_action pattern. Minor deviations exist: colab_session_log uses only a noun, and colab_session_get_url adds an extra noun to the usual pattern.

    Tool Count5/5

    Eight tools is well-scoped for a Colab session adapter, covering creation, listing, status, termination, execution, URL access, and logs without obvious padding. Each tool appears to earn its place in the surface.

    Completeness4/5

    The core session lifecycle and execution workflows are covered, including logs and browser URL access. Explicit file upload/download or notebook-file operations are absent, though agents can likely work around this by writing files through code_execute.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources