Add the Browserbase MCP server to Windsurf

Config last verified Jun 1, 2026

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

Prerequisites

Windsurf 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 `~/.codeium/windsurf/mcp_config.json`

On Windows the file lives at %USERPROFILE%\.codeium\windsurf\mcp_config.json.

2. Add this configuration

Add to ~/.codeium/windsurf/mcp_config.json

~/.codeium/windsurf/mcp_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 Windsurf and confirm the Browserbase tools load.

Gotchas

Windsurf's Cascade reads MCP servers from an "mcpServers" object in ~/.codeium/windsurf/mcp_config.json. Unlike most clients, remote servers are configured with the "serverUrl" field rather than "url", so a config that uses "url" silently fails to connect. Native remote transport is supported without an OAuth flow.

← Back to the Browserbase MCP server