Add the Browserbase MCP server to Claude Desktop

Config last verified Jun 1, 2026

The exact config to run Browserbase in Claude Desktop — paste it in, restart, and the tools load.

Prerequisites

Claude Desktop installed.
BROWSERBASE_API_KEY — Browserbase API key.
BROWSERBASE_PROJECT_ID — Browserbase project ID.
GEMINI_API_KEY — LLM key used by Stagehand's default model.

Setup

1. Open `~/Library/Application Support/Claude/claude_desktop_config.json`

On Windows the file lives at %APPDATA%\Claude\claude_desktop_config.json.

2. Add this configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json

~/Library/Application Support/Claude/claude_desktop_config.json

json

{
  "mcpServers": {
    "browserbase": {
      "command": "npx",
      "args": [
        "@browserbasehq/mcp"
      ],
      "env": {
        "BROWSERBASE_API_KEY": "<BROWSERBASE_API_KEY>",
        "BROWSERBASE_PROJECT_ID": "<BROWSERBASE_PROJECT_ID>",
        "GEMINI_API_KEY": "<GEMINI_API_KEY>"
      }
    }
  }
}

3. Restart Claude Desktop and confirm the Browserbase tools load.

Gotchas

Claude Desktop reads MCP servers from an "mcpServers" object, but the config file is stdio-only: it cannot dial a remote URL directly. To reach a remote server you bridge it locally by running "npx mcp-remote <url>" as the command. Native remote Connectors exist on paid plans, but not through this config file, so the bridge is the portable path.

← Back to the Browserbase MCP server