MCP VS Code

MCP VS Code runs locally from a Node.js package published to the npm registry: @mario.andreschak/mcp-vscode version 0.2.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @mario.andreschak/mcp-vscode@0.2.2. It reads these environment variables: MCP_VSCODE_WORKSPACE (required), MCP_VSCODE_RENDER_MODE, MCP_VSCODE_STREAM_BROWSER and MCP_VSCODE_STREAM_NO_SANDBOX; set them in the client's configuration for this server. Required arguments: --stdio.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "mcp-vscode": {
      "command": "npx",
      "args": [
        "-y",
        "@mario.andreschak/mcp-vscode@0.2.2"
      ],
      "env": {
        "MCP_VSCODE_WORKSPACE": "<value>",
        "MCP_VSCODE_RENDER_MODE": "<value>",
        "MCP_VSCODE_STREAM_BROWSER": "<value>",
        "MCP_VSCODE_STREAM_NO_SANDBOX": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect