What it does

Wraps Browserbase’s cloud browser API as MCP tools. The agent gets create_session, navigate, click, fill, screenshot, extract_text, solve_captcha (paid tier). Each session runs a real browser on Browserbase’s infrastructure, optionally persisting state across calls.

When you actually need it

If playwright-mcp running locally has hit a wall:

1. Scaling. Spinning up 10 browsers locally eats RAM. Spinning up 10 browsers on Browserbase eats your wallet, but doesn’t crash your laptop.
2. Bot-detection. Sites that block obvious automation (Playwright’s default user-agent / fingerprint) sometimes accept Browserbase. Not always, but more often.
3. Captcha-heavy workflows. Browserbase’s captcha-solving (paid) is the only realistic option short of human-in-the-loop.
4. Persistent authenticated sessions. Log in once on Browserbase, reuse the session across multiple agent calls without re-authing.
5. Production agents on small infra. Your Lambda or Cloud Run instance doesn’t need to host Chromium.

Setup

"browserbase": {
  "command": "npx",
  "args": ["-y", "@browserbasehq/mcp"],
  "env": {
    "BROWSERBASE_API_KEY":  "bb_…",
    "BROWSERBASE_PROJECT_ID": "…"
  }
}

You’ll burn free-tier session-minutes quickly during development. Plan for the paid tier if this is going to production.

The catch

You’re outsourcing the browser. That’s the entire benefit and the entire catch.

• Privacy posture changes. Browserbase sees every URL, every page, every form. For your own SaaS dashboards: usually fine (you’re already trusting Cloudflare, AWS, etc.). For competitor sites or PII-handling sites: read their docs.
• Latency floor. Local browsing has a 50-100ms latency floor on click/navigate. Browserbase adds 100-300ms per call (network round-trip + server processing). For interactive workflows this matters.
• Detection arms race. Sites that fingerprint browser sessions sometimes detect Browserbase IP ranges. Workarounds (residential proxies, paid tiers) help but aren’t guaranteed.
• Vendor lock-in. Migrating from Browserbase to playwright-mcp local is a non-trivial code change because Browserbase exposes session-management primitives that local Playwright doesn’t have built in.

For most teams: start with playwright-mcp local. Move to Browserbase only when you’ve genuinely hit a wall the local version can’t overcome.