cursor-browser-bridge

Cursor Browser Bridge exposes a set of MCP tools that let Claude Code (or any MCP client) automate Cursor IDE's embedded browser. The bridge translates MCP JSON-RPC calls into HTTP requests to the Cursor extension's local server, enabling commands such as navigating to URLs, taking snapshots, clicking elements by reference, filling and typing into fields, and querying network activity or console messages. The available tools cover browser navigation, element interactions, viewport control, and information gathering (e.g., accessibility trees, network logs, and console output), effectively giving Claude Code full automation capabilities over Cursor's built-in Simple Browser.

To use it, start the MCP bridge (node mcp-bridge.js) so Claude Code can connect over stdio using MCP. The extension runs a local HTTP server on a random port and exposes Cursor browser controls via HTTP endpoints. The MCP bridge forwards tool invocations from Claude Code to that HTTP server, translating them into actions in the Cursor browser. After starting, reload Claude Code if necessary and verify that the bridge registers with your MCP client (e.g., via claude mcp list).

Prerequisites:

• Node.js (recommended LTS)
• A working clone of this repository: git clone https://github.com/VectorlyApp/cursor-browser-bridge.git

Install and run the MCP bridge:

1. Navigate to the project folder:

cd cursor-browser-bridge

2. Install dependencies (if any) and ensure the bridge script is accessible. If this project uses npm, you can install dependencies with:

npm install

3. Start the MCP bridge (the bridge speaks MCP over stdio and expects to be launched by Claude Code or another MCP client):

node mcp-bridge.js

4. Ensure Cursor extension and environment are ready. Reload Cursor window as described in the project README when you install or update the extension.

5. Optional: verify the bridge is listening by connecting the MCP client and attempting a health check as described in troubleshooting (e.g., ensure the extension port file exists and curl the health endpoint).

Prerequisites summary: Node.js installed, access to the cursor-browser-bridge project, and the Cursor IDE with the Browser Bridge extension installed and activated.

Tips and troubleshooting:

• If the MCP bridge cannot connect, verify that /tmp/cursor-browser-bridge-port exists and contains a port number, and try curling http://127.0.0.1:$(cat /tmp/cursor-browser-bridge-port)/health to confirm ok status.
• After updating extension files, reload the Cursor window to pick up changes.
• If tools don’t appear in Claude Code, restart Claude Code and verify the server is registered with claude mcp list.
• For flaky interactions (e.g., browser_fill or browser_click), take a fresh snapshot (browser_snapshot) to refresh element refs, or use browser_evaluate for custom JS as a fallback.
• The bridge logs to the Output/Browser Bridge channel in VS Code; check there for errors if the MCP bridge fails to activate.