Browserbase MCP Server is the official Browserbase and Stagehand bridge for giving MCP clients a controllable browser. The current docs describe a hosted Streamable HTTP endpoint served by Browserbase infrastructure plus a self-hostable STDIO server with the same six core tools: start, end, navigate, act, observe, extract, and screenshot. That distinction matters for buyers comparing it with local Playwright MCP options: the value proposition is managed browser sessions, natural-language Stagehand actions, session lifecycle control, recordings/logging, and Browserbase infrastructure rather than a purely local browser driver.
The public README and docs now emphasize both setup paths. The hosted endpoint at mcp.browserbase.com/mcp is recommended for the easiest start and includes Browserbase-hosted capacity, while the open-source Apache-2.0 repository can be installed with npm, run directly, or built as a Docker image. Teams still need Browserbase API credentials, and self-hosted configurations may also need a model API key depending on the Stagehand/model settings. Claims about CAPTCHA, proxy support, geolocation, or reliability should be framed as platform capabilities and plan-dependent infrastructure features, not guaranteed bypass outcomes.
Pricing is tied to Browserbase platform usage. The current pricing page lists Free at $0/month with 3 concurrent browsers, 1 browser hour, 1,000 Search calls, 1,000 Fetch calls, 15-minute sessions, 7-day retention, and $5 in model tokens; Developer at $20/month with 25 concurrent browsers and 100 browser hours; Startup at $99/month with 100 concurrent browsers and 500 browser hours; and custom Scale plans with 250+ concurrent browsers and usage-based allowances. The GitHub repo remains active with about 3.4K stars, so the base page should present it as an open-source server attached to a commercial managed-browser platform.
