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 Shell Scripts

Use the Lambda Labs CLI for shell scripts with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write API key auth

Submit Lambda Labs feedback View package source

Lambda Labs CLI for Shell Scripts

Call integration functions from shell scripts with stable JSON input and output.

Use shell scripts for small local automations that need one or more integration calls. The Lambda Labs CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Lambda Labs CLI for Shell Scripts
kosmokrator integrations:configure lambda-labs --set api_key="$LAMBDA_LABS_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call lambda-labs.lambda_labs_list_instances '{}' --json

Discovery Before Execution

Agents and scripts can inspect Lambda Labs docs and schemas before choosing a function.

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

Useful Lambda Labs CLI Functions

Function	Type	Parameters	Description
`lambda-labs.lambda_labs_list_instances`	Read	none	List all GPU instances in the Lambda Labs account. Returns instance IDs, names, status, IP addresses, and GPU configuration.
`lambda-labs.lambda_labs_get_instance`	Read	id	Get details for a specific Lambda Labs GPU instance by ID. Returns full instance information including status, IP, region, and GPU type.
`lambda-labs.lambda_labs_launch_instance`	Write	name, region_name, instance_type, ssh_key_ids, image_id, quantity	Launch a new GPU instance on Lambda Labs. Requires a region name, instance type, SSH key IDs, and optionally a name and image.
`lambda-labs.lambda_labs_list_ssh_keys`	Read	none	List all SSH keys registered in the Lambda Labs account. Returns key IDs, names, and public key fingerprints.
`lambda-labs.lambda_labs_list_instance_types`	Read	none	List all available GPU instance types on Lambda Labs. Returns specs including GPU model, VRAM, vCPUs, memory, and pricing.
`lambda-labs.lambda_labs_list_images`	Read	none	List all available machine images on Lambda Labs. Returns image IDs, names, and descriptions for OS templates and custom images.
`lambda-labs.lambda_labs_get_current_user`	Read	none	Get information about the current authenticated Lambda Labs user, including email, user ID, and account status.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Lambda Labs CLI Pages

CI Lambda Labs CLI for CI. Cron Jobs Lambda Labs CLI for cron jobs. Headless Automation Lambda Labs CLI for headless automation. Coding Agents Lambda Labs CLI for coding agents.