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.
Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to i…
2026-11-07
Sterne
—
Tools
—
Uptime
—
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.
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.
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.
Noch keine Tool-Liste. Remote-Server erhalten eine nach dem ersten Health-Check.
FAQ
Fragen
Wie installiere ich Browserbasehq MCP Browserbase?
Kopieren Sie auf dieser Seite die http-Konfiguration für Cursor, Claude Desktop, Claude Code oder VS Code. Sie nutzt die Installation des Herausgebers, keinen PlugMCP-Proxy.
Benötigt Browserbasehq MCP Browserbase einen API-Schlüssel?
In diesem Eintrag ist keine erforderliche Umgebungsvariable aufgeführt.
Welchen Transport verwendet Browserbasehq MCP Browserbase?
Browserbasehq MCP Browserbase wird über HTTP erreicht.
Wann wurde Browserbasehq MCP Browserbase zuletzt geprüft?
Zuletzt geprüft: 2026-11-07. Provides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to i…