MCP.so
Sign In

Nexus MCP Bridge for VSCode

@MCP-Mirror

Basic information

Category

Developer Tools

License

MIT license

Transports

stdio

Author

MCP-Mirror

About Nexus MCP Bridge for VSCode

Mirror of

Nexus MCP Bridge for VSCode config

Add this server to your MCP-compatible client using the configuration below.

{
  "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"
      ]
    }
  }
}

Nexus MCP Bridge for VSCode tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is Nexus MCP Bridge for VSCode?

A lightweight VSCode extension that acts as a bridge, enabling Claude Desktop to connect to your VSCode workspace via the Model Context Protocol (MCP). It is designed for users who want Claude Desktop to interact directly with workspace files and directories while keeping a small memory footprint and staying inside VSCode.

How to use Nexus MCP Bridge for VSCode?

Install the extension from the VSIX file, then optionally configure settings such as the port and allowed paths. The bridge can start automatically on VSCode launch (startOnLaunch setting) or manually via the commands: “Start Nexus MCP Bridge”, “Stop Nexus MCP Bridge”, or “Toggle Nexus MCP Bridge” from the status bar. Finally, add the bridge to Claude Desktop’s claude_desktop_config.json with the URL http://localhost:3000/mcp and list the tools you want to allow.

Key features of Nexus MCP Bridge for VSCode

  • Minimal memory footprint and lightweight design.
  • Automatic startup when VSCode launches.
  • Status bar integration for easy control.
  • File system read and write access in the workspace.
  • Directory management (create directories, list contents).
  • Security controls to restrict accessible paths.

Use cases of Nexus MCP Bridge for VSCode

  • Let Claude Desktop edit and create files in your project without leaving VSCode.
  • Reduce memory usage by using a lightweight bridge instead of a full server.
  • Protect sensitive system areas by explicitly allowing only specific directories.
  • Automate project workflows by combining Claude Desktop’s reasoning with direct file access.

Frequently asked questions

1

What is the default port for the bridge?

The default port is `3000`, as shown in the configuration example (`nexusMcpBridge.port`).

2

How do I start the bridge?

You can start it either automatically by setting `nexusMcpBridge.startOnLaunch` to `true` in VSCode settings, or manually using the “Start Nexus MCP Bridge” command or the status bar toggle.

3

Which directories can Claude access?

Only the directories listed in the `nexusMcpBridge.allowedPaths` configuration array. By default, none are allowed; you must explicitly specify each path.

4

What tools does Claude Desktop need to allow?

The `alwaysAllow` list in `claude_desktop_config.json` can include `get_system_info`, `read_file`, `write_file`, `create_directory`, `list_directory`, and `get_project_status`.

5

Will the bridge start automatically every time I open VSCode?

Only if you set `"nexusMcpBridge.startOnLaunch": true` in your VSCode settings. Otherwise, you must start it manually.

Comments

More Developer Tools MCP servers