B
Browserbase MCP
39
Stack Score
Editorial pick✓ Verified workingMCP server
Browserbase MCP
Managed remote browser sessions.
Best for
Best for teams running serious browser automation in production.
At a glance
- Pricing
- open-source
- Setup time
- 20 minutes
- Learning curve
- moderate
- Last verified
- 5/27/2026
What we love
- ✓Browserbase-maintained
- ✓Production-grade remote browsers
- ✓No local headless setup
Where it falls short
- −Per-session cost
- −Browserbase account needed
- −Session-scope discipline
Install & connect
Copy-paste ready
Install
shell
npx -y mcp-remote https://browserbase.run.tools
Config — Claude Desktop
json
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://browserbase.run.tools"]
}
}
}Config — Claude Code
shell
claude mcp add --transport http browserbase https://browserbase.run.tools
Pricing
✓ Pricing verified Jun 14, 20261 tier
Open-source
$0
perpetual
- ✓MIT
Overview
MCP server for Browserbase — spin up managed Playwright sessions in the cloud, persist sessions, debug visually. Browserbase API key.
Key features
- ●Managed Playwright sessions
- ●Session persistence
- ●Visual debugging
- ●Stealth mode
- ●API key
Exposed tools
The MCP-tool names this server exposes. Your agent can invoke any of these when this server is connected.
- startCreate or reuse a Browserbase session.
- endClose the current Browserbase session.
- navigateNavigate to a URL.
- actPerform an action on the page.
- observeObserve actionable elements on the page.
- extractExtract data from the page.
Best use cases
Cloud browser automation
Run Claude-driven Playwright in the cloud without local headless setup.
Persistent session scraping
Maintain logged-in sessions across many runs.
Integrations
Similar tools
See all automation tools →One AI Stack pick every week.
The tool we’d pay for this week, why we’d pay for it, and what we’d skip. No promo spam.