Skip to main content
Glama
Sign In
SEN-Adarsh

colab-mcp

by SEN-Adarsh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to colab-mcp

No user-submitted related servers found.

    Related Servers

    • colab-mcp by googlecolab

      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,357
      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

      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.
      9
      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
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: opening a new connection, retrieving connection metadata, and reconnecting a previous session. No overlap exists, as the actions are complementary and easily distinguishable.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (open, get, reconnect) with snake_case, maintaining a uniform and predictable structure throughout the set.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to connection management, and each tool is essential for that purpose. This is well within the ideal range for a focused server.

    Completeness4/5

    The surface covers the core connection workflow (open, info, reconnect) but lacks an explicit close/disconnect tool. However, this is a minor gap that does not break the primary use case of establishing and resuming connections.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources