by browserbase
Provides cloud browser automation capabilities for LLMs, enabling navigation, data extraction, screenshots, and session management via Browserbase and Stagehand.
Enables large language models to control cloud browsers through Browserbase and Stagehand, offering precise web interaction, structured data extraction, and visual capture without writing low‑level automation code.
browserbase
server in the client’s JSON config.npx @browserbasehq/mcp-server-browserbase
.BROWSERBASE_API_KEY
, BROWSERBASE_PROJECT_ID
, and optionally GEMINI_API_KEY
for the default model.Q: Do I need to host the server myself?
A: No. You can use the remote hosted SHTTP endpoint from Smithery, or run it locally with npx
.
Q: Which models are supported?
A: By default Gemini 2.0 Flash; you can switch to any model supported by Stagehand (e.g., GPT‑4o, Claude) using --modelName
and provide the corresponding API key via --modelApiKey
.
Q: How do I enable proxies or stealth mode?
A: Add the flags --proxies
or --advancedStealth
to the CLI arguments in your MCP config.
Q: Can I run multiple browsers at once? A: Yes. The server supports parallel sessions, each isolated with its own context ID.
Q: What environment variables are required?
A: BROWSERBASE_API_KEY
and BROWSERBASE_PROJECT_ID
are mandatory; GEMINI_API_KEY
is needed for the default model, and other model keys are required when using custom providers.
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, take screenshots, extract information, and perform automated actions with atomic precision.
Feature | Description |
---|---|
Browser Automation | Control and orchestrate cloud browsers via Browserbase |
Data Extraction | Extract structured data from any webpage |
Web Interaction | Navigate, click, and fill forms with ease |
Screenshots | Capture full-page and element screenshots |
Model Flexibility | Supports multiple models (OpenAI, Claude, Gemini, and more) |
Vision Support | Use annotated screenshots for complex DOMs |
Session Management | Create, manage, and close browser sessions |
Multi-Session | Run multiple browser sessions in parallel |
Copy and Paste this link in your Browser:
cursor://anysphere.cursor-deeplink/mcp/install?name=browserbase&config=eyJjb21tYW5kIjoibnB4IEBicm93c2VyYmFzZWhxL21jcCIsImVudiI6eyJCUk9XU0VSQkFTRV9BUElfS0VZIjoiIiwiQlJPV1NFUkJBU0VfUFJPSkVDVF9JRCI6IiIsIkdFTUlOSV9BUElfS0VZIjoiIn19
We currently support 2 transports for our MCP server, STDIO and SHTTP. We recommend you use SHTTP with our remote hosted url to take advantage of the server at full capacity.
To use the Browserbase MCP Server through our remote hosted URL, add the following to your configuration.
Go to smithery.ai and enter your API keys and configuration to get a remote hosted URL. When using our remote hosted server, we provide the LLM costs for Gemini, the best performing model in Stagehand.
If your client supports SHTTP:
{
"mcpServers": {
"browserbase": {
"url": "your-smithery-url.com"
}
}
}
If your client doesn't support SHTTP:
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": ["mcp-remote", "your-smithery-url.com"]
}
}
}
You can either use our Server hosted on NPM or run it completely locally by cloning this repo.
❗️ Important: 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.
Go into your MCP Config JSON and add the Browserbase Server:
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": ["@browserbasehq/mcp-server-browserbase"],
"env": {
"BROWSERBASE_API_KEY": "",
"BROWSERBASE_PROJECT_ID": "",
"GEMINI_API_KEY": ""
}
}
}
}
That's it! Reload your MCP client and Claude will be able to use Browserbase.
# Clone the Repo
git clone https://github.com/browserbase/mcp-server-browserbase.git
cd mcp-server-browserbase
# Install the dependencies and build the project
pnpm install && pnpm build
Then in your MCP Config JSON run the server. To run locally we can use STDIO or self-host SHTTP.
To your MCP Config JSON file add the following:
{
"mcpServers": {
"browserbase": {
"command": "node",
"args": ["/path/to/mcp-server-browserbase/cli.js"],
"env": {
"BROWSERBASE_API_KEY": "",
"BROWSERBASE_PROJECT_ID": "",
"GEMINI_API_KEY": ""
}
}
}
}
Then reload your MCP client and you should be good to go!
The Browserbase MCP server accepts the following command-line flags:
Flag | Description |
---|---|
--proxies |
Enable Browserbase proxies for the session |
--advancedStealth |
Enable Browserbase Advanced Stealth (Only for Scale Plan Users) |
--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) |
--cookies [json] |
JSON array of cookies to inject into the browser |
--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.0-flash) |
--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.
Currently, these flags can only be used with the local server (npx @browserbasehq/mcp-server-browserbase).
Here are our docs on Proxies.
To use proxies, set the --proxies flag in your MCP Config:
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": ["@browserbasehq/mcp-server-browserbase", "--proxies"],
"env": {
"BROWSERBASE_API_KEY": "",
"BROWSERBASE_PROJECT_ID": "",
"GEMINI_API_KEY": ""
}
}
}
}
Here are our docs on Advanced Stealth.
To use advanced stealth, set the --advancedStealth flag in your MCP Config:
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": ["@browserbasehq/mcp-server-browserbase", "--advancedStealth"],
"env": {
"BROWSERBASE_API_KEY": "",
"BROWSERBASE_PROJECT_ID": "",
"GEMINI_API_KEY": ""
}
}
}
}
Here are our docs on Contexts
To use contexts, set the --contextId flag in your MCP Config:
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": [
"@browserbasehq/mcp-server-browserbase",
"--contextId",
"<YOUR_CONTEXT_ID>"
],
"env": {
"BROWSERBASE_API_KEY": "",
"BROWSERBASE_PROJECT_ID": "",
"GEMINI_API_KEY": ""
}
}
}
}
The default viewport sizing for a browser session is 1024 x 768. You can adjust the Browser viewport sizing with browserWidth and browserHeight flags.
Here's how to use it for custom browser sizing. We recommend to stick with 16:9 aspect ratios (ie: 1920 x 1080, 1280 x 720, 1024 x 768)
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": [
"@browserbasehq/mcp-server-browserbase",
"--browserHeight 1080",
"--browserWidth 1920"
],
"env": {
"BROWSERBASE_API_KEY": "",
"BROWSERBASE_PROJECT_ID": "",
"GEMINI_API_KEY": ""
}
}
}
}
Stagehand defaults to using Google's Gemini 2.0 Flash 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.
Here's how to configure different models:
{
"mcpServers": {
"browserbase": {
"command": "npx",
"args": [
"@browserbasehq/mcp-server-browserbase",
"--modelName",
"anthropic/claude-3-5-sonnet-latest",
"--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. When using any custom model, you must provide your own API key for that provider.
The server provides access to screenshot resources:
screenshot://<screenshot-name>
)
For more information about the Model Context Protocol, visit:
For the official MCP Docs:
Licensed under the Apache 2.0 License.
Copyright 2025 Browserbase, Inc.
Please log in to share your review and rating for this MCP.
{ "mcpServers": { "browserbase": { "command": "npx", "args": [ "@browserbasehq/mcp-server-browserbase" ], "env": { "BROWSERBASE_API_KEY": "<YOUR_BROWSERBASE_API_KEY>", "BROWSERBASE_PROJECT_ID": "<YOUR_PROJECT_ID>", "GEMINI_API_KEY": "<YOUR_GEMINI_API_KEY>" } } } }
Explore related MCPs that share similar capabilities and solve comparable challenges
by zed-industries
A high‑performance, multiplayer code editor designed for speed and collaboration.
by modelcontextprotocol
Model Context Protocol Servers
by modelcontextprotocol
A Model Context Protocol server for Git repository interaction and automation.
by modelcontextprotocol
A Model Context Protocol server that provides time and timezone conversion capabilities.
by cline
An autonomous coding assistant that can create and edit files, execute terminal commands, and interact with a browser directly from your IDE, operating step‑by‑step with explicit user permission.
by continuedev
Enables faster shipping of code by integrating continuous AI agents across IDEs, terminals, and CI pipelines, offering chat, edit, autocomplete, and customizable agent workflows.
by upstash
Provides up-to-date, version‑specific library documentation and code examples directly inside LLM prompts, eliminating outdated information and hallucinated APIs.
by github
Connects AI tools directly to GitHub, enabling natural‑language interactions for repository browsing, issue and pull‑request management, CI/CD monitoring, code‑security analysis, and team collaboration.
by daytonaio
Provides a secure, elastic infrastructure that creates isolated sandboxes for running AI‑generated code with sub‑90 ms startup, unlimited persistence, and OCI/Docker compatibility.