Skip to main content
Glama

Related Servers

Alternatives to Colab Compute MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI coding assistants to consumer Google Colab so they can run Python code, execute full .ipynb notebooks, and capture plots and outputs on CPU, GPU (T4/L4/A100/H100), or TPU runtimes. It handles Google authentication, runtime provisioning and re-attachment, keep-alive heartbeats, and Jupyter kernel messaging without manual browser interaction.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to rent disposable cloud dev environments with a terminal, real browser, repo checkout, git gateway, and live view, so they can build, test, run dev servers, inspect pages, and push branches while keeping keys off the VM.
      1
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to run and manage machine-learning training on Kaggle, Google Colab, and Hugging Face GPUs. Supports background runs, status and metrics, plots, checkpoints, Kaggle submissions, and Hugging Face Hub operations.
      54
      MIT
    • A
      license
      B
      quality
      B
      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
      61 PyPI
      5
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation4/5

    The tools mostly target distinct concepts: pool status/stopping versus job run/status/cancel. There is some overlap because colab_pool_stop can force-cancel this client's jobs on selected VMs, which touches the same operation space as colab_cancel_job, but the descriptions make the intended boundaries reasonably clear.

    Naming Consistency4/5

    All names use a consistent colab_ prefix and snake_case, which is readable and predictable. However, the patterns mix resource_action (pool_status, pool_stop, job_status) with action_resource (run_job, cancel_job), so it is not a single uniform verb_noun convention throughout.

    Tool Count5/5

    Five tools is well-scoped for a Colab compute server: pool visibility/management and job execution lifecycle are covered without excessive surface area. Each tool earns its place and there is no obvious padding.

    Completeness4/5

    The set covers the core lifecycle: inspect pool, stop idle VMs, run jobs, check job status, and cancel jobs. Minor gaps exist, such as no explicit tool to list all of the client's jobs or manage artifacts beyond status reporting, but agents can work around these using returned job IDs and status details.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data