Chpatil Vscode MCP Extension MCP Server

VSCode tools and resources as a Model Context Protocol (MCP) server in a VSCode extension. Exposed over MCP by the chpatil vscode mcp extension mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

The VSCode MCP Server is a VSCode extension that acts as a Model Context Protocol (MCP) server integrated directly within VSCode. Its primary purpose is to expose a coding diagnostic tool—namely, the code_checker—which aggregates diagnostic messages (similar to those displayed in VSCode’s Problems panel) and makes them accessible to an external AI assistant via Server-Sent Events (SSE). This allows your assistant to invoke MCP methods and retrieve timely diagnostic information from your workspace.

• Automatic Startup: —
• MCP Server Integration: —
• Diagnostic Tool (code_checker): —
• Focus Editor Tool (focus_editor) — Opens a specific file in the VSCode editor and navigates to a designated line and column. Useful for bringing files into visual focus for the user but does not include file content in the tool call result
• Search Symbol Tool (search_symbol) — Searches for symbols in the workspace, using "Go to Definition" primarily, with a fallback to text search (similar to Ctrl+Shift+F). Can optionally open the results in the editor using the focus_editor tool
• Debug Session Management Tools: —

Adding it to your client

mcp-proxy on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Its toolset

Everything the assistant can do here goes through one of these:

• list_debug_sessions — Retrieve all active debug sessions in the workspace
• start_debug_session — Start a new debug session with the provided configuration
• stop_debug_session — Stop debug sessions matching a specific session name
• restart_debug_session — Restart a debug session by stopping it and then starting it with the provided configuration (new!)
• NOTE — This is different than just closing the window or using File > Close, which leaves the application running in the background
• Prerequisites — 1. Clone the Repository: Clone the Semantic Workbench repository to your local machine:

Configuration

1. Clone the Repository: Clone the Semantic Workbench repository to your local machine: 2. Navigate to the Project Directory: 3. Install Dependencies: Ensure you have Node.js (v16 or higher) and pnpm installed. Then, from the project directory, run: 4. Package the Extension: To package the extension, execute: This will generate a .vsix file in the project root.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the chpatil vscode mcp extension mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Chpatil Vscode MCP Extension's toolset — list_debug_sessions, start_debug_session, stop_debug_session and 3 more — is a fair guide to whether it matches your workflow. It is maintained by cspatil8; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.