Browserbase MCP Server

The Browserbase MCP Server is the official Model Context Protocol server from Browserbase, Inc. It gives any compatible MCP client a full cloud browser. At its core is [Stagehand](https://docs.stagehand.dev/), an open-source framework that translates natural-language commands into precise browser actions. The direct product link to the official documentation is https://docs.browserbase.com/integrations/mcp/introduction; the source repository lives at https://github.com/browserbase/mcp-server-browserbase (archived, Apache-2.0). The recommended path is the hosted Streamable HTTP endpoint at https://mcp.browserbase.com/mcp.

What is the Browserbase MCP Server?

The Model Context Protocol (MCP) is an open standard that connects AI applications with external tools and data sources. The Browserbase MCP Server implements this standard by connecting AI clients such as Claude, Codex, or Cursor directly to a cloud browser. Instead of installing, starting, and managing a browser themselves, AI clients send a natural-language command to the MCP server — for example "click the login button" or "extract all product prices" — and receive the result in a structured format.

According to the provider, two operation modes are available: the hosted Streamable HTTP endpoint at https://mcp.browserbase.com/mcp, which runs on Browserbase infrastructure and includes Google Gemini 2.5 Flash Lite for Stagehand processing, and a local STDIO mode launched via npx @browserbasehq/mcp that requires your own model API keys.

Note: The GitHub repository browserbase/mcp-server-browserbase is archived and maintained per the README as a historical reference implementation. The hosted server at https://mcp.browserbase.com/mcp is the provider's recommended and actively maintained option.

Prerequisites

For the hosted mode (recommended): an active Browserbase account, a Browserbase API key, and a Project ID created in the [Browserbase Dashboard](https://www.browserbase.com/overview). Node.js does not need to be installed locally; the client communicates with the hosted endpoint via Streamable HTTP directly. If your MCP client does not support native SHTTP, use mcp-remote as a bridge (npx mcp-remote https://mcp.browserbase.com/mcp).

For the local STDIO mode, Node.js is required (current LTS version recommended). For the default model (Google Gemini 2.5 Flash Lite), a Gemini API key is needed. To use a different model such as Claude Sonnet or GPT-4o, pass the provider and key via --modelName and --modelApiKey.

Features and tools

The Browserbase MCP Server exposes six core tools according to the README and official documentation:

start – Creates a new Browserbase session or reuses an existing one. This step initialises the browser environment including cookies, session state, and optional configuration (proxies, stealth mode, keep-alive).

end – Cleanly closes the current Browserbase session and releases resources. Important for cost efficiency and security, since open sessions continue to consume resources.

navigate – Navigates the browser to a specified URL. Automatically waits for the complete page load before returning the result. Input: { url: string }.

act – Executes a natural-language action on the current page. Stagehand translates the command into precise browser interactions: clicks, text inputs, scroll actions, and more. Input: { action: string }.

observe – Analyses the current page and returns a list of all interactive elements that can be acted on. Useful for multi-step automations where the agent needs to explore the page first. Input: { instruction: string }.

extract – Extracts structured data from the current page — product prices, tables, contact details, articles, and more. Works even without an explicit instruction; the AI identifies the relevant content autonomously. Input: { instruction?: string }.

Setup

Hosted mode (Streamable HTTP, recommended):

For clients with native SHTTP support, the following configuration is sufficient:

{
  "mcpServers": {
    "browserbase": {
      "type": "http",
      "url": "https://mcp.browserbase.com/mcp"
    }
  }
}

Clients without native SHTTP support use mcp-remote:

{
  "mcpServers": {
    "browserbase": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.browserbase.com/mcp"]
    }
  }
}

Local STDIO mode:

{
  "mcpServers": {
    "browserbase": {
      "command": "npx",
      "args": ["@browserbasehq/mcp"],
      "env": {
        "BROWSERBASE_API_KEY": "",
        "BROWSERBASE_PROJECT_ID": "",
        "GEMINI_API_KEY": ""
      }
    }
  }
}

API keys are created in the [Browserbase Dashboard](https://www.browserbase.com/overview). The Project ID is visible in the dashboard under project settings.

Security

The Browserbase MCP Server grants the AI client access to a real cloud browser. This means the agent can fill forms, click buttons, and access authenticated areas if session credentials are stored. Key points to consider:

API keys and Project IDs should only be placed in environment variables or secure client configurations — never in publicly visible files or prompts. The --proxies flag should only be enabled when the target website permits proxy usage. Prompt injection via manipulated web page content is a known risk for MCP servers with browser access; agent actions should therefore be reviewed before any productive steps. The --verified flag (Verified Identity) is per the provider available exclusively for Scale Plan users and should not be enabled without deliberate planning.

FAQ

Is the Browserbase MCP Server free? The source repository is Apache-2.0 licensed. Using the hosted endpoint depends on the Browserbase plan chosen. Current pricing is published on Browserbase's own pricing page.

What is Stagehand? Stagehand is an open-source framework from Browserbase that translates natural-language commands into browser actions. According to the provider, it achieves top positions in leading web automation benchmarks and is the technical core of the Browserbase MCP Server.

Why is the GitHub repository archived? The repository browserbase/mcp-server-browserbase serves per the README as a historical reference implementation. The actively maintained path is the hosted endpoint https://mcp.browserbase.com/mcp or the npm package @browserbasehq/mcp.

How current are the GitHub stars? The GitHub API reported exactly 3,404 stars on 2026-09-08. That number is a point-in-time snapshot of repository popularity and is not a security or quality promise.

Can I use a different AI model than Gemini? Yes, in local STDIO mode. With --modelName and --modelApiKey, alternative models such as Claude Sonnet or GPT-4o can be configured, provided Stagehand supports them. In hosted mode, Browserbase provides the model according to the provider.

Browserbase account, API key and Project ID (Dashboard), compatible MCP client; for local mode additionally Node.js and a Gemini or other model API key.

Hosted (recommended): {"mcpServers":{"browserbase":{"type":"http","url":"https://mcp.browserbase.com/mcp"}}}. Local (STDIO): npx @browserbasehq/mcp with BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID, and GEMINI_API_KEY as environment variables.

npx @browserbasehq/mcp

Browserbase API key and Project ID for all modes; Gemini API key (or other model key) for local STDIO mode.

Full browser control within the Browserbase account scope: navigation access, form filling, data extraction, and session-based authentication.

Browser sessions run on Browserbase infrastructure; extracted data is returned to the MCP client. In hosted mode, Browserbase per the provider also processes the AI model requests (Gemini).

Browser access enables destructive actions (forms, clicks, authentication); prompt injection via web page content; API keys in insecure configurations.