Can the AI forcefully terminate or delete critical production endpoint fleets on demand?

No. This module safely allows the AI to only pause and manage running instances. Destructive deletion actions (like completely erasing a pod) are intentionally prohibited by the tooling design to protect your critical compute resources from unintended loss.

Can the AI provision large GPU arrays automatically?

Yes. Using the `create_pod` capability, the AI can query the available hardware models (such as A100 or H100) and immediately launch new Docker clusters based on existing community templates, simplifying complex DevOps scaling actions significantly.

Will the AI know the billing state or the real-time cost of running each endpoint?

No. The current RunPod AI module is concentrated on operational control and system orchestration, such as discovering inactive processes and booting new instances. Deep billing analytics or invoice extraction is not natively integrated in the commands exposed to the AI at this time.

RunPod MCP Server for VS Code Copilot 7 tools — connect in under 2 minutes

Name: RunPod
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 RunPod and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "runpod": {
      "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 RunPod MCP Server

Connect your AI directly to RunPod, the leading cloud infrastructure provider for on-demand GPU computing and serverless execution. Empower your conversational agent to act as a highly proficient DevOp engineer, managing advanced computational workloads, exploring deployment options, and spinning up new hardware instances.

GitHub Copilot Agent mode brings RunPod 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

Manage Pods On-Demand — Effortlessly identify running and paused GPU machines across your cloud account (list_pods, get_pod). Halt specific billable instances to control costs securely (stop_pod).
Provision GPU Workloads — Find verified templates or specific GPU architectures ready for deployment (list_templates, list_gpu_types), and create entirely new hardware nodes immediately directly from chat (create_pod).
Audit Serverless Environments — Review all registered endpoints routing your containerized inference applications (list_endpoints).

The RunPod 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 RunPod to VS Code Copilot via MCP

Follow these steps to integrate the RunPod 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 RunPod

Ask Copilot: "Using RunPod, help me..." — 7 tools available

Why Use VS Code Copilot with the RunPod MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with RunPod 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

RunPod + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the RunPod 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

RunPod MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect RunPod to VS Code Copilot via MCP:

create_pod

Specify name, GPU type, and Docker image. Creates a new GPU pod

get_pod

Retrieves details for a specific GPU pod

list_endpoints

Lists all serverless endpoints

list_gpu_types

Lists available GPU hardware types

list_pods

Lists all GPU pods in the account

list_templates

Lists saved pod templates

stop_pod

Stops a running GPU pod

Example Prompts for RunPod in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with RunPod immediately.

"Show me our stopped GPU pods."

"Check what GPU templates are available to deploy a new Llama-3 inference instance."

"Pause pod with ID 'pod_xyz_980' immediately to prevent recurring costs throughout the evening."

Troubleshooting RunPod MCP Server with VS Code Copilot

Common issues when connecting RunPod 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.

RunPod + VS Code Copilot FAQ

Common questions about integrating RunPod 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.