nexus -claude-desktop

Nexus MCP Bridge for VSCode enables Claude Desktop to interact with your current VSCode workspace through the Model Context Protocol. It exposes a lightweight bridge that lets Claude read and write files, create directories, list directory contents, and query project status while enforcing explicit path allowances for security. You can configure which folders Claude is allowed to access, and you can start or stop the bridge from the VSCode status bar or via the provided commands. In Claude Desktop, you’ll point the bridge to your local MCP endpoint and specify the allowed functions (e.g., get_system_info, read_file, write_file, create_directory, list_directory, get_project_status), so Claude can request operations within the allowed workspace boundaries. The bridge is designed to be auto-started if configured, reducing setup friction.

Prerequisites:

• Visual Studio Code installed
• The Nexus MCP Bridge extension packaged as a VSIX (or installed via the marketplace if available)
• Basic network access to localhost for MCP communications

Installation steps:

1. Install the VSIX extension for Nexus MCP Bridge:
   • Open VSCode
   • Press Ctrl+Shift+P (Cmd+Shift+P on macOS) and run "Extensions: Install from VSIX..."
   • Select the nexus-mcp-claude-desktop-server.vsix file
2. Configure the bridge (optional but recommended):
   • In VSCode settings, set:
     • nexusMcpBridge.port to 3000
     • nexusMcpBridge.startOnLaunch to true (if you want automatic startup)
     • nexusMcpBridge.allowedPaths to an array of workspace directories Claude may access
3. Start the bridge if it isn’t configured to start automatically:
   • Use the command palette to run "Start Nexus MCP Bridge"
4. In Claude Desktop, create or edit claude_desktop_config.json to point to the MCP server at http://localhost:3000/mcp and enumerate the allowed actions as shown in the example

Tips and considerations:

• Default port is 3000; adjust in both the VSCode extension settings and Claude Desktop config if you customize it.
• Only expose specific, whitelisted paths with nexusMcpBridge.allowedPaths to minimize security risk.
• If you encounter connection failures, ensure the bridge service is running and that the port is not blocked by a firewall.
• You can start/stop the bridge via the status bar widget or the corresponding commands in VSCode.
• The bridge supports typical MCP functions like get_system_info, read_file, write_file, create_directory, list_directory, and get_project_status; ensure Claude Desktop requests are aligned with these capabilities.
• Check for VSCode updates that may affect extension compatibility and MCP connectivity.