Can I use Lambda Labs as a CLI?

Yes. KosmoKrator exposes a Lambda Labs CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Lambda Labs through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Lambda Labs tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Lambda Labs credentials stored?

Lambda Labs credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Lambda Labs MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Lambda Labs CLI for AI Agents

Use the Lambda Labs CLI from KosmoKrator to call Lambda Labs tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Lambda Labs CLI Setup

Lambda Labs can be configured headlessly with `kosmokrator integrations:configure lambda-labs`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure lambda-labs --set api_key="$LAMBDA_LABS_API_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor lambda-labs --json
kosmokrator integrations:status --json

Credentials

Authentication type: API key api_key. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`api_key`	`LAMBDA_LABS_API_KEY`	Secret `secret`	yes	API Key
`url`	`LAMBDA_LABS_URL`	URL `url`	no	API Base URL

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call lambda-labs.lambda_labs_list_instances '{}' --json

Provider shortcut

kosmo integrations:lambda-labs lambda_labs_list_instances '{}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

kosmo integrations:docs lambda-labs --json
kosmo integrations:docs lambda-labs.lambda_labs_list_instances --json
kosmo integrations:schema lambda-labs.lambda_labs_list_instances --json
kosmo integrations:search "Lambda Labs" --json
kosmo integrations:list --json

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`lambda-labs.lambda_labs_list_instances`

List all GPU instances in the Lambda Labs account. Returns instance IDs, names, status, IP addresses, and GPU configuration.

Read read

Parameters: none

Generic call

kosmo integrations:call lambda-labs.lambda_labs_list_instances '{}' --json

Shortcut

kosmo integrations:lambda-labs lambda_labs_list_instances '{}' --json

`lambda-labs.lambda_labs_get_instance`

Get details for a specific Lambda Labs GPU instance by ID. Returns full instance information including status, IP, region, and GPU type.

Read read

Parameters: id

Generic call

kosmo integrations:call lambda-labs.lambda_labs_get_instance '{"id":"example_id"}' --json

Shortcut

kosmo integrations:lambda-labs lambda_labs_get_instance '{"id":"example_id"}' --json

`lambda-labs.lambda_labs_launch_instance`

Launch a new GPU instance on Lambda Labs. Requires a region name, instance type, SSH key IDs, and optionally a name and image.

Write write

Parameters: name, region_name, instance_type, ssh_key_ids, image_id, quantity

Generic call

kosmo integrations:call lambda-labs.lambda_labs_launch_instance '{"name":"example_name","region_name":"example_region_name","instance_type":"example_instance_type","ssh_key_ids":"example_ssh_key_ids","image_id":"example_image_id","quantity":1}' --json

Shortcut

kosmo integrations:lambda-labs lambda_labs_launch_instance '{"name":"example_name","region_name":"example_region_name","instance_type":"example_instance_type","ssh_key_ids":"example_ssh_key_ids","image_id":"example_image_id","quantity":1}' --json

`lambda-labs.lambda_labs_list_ssh_keys`

List all SSH keys registered in the Lambda Labs account. Returns key IDs, names, and public key fingerprints.

Read read

Parameters: none

Generic call

kosmo integrations:call lambda-labs.lambda_labs_list_ssh_keys '{}' --json

Shortcut

kosmo integrations:lambda-labs lambda_labs_list_ssh_keys '{}' --json

`lambda-labs.lambda_labs_list_instance_types`

List all available GPU instance types on Lambda Labs. Returns specs including GPU model, VRAM, vCPUs, memory, and pricing.

Read read

Parameters: none

Generic call

kosmo integrations:call lambda-labs.lambda_labs_list_instance_types '{}' --json

Shortcut

kosmo integrations:lambda-labs lambda_labs_list_instance_types '{}' --json

`lambda-labs.lambda_labs_list_images`

List all available machine images on Lambda Labs. Returns image IDs, names, and descriptions for OS templates and custom images.

Read read

Parameters: none

Generic call

kosmo integrations:call lambda-labs.lambda_labs_list_images '{}' --json

Shortcut

kosmo integrations:lambda-labs lambda_labs_list_images '{}' --json

`lambda-labs.lambda_labs_get_current_user`

Get information about the current authenticated Lambda Labs user, including email, user ID, and account status.

Read read

Parameters: none

Generic call

kosmo integrations:call lambda-labs.lambda_labs_get_current_user '{}' --json

Shortcut

kosmo integrations:lambda-labs lambda_labs_get_current_user '{}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

lambda-labs.lambda_labs_list_instances 0 parameters

Schema command

kosmo integrations:schema lambda-labs.lambda_labs_list_instances --json

Parameter	Type	Required	Description
No parameters.

lambda-labs.lambda_labs_get_instance 1 parameters

Schema command

kosmo integrations:schema lambda-labs.lambda_labs_get_instance --json

Parameter	Type	Required	Description
`id`	string	yes	The instance ID.

lambda-labs.lambda_labs_launch_instance 6 parameters

Schema command

kosmo integrations:schema lambda-labs.lambda_labs_launch_instance --json

Parameter	Type	Required	Description
`name`	string	yes	A human-readable name for the instance (e.g., "gpu-training-01").
`region_name`	string	yes	The region to launch in (e.g., "us-east-1", "us-west-2", "europe-central-1").
`instance_type`	string	yes	The instance type slug (e.g., "gpu_1x_a100", "gpu_8x_h100").
`ssh_key_ids`	array	yes	Array of SSH key IDs to assign to the instance.
`image_id`	string	no	The image ID to use for the instance OS.
`quantity`	integer	no	Number of instances to launch (default: 1).

lambda-labs.lambda_labs_list_ssh_keys 0 parameters

Schema command

kosmo integrations:schema lambda-labs.lambda_labs_list_ssh_keys --json

Parameter	Type	Required	Description
No parameters.

lambda-labs.lambda_labs_list_instance_types 0 parameters

Schema command

kosmo integrations:schema lambda-labs.lambda_labs_list_instance_types --json

Parameter	Type	Required	Description
No parameters.

lambda-labs.lambda_labs_list_images 0 parameters

Schema command

kosmo integrations:schema lambda-labs.lambda_labs_list_images --json

Parameter	Type	Required	Description
No parameters.

lambda-labs.lambda_labs_get_current_user 0 parameters

Schema command

kosmo integrations:schema lambda-labs.lambda_labs_get_current_user --json

Parameter	Type	Required	Description
No parameters.

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.