Browserbasehq Mcp Browserbase

ai.smitheryPublished by smithery.aiOfficial publisherv2.2.0Updated Oct 24, 2026

Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to i…

The publisher's own server: 222wcnm Bilistalkermcp

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBrowser Automation

Overview

AI-generated overview

Cloud browser automation server using Browserbase and Stagehand, letting an assistant open sessions, navigate pages, act, observe and extract data.

What you can do
  • Start or reuse a Browserbase cloud browser session and close it when done
  • Navigate the browser to a URL
  • Perform actions on the page and observe actionable elements
  • Extract data from the current page on instruction
When to use it
Useful when an assistant needs to drive a real cloud browser: filling in forms, clicking through a site, or pulling structured information off pages that plain HTTP fetching cannot handle. The README notes the repository is archived and recommends the hosted Browserbase server instead.
Requirements
Remote endpoint at server.smithery.ai with a bearer token in the Authorization header. The self-hosted variant needs Node.js (npx @browserbasehq/mcp) or Docker, plus BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID and, for the default Stagehand model, GEMINI_API_KEY; custom models need --modelApiKey.
Before you install
The README states the repository is archived and no longer maintained, so prefer the hosted version. Self-hosting requires a Browserbase API key and project ID, and a model provider key for non-default models. The assistant can act on live web pages, which may submit forms or change remote state, and page content is processed by Browserbase and the chosen model provider.

Installation

In SourceWeft

  1. Open Browserbasehq Mcp Browserbase in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.smithery%2Fbrowserbasehq-mcp-browserbase/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "browserbasehq-browserbase": {
      "type": "http",
      "url": "https://server.smithery.ai/@browserbasehq/mcp-browserbase/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Browserbase MCP Server

Archived

This repository is archived and no longer maintained.

It was originally published as a reference implementation and is retained for historical purposes. It should not be interpreted as representative of Browserbase's current production services or implementation.

[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:

ToolDescriptionInput
startCreate or reuse a Browserbase session(none)
endClose the current Browserbase session(none)
navigateNavigate to a URL{ url: string }
actPerform an action on the page{ action: string }
observeObserve actionable elements on the page{ instruction: string }
extractExtract 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:

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

If your client doesn't support SHTTP:

json
{  "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:

json
{  "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
bash
git clone https://github.com/browserbase/mcp-server-browserbase.gitcd mcp-server-browserbasenpm install && npm run build
Option 2: Docker
bash
git clone https://github.com/browserbase/mcp-server-browserbase.gitcd mcp-server-browserbasedocker build -t mcp-browserbase .

Then in your MCP Config JSON run the server:

Using Direct Installation
json
{  "mcpServers": {    "browserbase": {      "command": "node",      "args": ["/path/to/mcp-server-browserbase/cli.js"],      "env": {        "BROWSERBASE_API_KEY": "",        "BROWSERBASE_PROJECT_ID": "",        "GEMINI_API_KEY": ""      }    }  }}
Using Docker
json
{  "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:

FlagDescription
--proxiesEnable Browserbase proxies for the session
--verifiedEnable Browserbase Verified Identity (Only for Scale Plan Users)
--advancedStealthDeprecated alias for --verified
--keepAliveEnable Browserbase Keep Alive Session
--contextId <contextId>Specify a Browserbase Context ID to use
--persistWhether 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)
--experimentalEnable 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.

json
{  "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.

Links

License

Licensed under the Apache 2.0 License.

Copyright 2025 Browserbase, Inc.

Source: README.md at commit 3e6f534

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.2.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Smithery integrations