Can I launch a high-performance H100 instance through my agent?

Yes. Use the `launch_instance` tool and specify the type (e.g. `gpu_1x_h100`) and region. Your agent will also allow you to attach registered SSH keys so the instance is securely accessible immediately upon boot.

How do I retrieve the Jupyter Lab access token for a running node?

Use the `get_instance` tool with your Instance ID. Your agent will fetch the complete telemetry, including the public IP and the Jupyter Lab access token if the environment is configured to provide it.

Can my agent check for GPU availability across different regions?

Absolutely. The `list_instance_types` tool queries the cloud boundary for hardware inventory. Your agent will report which GPU node types are currently available and in which physical regions they are hosted.

Lambda Labs (GPU Cloud) MCP Server for VS Code Copilot 7 tools — connect in under 2 minutes

Name: Lambda Labs (GPU Cloud)
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 7 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Lambda Labs (GPU Cloud) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "lambda-labs-gpu-cloud": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Lambda Labs (GPU Cloud) MCP Server

Connect your Lambda Labs account to any AI agent and take full control of your AI infrastructure and high-performance GPU orchestration through natural conversation.

GitHub Copilot Agent mode brings Lambda Labs (GPU Cloud) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Instance Orchestration — Launch state-of-the-art GPU virtual machines (e.g., H100, A100) and manage their entire lifecycle directly from your agent
ML Infrastructure Audit — List running instances and retrieve detailed hardware specifications, public IPv4 addresses, and Jupyter Lab access tokens securely
Inventory & Pricing — Discover available GPU node types and pricing matrices across different regions to optimize your AI training and inference budget
SSH Key Management — Enumerate globally managed public keys to ensure zero-trust infrastructure provisioning and secure access over port 22
Storage Mapping — Discover persistent shared NAS volumes living in the Lambda ecosystem that can be mounted simultaneously across multiple worker nodes
Resource Cleanup — Terminate and deallocate compute nodes instantly to stop billing and maintain a clean cloud footprint

The Lambda Labs (GPU Cloud) MCP Server exposes 7 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Lambda Labs (GPU Cloud) to VS Code Copilot via MCP

Follow these steps to integrate the Lambda Labs (GPU Cloud) MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Lambda Labs (GPU Cloud)

Ask Copilot: "Using Lambda Labs (GPU Cloud), help me..." — 7 tools available

Why Use VS Code Copilot with the Lambda Labs (GPU Cloud) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Lambda Labs (GPU Cloud) through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Lambda Labs (GPU Cloud) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Lambda Labs (GPU Cloud) MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Lambda Labs (GPU Cloud) MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect Lambda Labs (GPU Cloud) to VS Code Copilot via MCP:

get_instance

Get exact details and SSH connection string for a specific instance

launch_instance

g., powerful H100 or A100 boxes). Injects explicit SSH keys into the runtime so it is securely accessible over port 22 immediately upon boot. Provision a new Lambda GPU virtual machine

list_filesystems

Map persistent shared NAS volumes living in the Lambda ecosystem

list_instance_types

Exposes exact catalog configurations of available GPU node types, identifying exactly which regions currently hold physical availability. Discover available Lambda GPU instance specifications and pricing

list_instances

List running GPU instances on Lambda Cloud

list_ssh_keys

Enumerate globally managed SSH public keys in Lambda

terminate_instances

Any ephemeral drives attached will be vaporized immediately without backup. Extremely destructive; stops billing instantly. Permanently terminate and destroy Lambda GPU instances

Example Prompts for Lambda Labs (GPU Cloud) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Lambda Labs (GPU Cloud) immediately.

"List all my running GPU instances in Lambda Cloud"

"Launch a 1x H100 instance in us-east-1 with my 'default-key' SSH key"

"What are the available instance types and their current pricing?"

Troubleshooting Lambda Labs (GPU Cloud) MCP Server with VS Code Copilot

Common issues when connecting Lambda Labs (GPU Cloud) to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Lambda Labs (GPU Cloud) + VS Code Copilot FAQ

Common questions about integrating Lambda Labs (GPU Cloud) MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.