Lambda Labs MCP by usefulapi
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate…
- Runs
- Remotely
- Version
- 1.40.0
- Listing updated
- 4 days ago
About Lambda Labs MCP by usefulapi
Lambda Labs MCP by usefulapi is an MCP server for cloud and infrastructure. It runs as a hosted remote server, so there is nothing to install locally.
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
Install
Run in a terminal
claude mcp add --transport http lambda-labs https://lambda-labs.usefulapi.io/mcpAdd to Settings → Connectors → Add custom connector
https://lambda-labs.usefulapi.io/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"lambda-labs": {
"url": "https://lambda-labs.usefulapi.io/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"lambda-labs": {
"type": "http",
"url": "https://lambda-labs.usefulapi.io/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"lambda-labs": {
"serverUrl": "https://lambda-labs.usefulapi.io/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"lambda-labs": {
"type": "http",
"url": "https://lambda-labs.usefulapi.io/mcp"
}
}
}Tools this server provides (15)
Read directly from the server.
- lambda_list_instances
- List your running GPU cloud instances (id, name, ip, status, region, instance_type, ssh_key_names, filesystems, jupyter_url). Lambda Cloud REST: GET /api/v1/instances.
- lambda_get_instance
- Get full details of a single instance by id (status, ip, region, instance_type, ssh/filesystem attachments, jupyter url, available actions). Lambda Cloud REST: GET /api/v1/instances/{id}.
- lambda_list_instance_types
- List all GPU instance types with their specs (vcpus, memory, storage, gpus), hourly price (price_cents_per_hour), and which regions currently have capacity available. Use this to pick region_name + instance_type_name before launching. Lambda Cloud REST: GET /api/v1/instance-types.
- lambda_list_images
- List available machine images (id, name, family, version, region availability) that can be selected when launching an instance. Lambda Cloud REST: GET /api/v1/images.
- lambda_list_filesystems
- List your persistent filesystems (id, name, region, status, created_at) that can be attached to instances at launch. Lambda Cloud REST: GET /api/v1/file-systems.
- lambda_list_firewall_rules
- List the account's inbound firewall rules (protocol, port range, source CIDR, description). Lambda Cloud REST: GET /api/v1/firewall-rules.
- lambda_list_firewall_rulesets
- List firewall rulesets (id, name, region, rules) that can be applied to instances. Lambda Cloud REST: GET /api/v1/firewall-rulesets.
- lambda_get_firewall_ruleset
- Get a single firewall ruleset by id. Lambda Cloud REST: GET /api/v1/firewall-rulesets/{id}.
- lambda_list_audit_events
- List account audit-log events, optionally filtered by time window and resource type, with page_token pagination. Lambda Cloud REST: GET /api/v1/audit-events.
- lambda_launch_instance
- Launch one or more GPU cloud instances. COSTS MONEY: billing starts as soon as the instance boots (hourly rate per instance_type). Pick region_name + instance_type_name from lambda_list_instance_types (only regions with capacity available), and pass exactly one existing SSH key name in ssh_key_names (create keys in the Lambda dashboard). Lambda Cloud REST: POST /api/v1/instance-operations/launch.
- lambda_restart_instances
- Restart one or more running instances by id (a reboot — the instances are NOT destroyed and billing continues). Lambda Cloud REST: POST /api/v1/instance-operations/restart.
- lambda_terminate_instances
- Terminate (permanently destroy) one or more instances by id. This STOPS billing for them but DESTROYS the instances and any non-persistent data — persistent filesystems survive. Irreversible. Lambda Cloud REST: POST /api/v1/instance-operations/terminate.
- lambda_update_instance
- Update a live instance's name and/or tags. Only provided fields are changed. Lambda Cloud REST: POST /api/v1/instances/{id}.
- lambda_create_filesystem
- Create a new persistent filesystem in a region (can then be attached to instances at launch). Lambda Cloud REST: POST /api/v1/filesystems.
- lambda_delete_filesystem
- Delete a persistent filesystem by id. Irreversible — DESTROYS all data on it. The filesystem must not be attached to any instance. Lambda Cloud REST: DELETE /api/v1/filesystems/{id}.
Lambda Labs MCP by usefulapi FAQ
How do I add Lambda Labs MCP by usefulapi to Claude Code?
Run this command in your terminal: claude mcp add --transport http lambda-labs https://lambda-labs.usefulapi.io/mcp
What are the best alternatives to Lambda Labs MCP by usefulapi?
The closest alternatives to Lambda Labs MCP by usefulapi are Agent Yurt, Proofline, filex, MagicWP MCP and Kubana Cloud Domains.
Alternatives to Lambda Labs MCP by usefulapi

Agent Yurt
MCP serverBack up agent memory, files and dashboards, then recover from a reviewed snapshot
Not checked yet- Remote
- Free
- Knowledge and memory

Proofline
MCP serverProduction-aware review of changes against your AWS or Google Cloud setup, via MCP
- Remote
- Freemium
- Developer tools

filex
MCP serverSelf-hosted file manager in one Go binary with a built-in MCP server for agents
Not checked yet- Remote
- Open source
- Files and documents

MagicWP MCP
MCP serverRun WordPress hosting from an assistant: backups, staging, updates, PHP and domains
- Remote
- Free trial
- Cloud and infrastructure

Kubana Cloud Domains
MCP serverSearch, register and renew domains and set nameservers at Kubana Cloud from an assistant
Not checked yet- 3 tools
- Remote
- Paid
- Cloud and infrastructure

Kubana Cloud DNS Management
MCP serverCreate DNS zones, edit records and check nameserver delegation on Kubana Cloud
Not checked yet- 5 tools
- Remote
- Free
- Cloud and infrastructure