Summary
Agent edits arriving on disk before you have had a chance to look at them.
create_diff is the whole argument for this server: the change appears in VS Code's diff view and waits, so review is the default rather than a git command you run afterwards. get_context_tabs is the second reason — the tabs you explicitly marked are a much better description of what you are working on than a repository path is.
What it is
A bridge to a running VS Code window through its extension: nine tools covering diffs, file and project opening, terminal execution, and the tabs you have open.
What you get
- File changes presented as a diff in the editor and applied only after approval, instead of written straight to disk
- Shell commands executed in VS Code's integrated terminal, where the output is visible as it runs
- Files opened in the editor at a chosen view column, as a preview or a full tab
- A project folder opened in the current window or a new one, which also fixes the working directory the rest of the calls use
- The list of projects registered in the port registry file, so the right window can be chosen before anything runs
- The currently open tabs, and separately the tabs explicitly marked for AI context in the UI, each optionally with their content
Requirements
The VS Code MCP extension installed and responding in the window you want driven; the server reaches it on a port from the registry file.
Setup effort
One command — npx vscode-mcp-server