Primary capability
Natural-language actions
Documentation ↗MCP server / browser automation / source-linked
Browserbase MCP
Current Browserbase hosted MCP for Stagehand cloud sessions; old repo archived. The hosted service moves browser execution and session state off the local machine. That can simplify operations, but it also makes credentials, session retention and provider account terms part of the decision.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Current Browserbase hosted MCP for Stagehand cloud sessions; old repo archived. The hosted service moves browser execution and session state off the local machine. That can simplify operations, but it also makes credentials, session retention and provider account terms part of the decision.
Implementation source ↗
Current Browserbase hosted MCP for Stagehand cloud sessions; old repo archived. The hosted service moves browser execution and session state off the local machine. That can simplify operations, but it also makes credentials, session retention and provider account terms part of the decision.
Implementation source ↗
Current Browserbase hosted MCP for Stagehand cloud sessions; old repo archived. The hosted service moves browser execution and session state off the local machine. That can simplify operations, but it also makes credentials, session retention and provider account terms part of the decision.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- hosted Streamable HTTP; local stdio
- Authentication
- Browserbase API key
Use the official endpoint/package, store secrets outside committed config, and review returned tools before use.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
https://mcp.browserbase.com/mcpWhat it actually exposes.
Concrete capabilities with maintainer sources.
Secondary capability
Session lifecycle and extraction
Documentation ↗Workflow fit
Choose by transport, auth and state needs.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
Signal: local install build breakage
A local-development install of Browserbase MCP 2.4.3 reported peer dependency overrides and a TypeScript build failure because a capabilities property no longer matched the SDK type.
“npm install ... Found 1 error in src/index.ts.”Open community source ↗
Signal: indirect prompt injection
The advisory warns that extracted web content can inject instructions into the agent context and cause unwanted navigation, form submission or data exfiltration.
“attacker-controlled content ... can contain prompt injection payloads”Open community source ↗
Signal: hosted convenience vs antibot limits
The discussion frames Browserbase as a way to avoid local browser configuration, while commenters note that bot-blocked sites can still stop Browserbase, Playwright and Puppeteer alike.
“why should we pay for browsebase?”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Proposed decision workflow (proposed; not tested)
Suggested evaluation, not an observed test result.
- Choose a bounded public test task.
- Record setup, tool calls and source URLs.
- Review result, cost and failure boundaries.
What to inspect: Suggested evaluation; not tested.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Requires key and session management.
Boundary reference ↗Legacy repo is archived.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
Suggested evaluation; not tested.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Playwright MCP | Editorial inference: you need a different workflow. | Compare transport, auth and state tradeoffs. Documentation ↗ |
| Puppeteer MCP | Editorial inference: you need another workflow. | Compare scope and operational tradeoffs. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
What should I verify first?
Confirm current endpoint, auth and returned tools.
Documentation ↗
Is this page a test result?
No; the workflow is a proposed editorial comparison.
Documentation ↗
Source trail.
Maintainer documentation used in this record.