BROWSER AND AUTOMATION / Browserbase
Browserbase MCP
Provides cloud browser sessions for navigation, extraction and reviewed page interactions.
“The Browserbase MCP server gives any MCP client a browser.”
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.
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.
- 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"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://docs.browserbase.com/integrations/mcp/introduction
Supports: summary, upstreamDescription, whySelected, bestFor, install, compatibility, transports, limitations, access, review
https://docs.browserbase.com/integrations/mcp/setup
Supports: install, limitations, access, review
https://github.com/browserbase/mcp-server-browserbase
Supports: limitations, review