Browserbase MCP server

Installing Browserbase

Runs on demand via npx. Nothing to install globally.

claude mcp add browserbase -- npx -y @browserbasehq/mcp-server-browserbase

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

Not sure where the config file lives, or it isn't picking the server up? Config paths for every client.

Requires BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, get these from the maintainer. Never commit them.

What it does

The Browserbase MCP server gives an assistant managed cloud browsers to navigate and automate the web reliably, without running browsers yourself.

Like any MCP server, Browserbase plugs into MCP-compatible assistants (such as Claude and other clients) so the model can use it as a tool , no custom integration code required.

Related Browser & automation MCP servers

• PlaywrightDrive a real browser to navigate and act.
• PuppeteerAutomate a headless Chrome browser.
• Vibium"Selenium for AI", plain-English, self-healing browser tests.
• ApifyRun web scrapers and automation actors.
• Chrome DevToolsLet the assistant debug a live Chrome page.
• StagehandAutomate browsers using natural language instructions.