lambda_get_instance — lambda labs MCP Tool
lambda_get_instance
(lambda get instance) is one of 15 tools on the
lambda labs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call lambda_get_instance from your client
- Claude Code lambda labs lambda_get_instance run in your project directory
- Claude Desktop lambda labs lambda_get_instance ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor lambda labs lambda_get_instance ~/.cursor/mcp.json
- VS Code lambda labs lambda_get_instance .vscode/mcp.json
- Zed lambda labs lambda_get_instance ~/.config/zed/settings.json
- Windsurf lambda labs lambda_get_instance ~/.codeium/windsurf/mcp_config.json
- Cline lambda labs lambda_get_instance ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI lambda labs lambda_get_instance ~/.gemini/settings.json
- Grok lambda labs lambda_get_instance .mcp.json (in your project root)
- ChatGPT lambda labs lambda_get_instance Settings → Connectors → Advanced → Developer mode
- Claude.ai lambda labs lambda_get_instance Settings → Connectors → Add custom connector
- LangChain lambda labs lambda_get_instance pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http lambda-labs https://lambda-labs.usefulapi.io/mcp
Other tools on this server
- lambda_list_instances
- lambda_list_instance_types
- lambda_list_images
- lambda_list_filesystems
- lambda_list_firewall_rules
- lambda_list_firewall_rulesets
- lambda_get_firewall_ruleset
- lambda_list_audit_events
- lambda_launch_instance
- lambda_restart_instances
- lambda_terminate_instances
- lambda_update_instance
- lambda_create_filesystem
- lambda_delete_filesystem
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.