Lambda Labs MCP Server

io.usefulapi/lambda-labs

not responding

Lambda Labs is listed as active in the registry but did not answer our last check. It exposes 15 tools. Last commit 1 Aug 2026.

Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances.

Uptime history 41 hours of history · worst hour 0%

41 hours agonow

30.8%

Uptime 24h

28 of 91 checks

Tools

read from the server

171 ms

Response time

average over 24h

Stars

last commit 1 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add lambda-labs --transport http https://lambda-labs.usefulapi.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "lambda-labs": {
      "url": "https://lambda-labs.usefulapi.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.lambda-labs]
url = "https://lambda-labs.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "lambda-labs": {
      "url": "https://lambda-labs.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "lambda-labs": {
      "url": "https://lambda-labs.usefulapi.io/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

lambda

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_get_firewall_ruleset

Get a single firewall ruleset by id. Lambda Cloud REST: GET /api/v1/firewall-rulesets/{id}.

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_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_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_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_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_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_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_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}.

Endpoints

URL	Transport	State	Latency	Checked
https://lambda-labs.usefulapi.io/mcp	streamable-http	answering	54 ms	3 min ago

Lambda Labs — questions

Answers built from our own checks of this server.

What can Lambda Labs do?

It exposes 15 tools, read directly from the server on our last check. Among them: lambda_create_filesystem, lambda_delete_filesystem, lambda_get_firewall_ruleset, lambda_get_instance, lambda_launch_instance, lambda_list_audit_events and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Lambda Labs working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 28 of 91 checks got a reply (30.8%), average response time 171 ms. The bar chart above shows every period we have measured.

The registry lists Lambda Labs as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Lambda Labs?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Lambda Labs need an API key?

No. Lambda Labs completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Lambda Labs?

It answers our handshake in 171 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Lambda Labs open source?

Yes — it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.