Delv
Official (Vendor)Slow· 1mo4.3by Browserbase

Browserbase

Browserbase's hosted browser MCP. Lets Claude drive a real headless Chrome in the cloud, with session recording and proxy support.

B
Safety & Trust

Delv Safety Grade: B

Score 73/100 · assessed 2026-04-28

Maintainer75
Permissions40
Supply chain85
Transparency80
Incidents100

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 THREE
Private dataNo
Reads secrets, credentials, private files
Untrusted inputYes
Ingests web pages, PRs, issues, emails
External commsYes
Can send data outbound

Cloud 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

Browser controlOutbound networkAccess secretsExternal LLM call
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Review

Browserbase's MCP server gives Claude control of a real headless Chrome instance running in the cloud. Instead of scraping HTML or parsing DOM snapshots, you get a full browser with JavaScript execution, session persistence, and built-in recording. I've used it to automate multi-step workflows that break with traditional scraping: logging into dashboards, filling forms that validate client-side, or capturing rendered charts that only exist after React hydrates. The setup is straightforward if you already have a Browserbase account. You drop your API key and project ID into environment variables, add the server to your Claude Desktop config, and Claude can immediately spin up sessions. The real win is session recording. Every interaction is captured as a video, which makes debugging far easier than staring at error logs. Proxy support is there if you need geo-specific browsing or want to route through your own infrastructure. It's genuinely good for tasks where you need a real browser: testing web apps, scraping SPAs that rely on JavaScript, automating workflows across multiple sites with logins. I'd reach for this when I need to interact with a site as a human would, not just fetch static HTML. The session persistence means you can pause, inspect, and resume without losing state. Quirks: you're paying for hosted browser time, so this isn't free compute. If your task can be solved with a simple HTTP request or a static scraper, you're overpaying. The MCP server itself is lean, which is good, but it assumes you understand Browserbase's session model. If you've never used their platform, the abstraction might feel opaque at first. Also, this is tightly coupled to Browserbase's infrastructure. You can't swap in a local Puppeteer instance without rewriting the server. Skip this if you're just fetching public HTML or if you don't want to manage API credits. But if you're automating browser-dependent tasks and want Claude to handle the interaction layer, this is the cleanest option I've found. It's vendor-locked, but the vendor actually knows what they're doing.
Verdict

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

1. Sign up for a Browserbase account and grab your API key and project ID from the dashboard. 2. Set BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID as environment variables in your shell or add them to your Claude Desktop config. 3. Add the MCP server to your Claude Desktop config using the npx command: npx -y @browserbasehq/mcp. 4. Restart Claude Desktop and verify the server appears in the MCP section. Ask Claude to 'open a browser session and navigate to example.com' to test. 5. Watch out for session timeouts. If you pause mid-task, the session may expire, and you'll need to restart from scratch.

Works with

Claude DesktopCursorCline

Similar MCPs