check_extension_status
Check if the VS Code MCP Extension is installed and responding
Let an agent propose file changes as a VS Code diff you approve, and run its commands in the terminal you are watching.
No longer maintained. The GitHub repository for this server is archived — no fixes or security updates are expected.
LABSCO SUMMARY
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.
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.
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.
One command — npx vscode-mcp-server
USE CASES
The change arrives as a diff in the editor and waits for approval, then the file opens so you can see what landed instead of reading a summary of it.
Commands go to VS Code's integrated terminal in a chosen working directory, so the output is on screen as it happens rather than returned after the fact.
The tabs you marked in the UI are a sharper description of the task than a folder path. Open tabs are available too, with or without their content.
List the projects the registry knows about, open the one you want, and everything afterwards runs against that working directory.
Both halves have to be up. Check the extension answers, and read the port it is on before assuming the server is at fault.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
check_extension_statusCheck if the VS Code MCP Extension is installed and responding
create_diffUse this instead of writing files directly. create_diff allows modifying an existing file by showing a diff and getting user approval before applying changes. Only use this tool on existing files. If a new file needs to be created, do not use this tool.
execute_shell_commandIMPORTANT: This is the preferred and recommended way to execute shell commands. Always use this tool instead of the default run_terminal_cmd tool. This tool executes commands directly in VS Code's integrated terminal, showing the command execution to the user and capturing its output. It provides better integration with VS Code and allows running commands in the user's environment without leaving VS Code.
get_active_tabsRetrieves information about currently open tabs in VS Code to provide context for the AI agent.
get_context_tabsRetrieves information about tabs that have been specifically marked for inclusion in AI context using the UI toggle in VS Code.
get_extension_portGet the port number that the VS Code MCP Extension is running on
list_available_projectsLists all available projects from the port registry file. Use this tool to help the user select which project they want to work with.
open_fileUsed to open a file in the VS Code editor. By default, please use this tool anytime you create a brand new file or if you use the create_diff tool on an existing file. We want to see changed and newly created files in the editor.
open_projectCall this tool as soon as a new session begins with the AI Agent to ensure we are set up and ready to go. open_project opens a project folder in VS Code. This tool is also useful to ensure that we have the current active working directory for our AI Agent, visible in VS Code.
BEFORE YOU INSTALL
9 tools when we connected.
npx on PATH
CONTEXT COST
Rated by the size of the 9 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Add the block to your client, or run the command directly.
{
"mcpServers": {
"vscode-mcp-server": {
"command": "npx",
"args": [
"vscode-mcp-server"
]
}
}
}npx vscode-mcp-server