A file server for an assistant lives or dies on scope. Here the exposed set is an explicit array in your VSCode settings, so a project you did not list is simply not visible — and the status bar tells you at a glance whether the bridge is live. It is deliberately small: read, write, create and list, plus two status calls. If you want search, refactoring or terminal access, this is not that.
A bridge that runs inside VSCode and serves your workspace over MCP to Claude Desktop, so file work happens against the project you are already looking at instead of a separate connection.
- File access: `read_file` and `write_file` inside the workspace
- Directory work: `create_directory` and `list_directory`
- `get_system_info` and `get_project_status` report the environment and the current project
- A status bar item shows whether the bridge is running, with commands to start, stop or toggle it
- It can start automatically when VSCode launches
Install the extension from its VSIX file into VSCode. Claude Desktop connects to http://localhost:3000/mcp. Configure `nexusMcpBridge.port`, `nexusMcpBridge.startOnLaunch`, and `nexusMcpBridge.allowedPaths` — the last one is the list of directories the bridge will expose, and nothing outside it is reachable.