VSC-MCP Server

A VSCode extension that exposes your IDE as an MCP server — compensating for missing capabilities required by AI agents and enabling advanced control.

Features

• Start/stop the built-in MCP server from VS Code
• Execute commands in the integrated terminal and fetch output
• Code diagnostics as a tool for MCP clients
• Quick confirmation UI options: InputBox (editable), Status Bar buttons
• Multi‑instance switching across VS Code windows

Key Features

Terminal Operations

• Execute commands within VSCode’s integrated terminal (supports background/foreground execution, and timeout settings).

Multi-instance Switching

• Easily switch the MCP server between multiple open VSCode windows.(Just by clicking the status bar item)

Relay Functionality

• Returns the built-in tools defined in the relay's initial_tools.ts.
• Proxies tool execution to the VSC-MCP extension at --server-url.

Available Built-in Tools

• execute_command: Execute commands in VSCode’s integrated terminal
• code_checker: Retrieve current diagnostics for your code
• focus_editor: Focus specific locations within files
• get_terminal_output: Fetch output from a specified terminal

Configuration

1. Disable the IDE's default terminal tools

2. Configure your MCP client:

   Clients like VSCode, Cursor, Trae: add the following to your configuration file (mcp.json):

   {
     "mcpServers": {
         "vscode": {
           "command": "npx",
           "args": [
           "-y",
           "vsc-mcp",
           "--server-url",
           "http://localhost:60100",
           "--enable",
           "execute_command",
           "--enable",
           "code_checker",
           "--enable",
           "get_terminal_output"
           ]
         }
     }
   }
   

3. Check the MCP server status in the bottom-left VSCode status bar:

• (Server icon): Server is running
• ∅: Click to start the server

4. Recommended rules for AI agents:

## Code Development
- **After code editing**: Always check code using `mcp_vscode_code_checker` tool

## Tools Priority
- **Rule**: Always use ONLY `mcp_vscode_execute_command`, `mcp_vscode_get_terminal_output` instead of any other command line tool to perform tasks

## Terminal Analysis
- **CRITICAL**: MUST always read and analyze complete terminal output, not just exit code
- **Forbidden**: Never make assumptions based solely on exit codes
- **Required**: Always examine actual output text, error messages, warnings, and any other information displayed before providing response or next steps

Commands

• MCP Server: Start Server
• MCP Server: Stop Server
• MCP Server: Toggle Active Status

Settings

• mcpServer.startOnActivate (boolean, default: true) — start server on VS Code activation
• mcpServer.port (number, default: 60100) — port of the MCP server
• mcpServer.confirmationUI ("InputBox" | "statusBar", default: "InputBox") — UI for command confirmation
• mcpServer.confirmNonDestructiveCommands (boolean, default: false) — ask confirmation even for non‑destructive commands

Command Line Options

• --server-url: Base URL of the MCP server (default: http://localhost:60100)
• --listen-port: Starting port to listen for incoming JSON-RPC messages (default: 6011)
• --disable: Disable specific tools from being displayed (e.g., --disable text_editor --disable list_directory)
• --enable: Enable only specific tools (whitelist mode) - when used, only specified tools will be available (e.g., --enable execute_command --enable code_checker)

Attribution

This project is a fork of acomagu/vscode-as-mcp-server by Yuki Ito. Original copyrights and third-party notices are retained under Apache-2.0. This distribution is maintained by Ivan Mezentsev.