What is the default port for the bridge?
The default port is `3000`, as shown in the configuration example (`nexusMcpBridge.port`).
@MCP-Mirror
基本信息
Mirror of
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"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"
]
}
}
}工具列表暂未提供
当前收录暂时没有可展示的工具列表,不代表服务没有工具。请查阅项目文档了解支持的能力。
点击上方按钮,直接连接服务器端点实时获取工具列表。
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.
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.
The default port is `3000`, as shown in the configuration example (`nexusMcpBridge.port`).
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.
Only the directories listed in the `nexusMcpBridge.allowedPaths` configuration array. By default, none are allowed; you must explicitly specify each path.
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`.
Only if you set `"nexusMcpBridge.startOnLaunch": true` in your VSCode settings. Otherwise, you must start it manually.

One case file per task — shared by every session, agent and person that touches it. Self-hosted MCP server and live board. MIT.

Routebase keeps your API's design, docs, contract tests, mocks and monitoring in one living OpenAPI spec so they can't drift apart. Agents work on that same source of truth, under your team's permissions.

MCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools

Kaiva Bridge turns your API, database or documents into a managed MCP server for Claude, ChatGPT, Cursor and VS Code. Point it at an OpenAPI or Swagger spec, an API docs link, a cURL command, a Postman collection, a Grap
Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.
评论