Browserbase MCP 🔌 MCP server Freemium

What it does

Browserbase MCP gives an agent a browser that runs in Browserbase's cloud, so nothing needs to be installed or opened on your machine. The browser is driven by Stagehand, Browserbase's open-source automation framework. The agent gives plain-language instructions like "click the login button", and Stagehand's model turns them into browser actions. This suits scraping, filling in forms, or checking a deployed site from an agent that has no local browser, such as one running in CI or a remote sandbox. Note that the browserbase/mcp-server-browserbase GitHub repository is now archived and marked as no longer maintained. Browserbase recommends its hosted server instead.

Tools it gives your agent

• start and end: create, reuse or close a cloud browser session
• navigate: open a URL
• act: perform an action described in natural language
• observe: find the actionable elements that match an instruction
• extract: pull data from the current page

Every tool takes an optional sessionId, so clients that open a new connection for each call can reconnect to the same browser.

Works with

The hosted server uses Streamable HTTP at https://mcp.browserbase.com/mcp and works with any MCP client that supports remote servers, including Claude Code, Cursor, Codex and Gemini CLI. The archived npm package @browserbasehq/mcp still runs locally over stdio, but it no longer gets updates.

How to connect

claude mcp add --transport http browserbase "https://mcp.browserbase.com/mcp?browserbaseApiKey=YOUR_BROWSERBASE_API_KEY"

Cost and limits

At the time of writing (September 2026), Browserbase's Free plan costs $0 with no card needed. It includes 1 browser hour, 3 concurrent sessions and 15-minute sessions. Developer costs $20 a month for 100 browser hours, and Startup costs $99 for 500 hours, both with pay-as-you-go overage. On the hosted server, Browserbase covers the cost of the default Gemini model. If you pick a different model with modelName, you have to supply that provider's API key.

Safety notes

The documented setup puts your API key in the URL query string. Keep that config out of shared repos and treat it like a password. Avoid logging the agent into sensitive accounts. Remember that act makes a model guess which element to click, so check results on important flows.