MCP VS Code runs on your own machine — the client starts it, so there is no endpoint to ping. 71 installs a week from npm. Last commit 5 Sep 2026.
A self-hosted VS Code workbench embedded as an interactive MCP App.
What the code does
We read the source, 5 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(options.command, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mcp-vscode -e 'MCP_VSCODE_WORKSPACE=<MCP_VSCODE_WORKSPACE>' -- npx -y @mario.andreschak/mcp-vscode{
"mcpServers": {
"mcp-vscode": {
"command": "npx",
"args": [
"-y",
"@mario.andreschak/mcp-vscode"
],
"env": {
"MCP_VSCODE_WORKSPACE": "<MCP_VSCODE_WORKSPACE>"
}
}
}
}[mcp_servers.mcp-vscode]
command = "npx"
args = ["-y", "@mario.andreschak/mcp-vscode"]
env = { MCP_VSCODE_WORKSPACE = "<MCP_VSCODE_WORKSPACE>" }{
"mcpServers": {
"mcp-vscode": {
"command": "npx",
"args": [
"-y",
"@mario.andreschak/mcp-vscode"
],
"env": {
"MCP_VSCODE_WORKSPACE": "<MCP_VSCODE_WORKSPACE>"
}
}
}
}{
"servers": {
"mcp-vscode": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mario.andreschak/mcp-vscode"
],
"env": {
"MCP_VSCODE_WORKSPACE": "<MCP_VSCODE_WORKSPACE>"
}
}
}
}Put your own value in place of
<MCP_VSCODE_WORKSPACE> (Absolute path to the workspace directory exposed through VS Code and MCP tools).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
MCP_VSCODE_RENDER_MODE (Set to 'stream' to opt into experimental genuine-workbench pixel streaming; omit for normal iframe/browser behavior), MCP_VSCODE_STREAM_BROWSER (Optional absolute path to an installed Edge, Chrome, or Chromium executable used by experimental streaming), MCP_VSCODE_STREAM_NO_SANDBOX (Unsafe container-only escape hatch: set to 1 to launch streaming Chromium without its process sandbox).
Alternatives to MCP VS Code
same job, measured the same wayMCP App that renders Mermaid diagrams as interactive UI in Claude, VS Code and other MCP clients
Self-hosted code intelligence: cross-repo Q&A, dependency audits and PR review, over MCP
Self-hosted MCP task inbox shared by Claude Code, Codex, Gemini CLI and local LLMs.
Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.
Self-hosted MCP server exposing Claude Code as an agentic AI tool over streamable HTTP.
Self-hosted MCP server: run OpenAI Codex CLI prompts and manage workspace files.
Claude Code drives Codex CLI's interactive TUI and durable tmux terminals over MCP.
Hosted MCP for source-backed project context, memory, code impact, and agent workflow continuity.
MCP VS Code — questions
Answers built from our own checks of this server.