Skip to main content
Glama
ArdaGurcan

CloudLab MCP Server

by ArdaGurcan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to CloudLab MCP Server

No user-submitted related servers found.

    Related Servers

    • cloudlabMcp

      Raj708049
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables provisioning and managing CloudLab labs and sandboxes, including user creation, subscriptions, and automated lab launch workflows.
      -

    • MLflow MCP Server

      yesid-lopez
      A
      license
      C
      quality
      C
      maintenance
      Enables AI assistants to interact with MLflow experiments, runs, and registered models. Supports browsing experiments, retrieving run details with metrics and parameters, and querying the model registry through natural language.
      7
      MIT

    • GPU MCP

      wtrhacker
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to run policy-constrained Python jobs on lab NVIDIA GPU hosts, including GPU inspection, device reservation, job launching and monitoring, and owner-scoped process stopping.
      2
      -

    • Poiesis MCP Server

      JaeAeich
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to create, monitor, and manage computational tasks through GA4GH Task Execution Service (TES) functionality. Provides seamless access to TES-compliant services for executing bioinformatics and scientific computing workflows.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. The tools cover different actions on experiments (create, get, list, extend, terminate) and nodes (powercycle, reboot, reload), with clear boundaries between them. An agent can easily tell them apart based on their specific functions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern throughout. The verbs are clear and descriptive (e.g., create_experiment, reboot_node), and the nouns consistently specify the target resource (experiment or node). There are no deviations in style or convention.

    Tool Count5/5

    With 9 tools, the count is well-scoped for managing CloudLab experiments and nodes. Each tool earns its place by covering essential operations like lifecycle management (create, terminate), status retrieval (get, list), and node control (reboot, reload). This is neither too sparse nor overwhelming for the domain.

    Completeness4/5

    The tool set provides strong coverage for the CloudLab domain, including CRUD-like operations for experiments (create, get, list, terminate) and comprehensive node management (reboot, powercycle, reload). A minor gap is the lack of tools for modifying experiment configurations or profiles after creation, but agents can work around this by recreating experiments if needed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources