Mcp Server Browserbase

io.github.browserbasePublished by GitHub account browserbasev2.1.1Updated Oct 24, 2026

MCP server for AI web browser automation using Browserbase and Stagehand

VerifiedSTDIODesktop onlyWeb Search & Scraping Browser Automation

Server details

Identifier: io.github.browserbase/mcp-server-browserbase
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account browserbase for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.browserbase%2Fmcp-server-browserbase.svg)](https://sourceweft.com/mcp/io.github.browserbase%2Fmcp-server-browserbase?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A self-hostable MCP server that lets an assistant drive cloud browsers through Browserbase and Stagehand to navigate pages, act, observe and extract data.

What you can do: Start or end a Browserbase browser session, reusing an existing one when available. Navigate the session to a URL. Perform an action on the page from a natural-language instruction. Observe actionable elements on the page to plan next steps. Extract data from the page, optionally guided by an instruction.
When to use it: Useful when you want an assistant to browse and interact with live web pages in a managed cloud browser, for example to gather information or run repeatable web actions. The repository is archived, so consider the vendor's hosted server instead for new setups.
Requirements: Runs locally over stdio, typically via npx with the npm package or from a cloned repository, or in Docker; Node.js is needed for the npm route. Requires a Browserbase API key and project ID, plus a Gemini API key for the default Stagehand model; a custom model needs its own provider key. Network access to Browserbase and the model provider is required.

Before you install

Needs the secrets BROWSERBASE_API_KEY and GEMINI_API_KEY, and a custom model key if one is configured; keep them out of shared configuration. The assistant can act on live web pages, which may submit forms, click buttons or change remote state. Page content and instructions are sent to Browserbase and the model provider. The project is archived and unmaintained.

Installation

In SourceWeft

Open Mcp Server Browserbase in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

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:

json

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

{  "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"]    }  }}

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

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

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 .

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": ""      }    }  }}

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

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

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": ""      }    }  }}

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

License

Licensed under the Apache 2.0 License.

Source: README.md at commit 3e6f534

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v2.1.1LatestSep 16, 2026

Score

50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 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

Mcp Server Browserbase

Overview

Installation

In SourceWeft

Other MCP clients

README

Browserbase MCP Server

Archived

Tools

How to Setup

SHTTP (Hosted MCP):

STDIO (Self-Hosted):

To run via NPM (Recommended)

To run 100% local:

Option 1: Direct installation

Option 2: Docker

Using Direct Installation

Using Docker

Configuration

Model Configuration

Links

License

Tools

Version history

Score