Lambda Labs MCP by usefulapi
io.usefulapi/lambda-labs · v1.11.1
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.
MCPremoteno credentialsImages, video & audio
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 15 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 15 tools · 9 read, 6 write (incl. delete/pay)
Test call lambda_list_instances: needs a key: HTTP 401 (1,002 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://lambda-labs.usefulapi.io/mcpTools
15 tools listed at last check
lambda_list_instancesList 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_instanceGet 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_typesList 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_imagesList 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_filesystemsList 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_rulesList the account's inbound firewall rules (protocol, port range, source CIDR, description). Lambda Cloud REST: GET /api/v1/firewall-rules.lambda_list_firewall_rulesetsList firewall rulesets (id, name, region, rules) that can be applied to instances. Lambda Cloud REST: GET /api/v1/firewall-rulesets.lambda_get_firewall_rulesetGet a single firewall ruleset by id. Lambda Cloud REST: GET /api/v1/firewall-rulesets/{id}.lambda_list_audit_eventsList 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_instanceLaunch 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_nameslambda_restart_instancesRestart 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_instancesTerminate (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_instanceUpdate a live instance's name and/or tags. Only provided fields are changed. Lambda Cloud REST: POST /api/v1/instances/{id}.lambda_create_filesystemCreate a new persistent filesystem in a region (can then be attached to instances at launch). Lambda Cloud REST: POST /api/v1/filesystems.lambda_delete_filesystemDelete 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}.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/io.usefulapi/lambda-labs)