MCP ServerHTTPOfficialv2.2.0

Smithery Browserbasehq MCP Browserbase MCP Server

Automate web browser interactions and data extraction using cloud-hosted Browserbase and Stagehand. Ideal for LLM applications that need to navigate websites, observe page elements, and extract structured data.

ai.smithery/browserbasehq-mcp-browserbase

Hosted URL

https://server.smithery.ai/@browserbasehq/mcp-browserbase/mcp

Transport

HTTP

Auth

No auth required

Smithery Browserbasehq MCP Browserbase repository at a glance

Live signal from GitHub, refreshed weekly.

Stars

3,345

Last commit

May 7, 2026

License

Apache-2.0

Language

TypeScript

What the Smithery Browserbasehq MCP Browserbase MCP server does

How models use it and what it is built for.

Automate web browser interactions and data extraction using cloud-hosted Browserbase and Stagehand. Ideal for LLM applications that need to navigate websites, observe page elements, and extract structured data.

Connect to Smithery Browserbasehq MCP Browserbase

Hosted endpoint — paste into any MCP client.

https://server.smithery.ai/@browserbasehq/mcp-browserbase/mcp

Resources

Where to find authoritative docs and source for Smithery Browserbasehq MCP Browserbase.

Example prompts for Smithery Browserbasehq MCP Browserbase

Paste any of these into Agent Studio after connecting Smithery Browserbasehq MCP Browserbase.

  • Navigate to example.com and extract all product prices from the page
  • Click the login button and fill in the email field with my credentials
  • Observe what interactive elements are available on this page and describe them
  • Extract the table data from the current page and format it as JSON

Documentation from project README

View on GitHub

Excerpted from the project's README — boilerplate sections (license, changelog, contributing) omitted for clarity.

Browserbase MCP Server

cover

The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. Whether you're building an AI-powered IDE, enhancing a chat interface, or creating custom AI workflows, MCP provides a standardized way to connect LLMs with the context they need.

This server provides cloud browser automation capabilities using Browserbase and Stagehand. It enables LLMs to interact with web pages, extract information, and perform automated actions.

This is a self-hostable version of the Browserbase hosted MCP server with the same tools and functionality. We recommend using the hosted version for the easiest setup.

Tools

This server exposes 6 tools that match the hosted Browserbase MCP server:

Tool Description Input
start Create or reuse a Browserbase session (none)
end Close the current Browserbase session (none)
navigate Navigate to a URL { url: string }
act Perform an action on the page { action: string }
observe Observe actionable elements on the page { instruction: string }
extract Extract data from the page { instruction?: string }

How to Setup

We currently support 2 transports for our MCP server, STDIO and SHTTP. We recommend you use SHTTP with our hosted MCP server to take advantage of the server at full capacity.

SHTTP (Hosted MCP):

Use the Browserbase hosted MCP server at https://mcp.browserbase.com/mcp. This is the easiest way to get started -- we host the server and provide the LLM costs for Gemini, the best performing model in Stagehand.

For full setup instructions, see the Browserbase MCP documentation.

If your client supports SHTTP:

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

If your client doesn't support SHTTP:

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

STDIO (Self-Hosted):

You can either use our server hosted on NPM or run it completely locally by cloning this repo.

Note: If you want to use a different model you have to add --modelName to the args and provide that respective key as an arg. More info below.

To run via NPM (Recommended)

Go into your MCP Config JSON and add the Browserbase Server:

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

That's it! Reload your MCP client and you're ready to go.

To run 100% local:

Option 1: Direct installation

git clone https://github.com/browserbase/mcp-server-browserbase.git
cd mcp-server-browserbase
npm install && npm run build

Option 2: Docker

git clone https://github.com/browserbase/mcp-server-browserbase.git
cd mcp-server-browserbase
docker build -t mcp-browserbase .

Then in your MCP Config JSON run the server:

Using Direct Installation

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

Using Docker

{
  "mcpServers": {
    "browserbase": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BROWSERBASE_API_KEY",
        "-e",
        "BROWSERBASE_PROJECT_ID",
        "-e",
        "GEMINI_API_KEY",
        "mcp-browserbase"
      ],
      "env": {
        "BROWSERBASE_API_KEY": "",
        "BROWSERBASE_PROJECT_ID": "",
        "GEMINI_API_KEY": ""
      }
    }
  }
}

Configuration

The Browserbase MCP server accepts the following command-line flags:

Flag Description
--proxies Enable Browserbase proxies for the session
--verified Enable Browserbase Verified Identity (Only for Scale Plan Users)
--advancedStealth Deprecated alias for --verified
--keepAlive Enable Browserbase Keep Alive Session
--contextId <contextId> Specify a Browserbase Context ID to use
--persist Whether to persist the Browserbase context (default: true)
--port <port> Port to listen on for HTTP/SHTTP 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)

These flags can be passed directly to the CLI or configured in your MCP configuration file.

Note: These flags can only be used with the self-hosted server (npx @browserbasehq/mcp or Docker).

Model Configuration

Stagehand defaults to using Google's Gemini 2.5 Flash Lite model, but you can configure it to use other models like GPT-4o, Claude, or other providers.

Important: When using any custom model (non-default), you must provide your own API key for that model provider using the --modelApiKey flag.

{
  "mcpServers": {
    "browserbase": {
      "command": "npx",
      "args": [
        "@browserbasehq/mcp",
        "--modelName",
        "anthropic/claude-sonnet-4.5",
        "--modelApiKey",
        "your-anthropic-api-key"
      ],
      "env": {
        "BROWSERBASE_API_KEY": "",
        "BROWSERBASE_PROJECT_ID": ""
      }
    }
  }
}

Note: The model must be supported in Stagehand. Check out the docs here.

Continue reading on GitHub

Smithery Browserbasehq MCP Browserbase MCP server — FAQ

Common questions about connecting and running Smithery Browserbasehq MCP Browserbase.

  • What is the Browserbase MCP server and what can it do?

    It provides cloud browser automation for LLMs using Stagehand and Browserbase. You can navigate URLs, interact with page elements, observe actionable items, and extract data—all controlled by AI through six core tools: start, end, navigate, act, observe, and extract.

  • Do I need to self-host or can I use a hosted version?

    Browserbase recommends using their hosted MCP server at https://mcp.browserbase.com/mcp for easiest setup. You can also self-host via NPM (`npx @browserbasehq/mcp`), Docker, or by cloning the GitHub repo and running locally.

  • What authentication credentials do I need?

    You need a Browserbase API key and project ID. If using a custom model (not the default Gemini 2.5 Flash Lite), you must also provide that model's API key via the `--modelApiKey` flag.

  • Can I use models other than Gemini?

    Yes. The server defaults to Google Gemini 2.5 Flash Lite, but supports GPT-4o, Claude, and other providers via the `--modelName` flag. You must provide your own API key for any non-default model.

  • What are the main differences between hosted and self-hosted versions?

    The hosted version is easiest to set up and Browserbase covers LLM costs for Gemini. Self-hosted versions let you use custom models and have full control, but you manage your own infrastructure and API costs.

Run Smithery Browserbasehq MCP Browserbase across 60+ AI models, side-by-side

Connect Smithery Browserbasehq MCP Browserbase to Claude, GPT, Gemini, DeepSeek and 60+ AI models in MCP Agent Studio. Compare answers side-by-side, save reusable agent presets, share runs — all in your browser, no install required.

Open Agent Studio

Related servers

More on MCP Playground