# juehang/vscode-mcp-server [Health: Active]

**Category:** 🤖 Coding Agents  
**Repository:** https://github.com/juehang/vscode-mcp-server  
**GitHub Stars:** 392  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/juehang-vscode-mcp-server

## Description
A MCP Server that allows AI such as Claude to read from the directory structure in a VS Code workspace, see problems picked up by linter(s) and the language server, read code files, and make edits.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "vscode-mcp-server": {
    "command": "npx",
    "args": ["mcp-remote@next","http://localhost:3000/mcp"]
  }
}
```

## Documentation

## What juehang/vscode-mcp-server MCP server does

The juehang/vscode-mcp-server MCP server runs as a Visual Studio Code extension and presents workspace operations through the Model Context Protocol. It gives an MCP client access to the currently opened workspace, including directory listings, file contents, symbol information, language-server diagnostics, and file modifications.

The extension is intended for coding agents that need VS Code-specific context. Symbol search, document structure, hover or definition information, and diagnostics can help an agent navigate an existing codebase without reading every file. File operations cover creating, reading, copying, moving, renaming, and making validated line replacements. The extension also exposes shell command execution through VS Code's integrated terminal.

## How it works

When enabled, the extension starts an MCP server on a configurable local port. Requests arrive over HTTP using the streamable HTTP API; the README specifically distinguishes this from the SSE API. A status bar item shows whether the server is active and allows it to be toggled on or off.

The MCP tools delegate workspace operations to VS Code APIs. Move and rename operations use WorkspaceEdit support, which provides refactoring-oriented handling for those changes. File reads support an encoding option and a maximum character limit. Line replacement requires the client to provide the expected original code, allowing the server to validate that the targeted content has not changed unexpectedly.

## Setup and configuration

Install the extension from the Visual Studio Code Marketplace, or clone the repository and build it with `npm install` followed by `npm run compile`. After installation, enable the server from VS Code using its status bar control.

Claude Desktop can connect through an MCP configuration that invokes `mcp-remote@next` against the local `/mcp` endpoint, such as `http://localhost:3000/mcp`. The example configuration uses the `npx` command and the `mcp-remote@next` package. The server port is configurable, so the client URL must match the port used by the extension.

## Tools and capabilities

The juehang/vscode-mcp-server MCP server provides tools for:

- Listing workspace files and directories, with optional recursion.
- Reading files with encoding and maximum-character options.
- Copying files and moving or renaming files and directories.
- Creating files and optionally overwriting existing files.
- Replacing a specified inclusive line range after validating its original content.
- Searching workspace symbols and retrieving symbol definitions or hover information.
- Reporting warnings and errors from the workspace, with optional path, severity, format, and source settings.
- Running shell commands in the integrated terminal with shell integration.

## Limitations and notes

The extension operates against a VS Code workspace, so it is a fit for clients that need an active editor environment rather than a standalone remote repository interface. The README documents Claude Desktop configuration, but does not establish compatibility with every MCP client.

Shell command execution creates a security risk. Use the juehang/vscode-mcp-server MCP server only with an MCP client you trust, and avoid exposing its port to untrusted networks. Authentication is not implemented because the MCP authentication specification was still in flux in the project documentation. Keep the endpoint local unless the surrounding network and client trust model are understood.

The documented integration uses a local HTTP endpoint and a separate MCP remote bridge for Claude Desktop. That bridge is part of the client configuration, not the VS Code extension itself.

_Full upstream README: https://allmcps.com/mcp/juehang-vscode-mcp-server/readme_