cursor-bridge

An MCP (Model Context Protocol) server that gives Claude IDE capabilities inside VS Code and Cursor. Claude can read, write, edit, search, and run commands in your workspace — directly from the chat.

Tools

Cursor-control tools

cursor_send, cursor_send_and_wait, cursor_read_chat, and cursor_list_workspaces talk directly to Cursor's Chrome DevTools Protocol (CDP) debug port and to its state.vscdb SQLite database — they do not require the cursor-mcp-bridge extension. All other Cursor-control tools do require the extension (see below) running in the target Cursor window, and take a port argument for its fixed HTTP bridge port.

Requirement: Cursor must be launched with --remote-debugging-port=<port> (default 9222) for the CDP-based tools to work. See CDP debug port setup below.

CDP debug port setup (required for chat tools)

cursor_send, cursor_send_and_wait, cursor_read_chat, and cursor_list_workspaces connect to Cursor's native Chrome DevTools Protocol debug port. Cursor must be relaunched with --remote-debugging-port for these to work — the flag cannot be enabled while Cursor is already running.

Set the CURSOR_CDP_PORT environment variable if you use a non-default port (default 9222) when running the cursor-bridge server — see the MCP server config examples below (env field).

macOS — quit Cursor fully, then relaunch from a terminal:

open -a Cursor --args --remote-debugging-port=9222

To make this persistent (survive Dock/Spotlight launches too), edit Cursor's Info.plist launch arguments or wrap the app in a shell alias that always passes the flag before opening it normally.

Linux — launch (or add to your .desktop file's Exec= line):

cursor --remote-debugging-port=9222

Windows — add the flag to the shortcut target, or launch from PowerShell/cmd:

cursor.exe --remote-debugging-port=9222

For a persistent setup on any OS, edit the application's launch shortcut/.desktop entry once so every normal launch (Dock, Start Menu, taskbar) includes the flag — this needs to be done only once per machine.

Related MCP server: code-context

The cursor-mcp-bridge extension

extension/ is a small VS Code/Cursor extension that exposes an HTTP bridge for VS Code-command-dependent tools (/command, /editor/*, /diagnostics, /model/*, /commands, /status). It is cross-platform (macOS, Linux, Windows) and listens on a fixed, configurable port (default 9421, set via the cursorMcpBridge.port VS Code setting).

Chat send/read/discovery no longer go through this extension — they use CDP and direct SQLite reads from the client (see CDP debug port setup above).

Building and deploying the extension:

bash scripts/deploy.sh

This builds the MCP server and the extension, packages a .vsix, installs it into Cursor's extensions directory, and reloads the active window.

Installation

npm install
npm run build

Using with Cursor

Cursor reads MCP server configuration from:

• Global: ~/.cursor/mcp.json

• Project: .cursor/mcp.json (in your project root)

Option A — run via node (after build)

Add to your Cursor MCP config:

{
  "mcpServers": {
    "cursor-bridge": {
      "command": "node",
      "args": ["/absolute/path/to/cursor-bridge/dist/index.js"],
      "env": { "CURSOR_CDP_PORT": "9222" }
    }
  }
}

CURSOR_CDP_PORT (default 9222) must match the --remote-debugging-port value Cursor was launched with.

Option B — run via npx (no manual build needed)

{
  "mcpServers": {
    "cursor-bridge": {
      "command": "npx",
      "args": ["--yes", "cursor-bridge"]
    }
  }
}

After editing the config, open Cursor Settings → Features → MCP and click Refresh (or restart Cursor).

Using with VS Code + Copilot Chat (MCP support)

Add to your VS Code settings.json:

"mcp": {
  "servers": {
    "cursor-bridge": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/cursor-bridge/dist/index.js"]
    }
  }
}

Development

npm run dev    # watch mode (recompiles on save)
npm start      # run the built server

Tips

• All paths can be absolute or relative to the workspace root.

• Pass workspace_root to any tool to anchor relative paths to a specific directory.

• run_command accepts any shell command — use it for git, npm, linters, compilers, etc.

• search_files skips node_modules, dist, and hidden folders automatically.

Contributing

Contributions are welcome — see CONTRIBUTING.md for dev setup, how to run tests, and PR guidelines. This project follows the Contributor Covenant.

Found a security issue? See SECURITY.md — please don't file it as a public issue.

Changelog

See CHANGELOG.md.

License

MIT