CloudLab MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDLAB_API_URL | No | Override the API endpoint | https://www.emulab.net:43794 |
| CLOUDLAB_TOKEN_PATH | No | Custom path to your JWT token file. The server looks for your JWT token in these locations (in order): 1. Path specified in CLOUDLAB_TOKEN_PATH environment variable, 2. cloudlab.jwt in the project directory, 3. ~/Downloads/cloudlab.jwt |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_experimentsB | List all your CloudLab experiments |
| create_experimentC | Create a new CloudLab experiment from a profile |
| get_experimentB | Get detailed status of a specific experiment including node states |
| reboot_nodeC | Reboot a specific node in an experiment |
| reboot_all_nodesC | Reboot all nodes in an experiment |
| reload_nodeC | Reload/reimage a node with its disk image |
| powercycle_nodeB | Power cycle a node (hard reboot) |
| extend_experimentC | Extend the expiration time of an experiment |
| terminate_experimentA | Terminate an experiment (WARNING: destroys all data) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
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.
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.
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.
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.