Lambda Labs MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.36.4Updated Nov 7, 2026

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

The publisher's own server: Ably MCP by usefulapi

VerifiedStreamable HTTPWeb executableCloud & Infrastructure Security & Monitoring

Server details

Identifier: io.usefulapi/lambda-labs
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to usefulapi.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.usefulapi%2Flambda-labs.svg)](https://sourceweft.com/mcp/io.usefulapi%2Flambda-labs?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted MCP server for Lambda Labs GPU cloud: inspect instances, types, images, filesystems and firewall rules, and launch or terminate instances.

What you can do: List and inspect GPU instances, instance types with pricing and capacity, images, filesystems, firewall rules and rulesets, and audit events
Launch, restart, terminate and rename/tag instances
Create and delete persistent filesystems
Check monthly tool-call usage, request a missing feature, and upgrade or cancel the paid plan
When to use it: Useful when you want an assistant to check what GPU capacity is running or available on Lambda Labs, review account activity, or start and stop instances without opening the dashboard.
Requirements: Remote endpoint over streamable HTTP; no local install. Sign-in uses OAuth, and the login page asks for a Lambda Cloud API key from the Lambda Cloud dashboard, which is stored per user. No API key or Authorization header goes in the client config. Free plan allows 50 tool calls per month.

Before you install

Write tools change real cloud resources: launching instances starts hourly billing immediately, restarting keeps billing running, terminating is irreversible and destroys non-persistent data, and deleting a filesystem destroys all data on it. The server stores your Lambda Cloud API key per user. Paid plans (Pro, Pro+) are billed through a Stripe checkout link, and cancellation gives no refund for the current period.

Installation

In SourceWeft

Open Lambda Labs MCP by usefulapi in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Flambda-labs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lambda-labs-by-usefulapi": {
      "type": "http",
      "url": "https://lambda-labs.usefulapi.io/mcp"
    }
  }
}

README

Lambda Labs MCP by usefulapi

Use your Lambda Labs account from Claude, Cursor, or any MCP client — read GPU instances, instance types, images, filesystems and firewall rules, and launch or terminate instances. Hosted, no local install: connect with your own credentials.

Live endpoint: https://lambda-labs.usefulapi.io/mcp · Homepage: https://usefulapi.io

Connect

Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://lambda-labs.usefulapi.io/mcp.
Claude Code: claude mcp add --transport http lambda-labs https://lambda-labs.usefulapi.io/mcp, then run /mcp to log in.
VS Code: Add to VS Code.
Cursor and other clients: add the URL as a remote MCP server:

json

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

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

Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Lambda Labs credentials.

Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/lambda-labs/

On first connect you'll provide your Lambda Cloud API key (Lambda Cloud dashboard → API keys). It is validated, stored per-user, and scoped to you — no keys in config files.

Tools

Tool	Type	What it does
`lambda_list_instances`	read	List instances
`lambda_get_instance`	read	Get instance
`lambda_list_instance_types`	read	List instance types
`lambda_list_images`	read	List images
`lambda_list_filesystems`	read	List filesystems
`lambda_list_firewall_rules`	read	List firewall rules
`lambda_list_firewall_rulesets`	read	List firewall rulesets
`lambda_get_firewall_ruleset`	read	Get firewall ruleset
`lambda_list_audit_events`	read	List audit events
`lambda_launch_instance`	write	Launch instance
`lambda_restart_instances`	write	Restart instances
`lambda_terminate_instances`	write	Terminate instances
`lambda_update_instance`	write	Update instance
`lambda_create_filesystem`	write	Create filesystem
`lambda_delete_filesystem`	write	Delete filesystem
`lambda_labs_usage_status`	meta	Usage status (free-tier meter)
`lambda_labs_request_feature`	meta	Request a missing feature
`lambda_labs_upgrade`	meta	Upgrade to Pro or Pro+
`lambda_labs_cancel_subscription`	meta	Cancel the Pro subscription

read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.

Pricing

*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].

Pro covers this server only. Subscribe with lambda_labs_upgrade (it returns a Stripe Checkout link). Cancel any time with lambda_labs_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running lambda_labs_upgrade before then undoes the cancel. Or write to [email protected].

License

MIT — see LICENSE. Documentation only; the server is hosted.

Source: servers/lambda-labs/README.md at commit 4046075

Tools

lambda_list_instances

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.

Takes no parameters.

lambda_get_instance

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

Parametersidrequired

lambda_list_instance_types

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.

Takes no parameters.

lambda_list_images

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.

Takes no parameters.

lambda_list_filesystems

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.

Takes no parameters.

lambda_list_firewall_rules

List firewall rules

List the account's inbound firewall rules (protocol, port range, source CIDR, description). Lambda Cloud REST: GET /api/v1/firewall-rules.

Takes no parameters.

lambda_list_firewall_rulesets

List firewall rulesets

List firewall rulesets (id, name, region, rules) that can be applied to instances. Lambda Cloud REST: GET /api/v1/firewall-rulesets.

Takes no parameters.

lambda_get_firewall_ruleset

Get firewall ruleset

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

Parametersidrequired

lambda_list_audit_events

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.

Parametersendstartpage_tokenresource_type

lambda_launch_instance

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.

Parametersnametagshostnameimage_idquantityuser_dataregion_namerequiredimage_familyssh_key_namesrequiredfile_system_namesinstance_type_namerequired

lambda_restart_instances

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.

Parametersinstance_idsrequired

lambda_terminate_instances

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.

Parametersinstance_idsrequired

lambda_update_instance

Update instance

Update a live instance's name and/or tags. Only provided fields are changed. Lambda Cloud REST: POST /api/v1/instances/{id}.

Parametersidrequirednametags

lambda_create_filesystem

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.

Parametersnamerequiredregionrequired

lambda_delete_filesystem

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

Parametersidrequired

Version history

v1.36.4LatestNov 7, 2026
v1.35.3Nov 5, 2026
v1.35.2Nov 5, 2026
v1.35.1Nov 4, 2026
v1.35.0Nov 3, 2026
v1.34.1Nov 3, 2026
v1.33.0Nov 1, 2026
v1.31.0Oct 31, 2026
v1.30.0Oct 31, 2026
v1.29.2Oct 30, 2026
v1.29.0Oct 30, 2026
v1.24.0Oct 26, 2026
v1.21.3Oct 25, 2026
v1.21.0Oct 25, 2026
v1.20.0Oct 24, 2026
v1.17.0Oct 23, 2026
v1.16.4Oct 22, 2026
v1.16.3Oct 21, 2026
v1.11.1Oct 9, 2026
v1.10.0Oct 9, 2026
v1.0.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts