Browserbase MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Browserbase MCP Server Navigate to example.com and extract the page title."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Browserbase MCP Server

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 |
| Create or reuse a Browserbase session | (none) |
| Close the current Browserbase session | (none) |
| Navigate to a URL |
|
| Perform an action on the page |
|
| Observe actionable elements on the page |
|
| Extract data from the page |
|
Related MCP server: Browserbase MCP Server
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 buildOption 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 |
| Enable Browserbase proxies for the session |
| Enable Browserbase Verified Identity (Only for Scale Plan Users) |
| Deprecated alias for |
| Enable Browserbase Keep Alive Session |
| Specify a Browserbase Context ID to use |
| Whether to persist the Browserbase context (default: true) |
| Port to listen on for HTTP/SHTTP transport |
| Host to bind server to (default: localhost, use 0.0.0.0 for all interfaces) |
| Browser viewport width (default: 1024) |
| Browser viewport height (default: 768) |
| The model to use for Stagehand (default: google/gemini-2.5-flash-lite) |
| API key for the custom model provider (required when using custom models) |
| 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.
Links
License
Licensed under the Apache 2.0 License.
Copyright 2025 Browserbase, Inc.
Available Tools
6 toolsactD
Perform an action on the page
Inputs: action (required).
endA
Close the current Browserbase session
Inputs: no named parameters.
extractC
Extract data from the page
Inputs: instruction.
observeC
Observe actionable elements on the page
Inputs: instruction (required).
startB
Create or reuse a Browserbase session
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct operation: session management (start, end), navigation (navigate), interaction (act), data extraction (extract), and element observation (observe). No overlap in purposes.
All tool names are single verbs in lowercase, following a consistent imperative style. No mixing of conventions or naming patterns.
6 tools is well-scoped for a browser automation session server, covering the full lifecycle from creation to teardown, with core actions and data extraction.
Covers the essential session lifecycle and common operations. Missing specific actions like click or type, but 'act' is generic enough. A screenshot tool would be a minor addition.
Related MCP Connectors
Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to i…
Hosted browser for agents: open pages, search the web, extract data, read PDFs and take screenshots.
Control a real browser from AI agents: navigate, click, type, screenshot, read the page.
Cloud browser, web extraction, screenshots, and remote CDP tools for AI agents.
Related MCP Servers
- AlicenseAqualityNot gradedmaintenanceEnables AI to control cloud browsers and automate web interactions through Browserbase and Stagehand. Supports web navigation, form filling, data extraction, screenshots, and automated actions with natural language commands.8714 npm-
- AlicenseAqualityDmaintenanceEnables cloud browser automation using Browserbase and Stagehand to interact with web pages, extract data, take screenshots, and perform automated actions with AI-powered natural language commands.17Apache 2.0
- AlicenseAqualityDmaintenanceEnables cloud browser automation through Browserbase and Stagehand, allowing LLMs to navigate web pages, extract data, take screenshots, fill forms, and perform automated web interactions with multi-session support.14Apache 2.0
- AlicenseAqualityDmaintenanceEnables cloud browser automation through Browserbase and Stagehand, allowing LLMs to interact with web pages, take screenshots, extract data, and perform automated actions with support for proxies, stealth mode, and parallel sessions.14Apache 2.0