VSCode MCP
An MCP bridge to VS Code that gives agents language-server diagnostics and symbol references instead of slow tsc runs.
- 105 ★ on the repository
- Last commit
Broad access
Why this level
- `execute_command` runs arbitrary editor commands and the docs themselves warn about dangerous operations.
- `rename_symbol` edits files across the whole workspace.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/vscode-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- `execute_command` runs arbitrary editor commands and the docs themselves warn about dangerous operations.
- `rename_symbol` edits files across the whole workspace.
This is third-party code. Review the repository files before installing.
What it does
The project has two parts: the VSCode MCP Bridge extension and the `@vscode-mcp/vscode-mcp-server` MCP server. The extension opens a socket and the server relays its tools to the client: `get_diagnostics` returns errors and warnings from the LSP, `get_symbol_lsp_info` gives definitions, hover and signatures, `get_references` finds usages, and `rename_symbol` renames a symbol across the workspace and updates imports. There are also `open_files`, `list_workspaces`, `health_check` and `execute_command` for arbitrary VS Code commands. The same tools exist as `vscode-cli` subcommands for agents that would rather not register an MCP server.
Who it is for. Developers working on TypeScript projects in Cursor or Claude Code who are tired of waiting for type checks after every agent edit.
Good fit when
- An agent edited code and type errors have to show up within seconds.
- Before a refactor you need every usage of a function with surrounding code.
- A symbol is renamed across a monorepo together with imports.
- An agent cannot register MCP but can run shell commands.
Not a fit when
- VS Code is not running: the bridge works only with an open window.
- You need CI checks without an editor: `tsc` and `eslint` fit better.
- The model cannot be trusted with arbitrary editor commands.
Example request
Call get_diagnostics for the open project, list type errors per file and find every reference to the `parseConfig` function.MCP
- Transport
- stdio
- Authentication
- not required
Environment variables
VSCODE_MCP_DISABLED_TOOLS- Comma-separated list of tools to disable, for example `health_check,list_workspaces,open_files`.
Limitations
The `YuTengjing.vscode-mcp-bridge` extension must first be installed in a running VS Code, otherwise the server cannot connect. The `execute_command` tool runs any editor command and the docs warn about dangerous operations: disable it through `VSCODE_MCP_DISABLED_TOOLS`. Diagnostic quality depends on the language servers installed in the editor. The licence is Anti 996, which GitHub metadata does not recognise. The last commit is from August 2026.
How to disable. Remove the `vscode-mcp` entry from the client configuration, for example `claude mcp remove vscode-mcp`, and disable the extension in VS Code.
FAQ
Is the VS Code extension required?
Yes. Without `YuTengjing.vscode-mcp-bridge` in a running editor the MCP server gets no data.
Does it work in Cursor?
Yes, the README has an install button for Cursor. Codex and Gemini CLI get their own configurations.
How do I disable the dangerous tools?
`VSCODE_MCP_DISABLED_TOOLS` takes a list, for example `health_check,list_workspaces,open_files`.
What if I skip MCP?
Install `@vscode-mcp/vscode-mcp-cli` and call `vscode-cli get-diagnostics` and other subcommands.
Which languages are covered?
Any with a language server in the editor. The author mostly describes TypeScript.
Discussion
No questions or reviews yet.
Related
MCP serversA VS Code extension that runs a local MCP server so an agent can search symbols, edit files and run commands in the terminal
The openmcp CLI and a VS Code extension for debugging MCP servers: tools, prompts and resources, chat with a model, test cases
A bridge from an LSP language server to the agent: definitions, references, diagnostics, hover and symbol rename
The official Microsoft MCP server for debugging: a VS Code extension and a CLI give an agent breakpoints, steps, variables and expression evaluation
An MCP to LSP bridge: the agent gets types, references, diagnostics and refactoring from rust-analyzer, pyright and gopls.
VS Code extension for finding and installing MCP servers and skills for GitHub Copilot, Claude Code and Codex CLI
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| VSCode MCP (this card) | no | not required | 105 | |
| cclsp | no | not required | 675 | gives navigation via LSP servers directly; vscode-mcp reads data from an already open editor |
| Claude Code LSPs | no | 520 | a plugin with language servers for Claude Code; vscode-mcp works through a VS Code extension |
README in short
States the motivation: the LSP answers faster than a full type check. The `execute_command` tool carries a security warning.