browser-use MCP server

Add the server

claude mcp add browser-use -- uvx browser-use

Fill in your credentials

Replace <X-BROWSER-USE-API-KEY> with your real value. Keep secrets out of any config file you commit.

Verify it's connected

claude mcp list

Sharing it with your team?

Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

Use it in a session

Ask Claude to use the tools this server exposes. It discovers them automatically.

Open your MCP config

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

{
  "mcpServers": {
    "browser-use": {
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}

Fill in your credentials

Replace <X-BROWSER-USE-API-KEY> with your real value. Keep secrets out of any config file you commit.

Restart Claude Desktop

The tools appear under the 🔌 menu once the app reloads.

Create / edit .cursor/mcp.json in your project

{
  "mcpServers": {
    "browser-use": {
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}

Fill in your credentials

Replace <X-BROWSER-USE-API-KEY> with your real value. Keep secrets out of any config file you commit.

Enable it

Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

Add to ~/.codex/config.toml

[mcp_servers.browser-use]
command = "uvx"
args = ["browser-use"]

Fill in your credentials

Replace <X-BROWSER-USE-API-KEY> with your real value. Keep secrets out of any config file you commit.

Run Codex

Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

Edit ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "browser-use": {
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}

Fill in your credentials

Replace <X-BROWSER-USE-API-KEY> with your real value. Keep secrets out of any config file you commit.

Reload

Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

Open Cline → MCP Servers → Configure

Adds to cline_mcp_settings.json.

Add the server

{
  "mcpServers": {
    "browser-use": {
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}

Fill in your credentials

Replace <X-BROWSER-USE-API-KEY> with your real value. Keep secrets out of any config file you commit.

Create .vscode/mcp.json

{
  "servers": {
    "browser-use": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "browser-use"
      ]
    }
  }
}

Fill in your credentials

Replace <X-BROWSER-USE-API-KEY> with your real value. Keep secrets out of any config file you commit.

Start it

VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.