Data as of

Browser Use MCP Server for Claude Desktop: Setup & Config

Browser Use MCP Server connects Claude Desktop to browser-use for browser control.

What you can do with Browser Use in Claude Desktop

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

  • Let an MCP assistant navigate websites through browser-use.
  • Watch an automated browsing session through VNC.

Before you start: Browser Use in Claude Desktop

  • 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 Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For Browser Use MCP Server, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add Browser Use MCP Server to Claude Desktop

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

  3. Check Browser Use MCP Server in Claude Desktop

    Browser Use MCP Server: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "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 Claude Desktop

  • Fully quit and reopen Claude Desktop for Browser Use MCP Server. If browser-use-mcp-server is missing, check the desktop process's PATH, which may differ from your terminal.
  • In Claude Desktop's Browser Use MCP Server entry, check OPENAI_API_KEY. Keep secrets out of shared screenshots and repositories.
  • Browser Use MCP Server uses stdio here: Claude Desktop 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 Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Browser Use MCP Server — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads Browser Use MCP Server from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's browser-use-mcp-server example uses stdio.

Browser Use MCP Server's Claude Desktop configuration invokes browser-use-mcp-server.

Claude Desktop's Browser Use MCP Server example references OPENAI_API_KEY. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Yes. VNC streaming is documented, including Docker port exposure and a noVNC viewer workflow.

The README requires mcp-proxy, plus building and globally installing the server package before using its stdio launch command.