Lambda Labs MCP by usefulapi

Reviewed 26m ago.

• tools: 15 tools scanned
• metadata: scanned

No findings.

Tools (15)

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