MCP100 Assessment

Editorial verdict

Promising hosted browser automation, but it remains on the Shortlist until session isolation, sensitive browser data exposure, action boundaries, hosted usage behavior, and failure handling are independently reviewed.

Reviewed July 30, 2026

Task Fit

Mapped

Specialized workflows

Trust

Status warning

open_world_browser_actions_without_mcp_level_domain_or_read_only_controls

Maintenance

Date unavailable

No dated repository or package update is currently stored.

Popularity

Signals unavailable

No independently comparable adoption metric is currently stored.

Best for

Cloud browser automation and session-based web interaction.

Not ideal for

Production use before the documented maturity gaps are resolved

Avoid if

The connected identity is broader than the task requires
Tool calls cannot be reviewed before consequential mutations

Trade-offs

The former self-hosted repository is archived, so hosted maintenance transparency and migration stability need review.

Evidence scope

Evidence

Current source snapshot

Popularity

3.4k shared-repository stars · not MCP-specific

18.5k local-package downloads / 30 days

Repository identity: browserbase/mcp-server-browserbase

Package identity: @browserbasehq/mcp

Official local npm package @browserbasehq/mcp: 18,523 downloads / 30 days · hosted Browserbase MCP usage not included.

Stars observed September 24, 2026 · Downloads observed September 8, 2026

Archived 2026-07-20; historical adoption only, not current hosted maintenance/ranking.

Reviewed legacy_local_distribution_if_present; context only and not exact MCP ranking evidence.

Maintenance

Publisher activity observed September 24, 2026

Current source snapshot

Trust review

Source relationship: First-party MCP

Reviewed July 30, 2026

Sources

GitHub repository ↗Official documentation ↗GitHub releases ↗

Supporting evidence (2)

Evidence source ↗Source file: setup.mdx ↗

Evidence-backed setup

Install & Agents

Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.

Claude Code

Streamable HTTP

MCP100 logic checked

claude mcp add --transport http browserbase "https://mcp.browserbase.com/mcp"

The publisher connection details were combined with this client's official MCP transport configuration; installation was not executed by MCP100.

Verify safely: Reconnect Claude Code, complete the publisher OAuth or authentication flow if prompted, confirm browserbase tools are listed, and perform one read-only test.

Uninstall and revoke

Remove browserbase from Claude Code, clear its stored MCP OAuth credentials, and revoke the publisher authorization if it is no longer needed.

Evidence & methodology

Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.

Evidence checked 2026-08-12

Evidence 1 ↗Evidence 2 ↗

Read additional publisher installation details

From the publisher README

Publisher installation details

Original client setup and configuration retained from the publisher documentation.

View original README ↗

Publisher-documented clients

Claude DesktopGemini CLI

These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.

Installation Methods

Use your MCP client config:

{
  "mcpServers": {
    "browserbase": {
      "url": "https://mcp.browserbase.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BROWSERBASE_API_KEY"
      }
    }
  }
}

For custom models, include modelName and modelApiKey:

{
  "mcpServers": {
    "browserbase": {
      "url": "https://mcp.browserbase.com/mcp?modelName=openai/gpt-4.1&modelApiKey=YOUR_MODEL_API_KEY",
      "headers": {
        "Authorization": "Bearer YOUR_BROWSERBASE_API_KEY"
      }
    }
  }
}

Install the dependencies and build the project

npm install && npm run build

</Step>

<Step title="Choose your transport method">
You can run locally using either STDIO or [Streamable HTTP](https://modelcontextprotocol.io/specification/2025-03-26/basic/transports#streamable-http).

<Tabs>
<Tab title="STDIO">
Add the following to your MCP Config JSON file:

```json
{
  "mcpServers": {
    "browserbase": {
      "command": "node",
      "args": ["/path/to/mcp-server-browserbase/cli.js"],
      "env": {
        "BROWSERBASE_API_KEY": "your_api_key",
        "GEMINI_API_KEY": "your_gemini_api_key"
      }
    }
  }
}

node cli.js --port 8931

Then add this to your MCP Config JSON file:

{
  "mcpServers": {
    "browserbase": {
      "url": "http://localhost:8931/mcp",
      "env": {
        "BROWSERBASE_API_KEY": "your_api_key",
        "GEMINI_API_KEY": "your_gemini_api_key"
      }
    }
  }
}

Loading optional publisher installation details…

Capability

What it does

Run managed browser sessions through Browserbase's hosted MCP endpoint.

Browser AutomationSoftware & Technology

Representative uses

Cloud browser automation and session-based web interaction.

Important limits

Production use before the documented maturity gaps are resolved

Tools6 toolsView tools

start
Start or reuse a Browserbase browser session.
end
Close the active Browserbase session.
navigate
Navigate the browser to a URL.
act
Perform a natural-language action on the current page.
observe
Find actionable elements on the current page.
extract
Extract structured information from the current page.

Session, model, proxy, and browser options change execution behavior but not the documented six top-level tools.

Source: Official documentation

Context Footprint

~1.2K estimated schema tokens

Context impact: Low

Estimated token footprint of the MCP tool schemas exposed to the agent.

Approx. estimate

~1,200 schema tokens is an Approx. catalog/reference estimate, not Runtime Verified.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: The hosted server uses Browserbase account authentication.
Permissions: Browserbase project credentials, session settings, and account limits govern execution.
Data handling: Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive browser automation information.
Cost: The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.
Risk and cautions: The former self-hosted repository is archived, so hosted maintenance transparency and migration stability need review. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.

Related reviewed MCPs

Other options

Playwright MCP

MCP100 Recommended

Let AI clients inspect and automate web browsers with Playwright.

Choose this instead if

Choose Playwright MCP instead if inspecting and testing web interfaces through accessibility snapshots.

Let AI clients inspect and automate web browsers with Playwright.

Compare with Browserbase Hosted MCP Server View Playwright MCP details

browserstack

MCP100 Recommended

Run and investigate BrowserStack real-device and browser testing workflows.

Choose this instead if

Choose browserstack instead if cross-browser and real-device test execution, debugging, and result analysis.

Run and investigate BrowserStack real-device and browser testing workflows.

Compare with Browserbase Hosted MCP Server View browserstack details

Codebase Memory MCP

MCP100 Recommended

Codebase knowledge graph for AI agents — 159 languages, sub-ms queries, 99% fewer tokens.

Choose this instead if

Choose Codebase Memory MCP instead if repository indexing, symbol search, call-path tracing, impact analysis, and architecture queries across many languages.

Recommended after reviewed 2026-09-25 admission dossier: all_current_selected_gates_pass.

Compare with Browserbase Hosted MCP Server View Codebase Memory MCP details

Read publisher documentation

Publisher documentation

Publisher README

Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.

View original README ↗

title: "Browserbase MCP Server Setup" sidebarTitle: "Setup" description: "Add the Browserbase MCP Server to your MCP client"

import { V3Banner } from '/snippets/v3-banner.mdx';

Quick Installation

You can also add Browserbase MCP to Claude Code with a single command. If your client supports HTTP request headers, prefer Authorization: Bearer YOUR_BROWSERBASE_API_KEY; otherwise, use the legacy query-parameter fallback:

claude mcp add --transport http browserbase "https://mcp.browserbase.com/mcp?browserbaseApiKey=YOUR_BROWSERBASE_API_KEY"

We support both local STDIO and hosted Streamable HTTP (SHTTP). We recommend hosted Streamable HTTP for most users.

Endpoint

Hosted Streamable HTTP endpoint (served on Browserbase infrastructure):

https://mcp.browserbase.com/mcp

Prerequisites

Then copy your API Key directly from the input.

Authentication and Query Parameters (Hosted Streamable HTTP)

Required for tool calls

Optional

Query Param	Type	Behavior
`modelName`	string	Defaults to `google/gemini-2.5-flash-lite`
`modelApiKey`	string	Required when `modelName` is non-default
`keepAlive`	boolean string	`"true"` or `"false"`
`proxies`	boolean string	`"true"` or `"false"`
`verified`	boolean string	`"true"` or `"false"`

Available Tools

No input parameters required.

Local Command-Line Flags

Flag	Description
`--proxies`	Enable Browserbase proxies for the session
`--verified`	Enable Browserbase Verified Identity (Scale Plan only)
`--keepAlive`	Enable Browserbase Keep Alive Session
`--contextId <contextId>`	Specify a Browserbase Context ID to use
`--persist [boolean]`	Whether to persist the Browserbase context (default: true)
`--port <port>`	Port to listen on for HTTP or Streamable HTTP transport
`--host <host>`	Host to bind server to (default: localhost, use 0.0.0.0 for all interfaces)
`--browserWidth <width>`	Browser viewport width (default: 1024)
`--browserHeight <height>`	Browser viewport height (default: 768)
`--modelName <model>`	The model to use for Stagehand (default: google/gemini-2.5-flash-lite)
`--modelApiKey <key>`	API key for the custom model provider (required when using custom models)
`--experimental`	Enable experimental features (default: false)

Verify Installation

FAQ

What can Browserbase Hosted MCP do?

Run managed browser sessions through Browserbase's hosted MCP endpoint.

Can Browserbase MCP run managed browser sessions for an AI agent?

Yes. The official hosted MCP can start and end browser sessions, navigate, act on pages, observe elements, and extract page content. Session, model, proxy, and browser options change execution behavior but not the documented top-level tool set.

Does Browserbase MCP work with Codex?

Yes. MCP100 reviewed an evidence-backed setup for Codex, but has not independently verified it with a live runtime test.

Is this an official MCP?

Browserbase is listed as First-party MCP in MCP100’s current evidence.

Current official resources:

Promising hosted browser automation, but it remains on the Shortlist until session isolation, sensitive browser data exposure, action boundaries, hosted usage behavior, and failure handling are independently reviewed.

Best for

Not ideal for

Avoid if

Trade-offs

Evidence

Popularity

Maintenance

Trust review

Sources

Install & Agents

Claude Code

Publisher installation details

Installation Methods

Install the dependencies and build the project

What it does

Representative uses

Important limits

Context Footprint

Access & risk

Other options

Playwright MCP

browserstack

Codebase Memory MCP

Publisher README

title: "Browserbase MCP Server Setup" sidebarTitle: "Setup" description: "Add the Browserbase MCP Server to your MCP client"

Quick Installation

Endpoint

Prerequisites

Authentication and Query Parameters (Hosted Streamable HTTP)

Required for tool calls

Optional

Available Tools

Local Command-Line Flags

Verify Installation

Further Reading

FAQ

Publisher installation details

Installation Methods

Install the dependencies and build the project

Publisher README

title: "Browserbase MCP Server Setup" sidebarTitle: "Setup" description: "Add the Browserbase MCP Server to your MCP client"

Quick Installation

Endpoint

Prerequisites

Authentication and Query Parameters (Hosted Streamable HTTP)

Required for tool calls

Optional

Available Tools

Local Command-Line Flags

Verify Installation

Further Reading