Browser Use MCP Server for Cursor: Setup & Config

What you can do with Browser Use in Cursor

A browser-use bridge with live viewing and both asynchronous and completion-wait browsing workflows.

• Run browser tasks asynchronously or wait for completion.
• Connect a stdio-only client through the documented proxy workflow.

Before you start: Browser Use in Cursor

• Python and uv
• Playwright and its Chromium browser dependencies
• mcp-proxy for stdio mode
• A built and globally installed browser-use-mcp-server package

The README installs mcp-proxy with uv, synchronizes dependencies, installs Chromium through Playwright, builds a wheel, and installs it globally before this launch. Its source SSE alternative uses uv run server --port 8000 and http://localhost:8000/sse. CHROME_PATH and PATIENT are optional settings.

Browser Use Cursor configuration

1. Choose Cursor configuration scope

   For Browser Use MCP Server, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add Browser Use MCP Server to Cursor

   Use the browser-use-mcp-server entry below in mcpServers. Keep Browser Use MCP Server's documented stdio connection fields and your other Cursor entries.

3. Check Browser Use MCP Server in Cursor

   Browser Use MCP Server: Enable in Cursor’s MCP settings; inspect tools.

{
  "mcpServers": {
    "browser-use-mcp-server": {
      "command": "browser-use-mcp-server",
      "args": [
        "run",
        "server",
        "--port",
        "8000",
        "--stdio",
        "--proxy-port",
        "9000"
      ],
      "env": {
        "OPENAI_API_KEY": "<OpenAI API key>"
      }
    }
  }
}

Troubleshooting Browser Use in Cursor

• Cursor must find browser-use-mcp-server for Browser Use MCP Server. Enable the project/user entry in MCP settings and inspect its tools.
• Review OPENAI_API_KEY for Browser Use MCP Server before sharing project .cursor/mcp.json; project scope travels with the repository.
• Browser Use MCP Server uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
• Known limitation: Stdio mode requires mcp-proxy and package build/install steps.
• Known limitation: Requires Playwright browser setup and an OpenAI API key.
• Known limitation: Docker's documented VNC default should be replaced for protected viewing.
• General Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions