---
title: "Browserbase MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/browserbase/
description: "Provides cloud browser sessions for navigation, extraction and reviewed page interactions."
---

# Browserbase MCP: review, setup & limitations · Undominated.ai

> Provides cloud browser sessions for navigation, extraction and reviewed page interactions.

[← Explore all mcp servers](/mcp-servers/)

BROWSER AND AUTOMATION / Browserbase

# Browserbase MCP

Provides cloud browser sessions for navigation, extraction and reviewed page interactions.

 [See setup guidance ↓](#setup)[Original source ↗](https://docs.browserbase.com/integrations/mcp/introduction)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Browserbase
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“The Browserbase MCP server gives any MCP client a browser.”

 [Browserbase · upstream description ↗](https://docs.browserbase.com/integrations/mcp/introduction) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Documents session creation, navigation, observation, extraction and actions with explicit session identifiers.
- Offers a hosted setup for clients that need a browser without managing a local browser process.
- The fetched page is the publisher's own setup note for this server, which is the source the catalogue already cites.
- The transport and any stated account requirement are specific enough to configure a client without guessing a second product.

### A good fit for

 - Extracting information from a page in a controlled cloud browser session
- Testing an authorized web workflow with visible session boundaries
- Connect a client to the endpoint on this page and inspect the live tool list before relying on a tool name.
- Match the credentials and transport on this page, and do not treat unstated tools as available.

### Weigh up before choosing

 - The documented hosted setup passes a Browserbase API key in the connection URL. Keep the real URL out of shared files, logs, tickets and shell history.
- Browser actions can submit forms, send messages or change account data. Review consequential actions before they run.
- Pages, credentials and browsing state are processed in a cloud browser; check the account’s data handling and session settings.
- The former browserbase/mcp-server-browserbase repository is archived and is not treated as the current hosted implementation.
- The acquired current documentation describes session tools; inspect the connected server tool list because hosted releases can change.
- This review did not start the server or call its tools.
- A transport reconnection is not proof that browser cookies and authentication state were destroyed; verify browser-session lifecycle separately.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Current MCP introduction, tool descriptions and setup instructions
- Archive notice in the earlier standalone repository
- Documentation introduction
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The setup documents API-key URL authentication; an OAuth flow is not inferred. The catalogue provides instructions rather than embedding a credential-bearing configuration.
- The configuration examples start a local process and name stdio as the transport.
- Current documentation describes browser session tools and the sessionId required to target an existing session.
- The page documents both Streamable HTTP and a local stdio launch.
- Browser tools accept an explicit sessionId; otherwise they use the transport's current session, which can fail to persist across clients that change Mcp-Session-Id.

### Not established by this review

 - No MCP server or upstream package was installed or run.
- No authenticated account, client handshake, query, write operation or security test was performed.
- The server was not installed or initialised.
- No tools/list or tool call was made.
- A source review is not a runtime or security certification.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://docs.browserbase.com/integrations/mcp/introduction)
 - Follow the official setup guide to form the hosted https://mcp.browserbase.com/mcp URL with your API key in the documented parameter.
- Store that credential-bearing URL only in an appropriate private client configuration.
- Start a bounded session, retain its sessionId for subsequent tools and end the session when the task is complete.

### Before you start

 - A Browserbase account and API key
- A compatible remote MCP client with private credential storage

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "browserbase": {
 "url": "https://mcp.browserbase.com/mcp?browserbaseApiKey=YOUR_BROWSERBASE_API_KEY"
 }
 }
} Copy configuration ↗

### Compatibility

Remote MCP clients

### Transports

Streamable HTTP

### Hosted account connection

 - Start and control cloud browser sessions
- Read visited page contents and perform actions with any session credentials or authenticated browser state

### Cost model

Browserbase account, browser runtime and applicable model usage terms apply; assistant usage is separate. No hosted implementation licence is asserted.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Official setup and capabilities ↗](https://docs.browserbase.com/integrations/mcp/introduction) Checked 2026-10-14 https://docs.browserbase.com/integrations/mcp/introduction Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access, review
- [Official Browserbase MCP setup and authentication ↗](https://docs.browserbase.com/integrations/mcp/setup) Checked 2026-10-14 https://docs.browserbase.com/integrations/mcp/setup Supports: install, limitations, access, review
- [Archived former standalone server ↗](https://github.com/browserbase/mcp-server-browserbase) Checked 2026-10-14 https://github.com/browserbase/mcp-server-browserbase Supports: limitations, review

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Bedrock AgentCore MCP ↗ AWS Labs MCP server whose README says it exposes AgentCore runtime, memory, identity, gateway, policy, browser, and code-interpreter operations through boto3.](/mcp-servers/awslabs-bedrock-agentcore/)[### Bright Data MCP Server ↗ Search-engine results, page scraping, pre-built structured-data scrapers and a remote browser through Bright Data's proxy infrastructure, from a hosted URL or a local npx package.](/mcp-servers/brightdata/)[### Cloudflare Playwright MCP ↗ A Worker-hosted Playwright MCP server for Cloudflare Browser Rendering.](/mcp-servers/cloudflare-playwright/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
