Browserbase
Browserbase's hosted browser MCP. Lets Claude drive a real headless Chrome in the cloud, with session recording and proxy support.
Delv Safety Grade: B
Score 73/100 · assessed 2026-04-28
Browserbase is a legitimate vendor offering cloud-hosted headless Chrome automation via MCP. The company is established in the browser automation space with a commercial product. The MCP server is distributed through npm with proper versioning and appears well-maintained. However, the permissions profile is concerning: this grants Claude full browser control including arbitrary navigation, form submission, JavaScript execution, and interaction with any website. The browser runs in Browserbase's cloud, which adds a layer of isolation from your local machine, but the automation capabilities are essentially unrestricted within that browser context. Session recording is a transparency feature but also means all browsing activity is logged server-side. Requires API credentials which adds authentication but also means vendor lock-in. Suitable for controlled automation tasks but represents significant capability that could be misused if Claude is compromised or misdirected.
Lethal Trifecta (prompt-injection exposure)
TWO OF THREECloud headless browser. Same untrusted-input shape as Puppeteer with persistent sessions.
Green flags
- Official vendor product from established browser automation company
- Distributed via npm with proper package management and versioning
- Browser runs in cloud isolation, not on local machine
- Session recording provides audit trail of automation activity
- Requires API authentication, preventing unauthorized use
Red flags
- Full browser control allows arbitrary site navigation and form submission
- Can execute JavaScript and interact with any web content without sandboxing
- Session recording means all browsing activity logged on vendor servers
- Vendor lock-in requires ongoing Browserbase subscription and API access
Permissions requested
Review
Install this if you need Claude to drive a real browser for tasks that break with static scraping or require session state. Skip it if you're just fetching HTML or don't want to pay for hosted browser time. The session recording alone justifies the cost for complex automation workflows.
Good at
- Real headless Chrome with full JavaScript execution, not just HTML snapshots.
- Session recording captures every interaction as video, which makes debugging far easier than parsing logs.
- Proxy support lets you route traffic through specific geos or your own infrastructure.
- Session persistence means you can pause and resume without losing login state or cookies.
- Tight integration with Browserbase's platform means sessions are managed for you, no manual cleanup.
Watch out
- You're paying for hosted browser time, so this isn't suitable for simple HTTP requests or static scraping.
- Vendor-locked to Browserbase's infrastructure. You can't swap in a local Puppeteer instance without rewriting the server.
- If you've never used Browserbase, the session model might feel opaque at first. The MCP server assumes you understand their platform.
- Session timeouts can interrupt long-running tasks if you pause mid-workflow.
Getting started
Works with
Similar MCPs
- Playwright (Microsoft)Microsoft's official Playwright MCP — full browser control, accessibility tree, and click-by-text. The most capable browser MCP.
- PuppeteerHeadless browser control for Claude. Screenshots, form filling, scraping, and interacting with pages that require JavaScript.
- Webpage Screenshot MCPCaptures full-page and element-specific screenshots for UI development feedback, with authentication and system browser support.
- FirecrawlFirecrawl's MCP for high-quality web scraping. Returns clean markdown, handles JS-rendered sites, batch crawling.