Data as of

Browser Use MCP Server for Claude Code: Setup & Config

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

What you can do with Browser Use in Claude Code

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

  • Let an MCP assistant navigate websites through browser-use.
  • Connect a stdio-only client through the documented proxy workflow.

Before you start: Browser Use in Claude Code

  • 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 Code configuration

  1. Choose Claude Code configuration scope

    For Browser Use MCP Server, open Project scope: .mcp.json at the repository root. Project JSON: merge into mcpServers; user scope: use the CLI.

  2. Add Browser Use MCP Server to Claude Code

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

  3. Check Browser Use MCP Server in Claude Code

    Browser Use MCP Server: Inspect claude mcp list and /mcp status.

Config file · Project scope: .mcp.json at the repository root

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

CLI (POSIX shell)
claude mcp add-json --scope project 'browser-use-mcp-server' '{"type":"stdio","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 Code

  • If Browser Use MCP Server fails to start, check browser-use-mcp-server, the working directory, and Claude Code's selected scope; inspect claude mcp list and /mcp.
  • Browser Use MCP Server: check OPENAI_API_KEY; keep credentials out of shared .mcp.json.
  • Browser Use MCP Server uses stdio here: Claude Code 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 Code troubleshooting lives in the /clients/claude-code guide.

Browser Use MCP Server — details. Claude Code guide

Frequently asked questions

Register Browser Use MCP Server with the displayed claude mcp add-json --scope project command, or merge the JSON into .mcp.json at the repository root.

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

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

Claude Code'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.

Not stated in the README. It describes browser-control capabilities and launch methods without a named tool inventory.