MCP VS Code runs on your own machine — the client starts it, so there is no endpoint to ping. 65 installs a week from npm. Last commit 5 Sep 2026.
A self-hosted VS Code workbench embedded as an interactive MCP App.
We read the source, 20 h ago · rules 3dff92dd89df
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, {
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
- name: Create or update the release pull request
if: ${{ env.RELEASE_APP_CLIENT_ID_CONFIGURED == 'true' && env.RELEASE_APP_PRIVATE_KEY_CONFIGURED == 'true' }}
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
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 -- npx -y @mario.andreschak/mcp-vscode
{
"mcpServers": {
"mcp-vscode": {
"args": [
"-y",
"@mario.andreschak/mcp-vscode"
],
"command": "npx"
}
}
}
[mcp_servers.mcp-vscode]
command = "npx"
args = ["-y", "@mario.andreschak/mcp-vscode"]
{
"mcpServers": {
"mcp-vscode": {
"args": [
"-y",
"@mario.andreschak/mcp-vscode"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"mcp-vscode": {
"args": [
"-y",
"@mario.andreschak/mcp-vscode"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
MCP_VSCODE_WORKSPACE (Absolute path to the workspace directory exposed through VS Code and MCP tools.), 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.).
The author declared them in the registry entry; get the values from the project itself.
MCP 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 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.
Code-pinned team memory for AI coding agents — typed artifacts, MCP-native, self-host.
Answers built from our own checks of this server.