VSCode Context MCP MCP Server

MCP Server to Connect with VS Code IDE

Local serverstdio

What is the VSCode Context MCP MCP server?

Most file and storage access work still happens through a UI a human drives. VSCode Context MCP MCP server moves it into the conversation instead. MCP Server to Connect with VS Code IDE.

The short version

A Model Context Protocol (MCP) server that provides VSCode context and filesystem operations for AI assistants.

VSCode Context MCP creates a bridge between AI assistants and your VSCode environment. It enables AI models to:

The tools it exposes

The server publishes 14 tools. What each one is for:

  • get_vscode_context — Retrieve complete VSCode context information
  • get_attached_files — Retrieve a list of files attached to the workspace
  • get_project_path — Get current project root directory
  • get_current_file — Get details and content of the active file
  • get_open_tabs — List all open editor tabs
  • get_problems — Retrieve diagnostics (errors/warnings)
  • get_terminal_content — Get terminal output and history
  • run_command — Execute a shell command
  • read_file — Read contents of a file
  • read_multiple_files — Read multiple files at once
  • write_file — Create or overwrite a file
  • edit_file — Make line-based edits to a file

Getting it running

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

Plenty of file and storage access 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. VSCode Context MCP's toolset — get_vscode_context, get_attached_files, get_project_path and 11 more — is a fair guide to whether it matches your workflow. It is maintained by vilasone455; 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.

Things to watch

  • 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.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch VSCode Context MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
get_vscode_contextRetrieve complete VSCode context information
get_attached_filesRetrieve a list of files attached to the workspace
get_project_pathGet current project root directory
get_current_fileGet details and content of the active file
get_open_tabsList all open editor tabs
get_problemsRetrieve diagnostics (errors/warnings)
get_terminal_contentGet terminal output and history
run_commandExecute a shell command
read_fileRead contents of a file
read_multiple_filesRead multiple files at once
write_fileCreate or overwrite a file
edit_fileMake line-based edits to a file
create_directoryCreate directory structure
list_directoryList files and directories

How to install the VSCode Context MCP MCP server

{
  "mcpServers": {
    "vscode-context": {
      "command": "npx",
      "args": ["-y", "npm"]
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Example prompts to try

  • Use VSCode Context MCP to get vscode context.
  • Use VSCode Context MCP to get attached files.
  • Use VSCode Context MCP to get project path.

Frequently asked questions

Be careful what commands you ask the server to run. In Claude Desktop, use “Approve Once” instead of “Allow for This Chat” so you can review each action. Deny any command you don’t trust. The server does not yet implement comprehensive security measures.