lambda-cloud-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAMBDA_API_KEY | Yes | Your Lambda Cloud API key | |
| LAMBDA_API_BASE_URL | No | Override base URL (default https://cloud.lambda.ai) | https://cloud.lambda.ai |
| LAMBDA_MCP_ALLOW_WRITE | No | Set to '1' to enable write tools (launch, restart, terminate). By default read-only. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_instance_typesA | List Lambda Cloud instance types with price (USD/hour), specs and the regions that have capacity right now. Sorted from cheapest. |
| cheapest_available_instanceA | Find the cheapest instance type that has capacity now. Filters: min_gpus, gpu_contains (e.g. "H100"), region (e.g. "us-east-1"), max_hourly_usd. Returns {"found": false} if nothing matches. |
| list_instancesA | List your running instances. |
| get_instanceB | Get details of one instance by id. |
| list_ssh_keysA | List SSH keys saved in your Lambda Cloud account. |
| list_file_systemsA | List your persistent file systems. |
| list_imagesB | List available machine images. |
| list_regionsA | List Lambda Cloud regions. |
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 8 tools
The tools are mostly distinct, each targeting a different resource such as images, regions, instance types, running instances, SSH keys, or file systems. The only potential confusion is between list_instance_types and cheapest_available_instance, since the former already includes price and capacity data, but their intents are still reasonably clear.
Most tools follow a consistent list_<resource> or get_<resource> pattern, making the naming predictable. cheapest_available_instance breaks this verb-first convention and would be more consistent as find_cheapest_instance or get_cheapest_instance.
Eight tools is well within the ideal range for a focused cloud-inspection server, and each tool has a clear purpose. The count feels appropriately scoped without unnecessary redundancy.
The tool set is heavily read-only, covering listing and getting resources but lacking any create, update, or delete operations. For a Lambda Cloud management server, the absence of launch/terminate instance operations and SSH key or file system creation is a significant gap that would prevent agents from taking meaningful actions.