Nexus MCP Bridge for VSCode

Nexus MCP Bridge for VSCode is an MCP server that connects Claude Desktop directly to your Visual Studio Code workspace over a local HTTP connection. Software developers and engineers who build code within VSCode and use Claude Desktop for assistance can use this bridge to give the model direct access to their active files and directories. Rather than manually copying project contexts or switching tools, the bridge enables Claude Desktop to read local files, write updates, create new directories, inspect directory contents, and fetch project and system status. The extension runs directly inside VSCode with a minimal memory footprint and offers a status bar toggle to control server execution. It also enforces security controls by allowing users to restrict access strictly to whitelisted project paths configured in VSCode settings. By delegating file operations across the Model Context Protocol, the extension allows users to collaborate with Claude while maintaining strict boundaries on local file system read and write permissions.

Category: Developer Tools & Code Intelligence

Tags: filesystem, ide, vscode, workspace

Visit Nexus MCP Bridge for VSCode

How to install and configure Nexus MCP Bridge for VSCode

1. Install the extension from the VSIX file in Visual Studio Code. 2. Configure your settings in VSCode settings if needed, such as nexusMcpBridge.port, nexusMcpBridge.startOnLaunch, and nexusMcpBridge.allowedPaths. 3. Start the server using the Command Palette command Start Nexus MCP Bridge or via the status bar toggle. 4. In Claude Desktop, edit claude_desktop_config.json to register the server: json { "mcpServers": { "nexus-bridge": { "url": "http://localhost:3000/mcp", "disabled": false, "alwaysAllow": [ "get_system_info", "read_file", "write_file", "create_directory", "list_directory", "get_project_status" ] } } } 5. Restart Claude Desktop to begin using the bridge.

What you can do with Nexus MCP Bridge for VSCode

• Reading workspace source code files directly from Claude Desktop to analyze syntax, debug logic, or review pull requests. - Writing refactored code and generating new files directly into allowed repository directories without copying and pasting manually. - Listing folder hierarchies and directory structures to help Claude understand project layout across designated local file paths. - Creating new project directories and scaffolding project modules automatically using Claude Desktop tool execution. - Restricting file system operations to specific project paths using extension settings to maintain local workspace security boundaries.

Key facts

• https://github.com/wesnermichel/nexus-mcp-claude-desktop-server
• Developer Tools & Code Intelligence, Files, Documents & PDFs
• filesystem, ide, vscode, workspace

Part of MCP Servers

Which MCP clients work with Nexus MCP Bridge for VSCode?

Nexus MCP Bridge for VSCode is designed to connect Claude Desktop to your local VSCode workspace. Any Model Context Protocol client capable of interacting with HTTP MCP endpoints can communicate with the server once it is running on the configured port.

What tools does Nexus MCP Bridge for VSCode provide?

The server provides tools for managing local workspaces. These include reading files, writing files, listing directory contents, creating directories, retrieving system information, and checking project status. Users can also configure Claude Desktop to allow these specific operations without manual confirmation.

How do I install Nexus MCP Bridge for VSCode?

Install the extension into VSCode from its VSIX package. Once installed, configure optional settings such as port number and allowed directory paths in VSCode. Start the bridge via the status bar or command palette, then add the HTTP endpoint configuration to your Claude Desktop config file.

Is Nexus MCP Bridge for VSCode open source?

Yes, Nexus MCP Bridge for VSCode is open-source software released under the MIT license. You can view, inspect, and contribute to the source code on its GitHub repository.

How does the bridge restrict file access?

The extension lets you define an allowedPaths setting in your VSCode configuration. This ensures that the MCP bridge only exposes the specific project directories you select, protecting other local system files from unauthorized reading or writing during automated sessions.