CookiesForAI

Browserbase MCP server

The Browserbase MCP server gives AI agents a browser that runs in Browserbase's cloud, controlled with plain-language commands through Stagehand: navigate, act on the page, observe elements and extract data.

By Browserbase Official · Updated

Connect Browserbase

Claude Code

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

Clients that support Streamable HTTP

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

The hosted endpoint needs your API key as the browserbaseApiKey query parameter for tool calls. Add modelName and modelApiKey to use a model other than the default google/gemini-2.5-flash-lite; Cursor has a one-click install on Browserbase's setup page.

What the Browserbase MCP server does

The Browserbase MCP server connects an AI agent to Browserbase, a service that runs headless browsers in the cloud. It is built on Stagehand, Browserbase's open-source automation framework, so the agent gives instructions in plain language, such as "click the login button" or "fill in the contact form", instead of writing selectors. A model reads the page and turns each instruction into actions.

Browserbase's server keeps its tool list short: start and end open and close a cloud browser session, navigate goes to a URL, act performs an action, observe finds the elements you can act on, and extract pulls data from the page, optionally guided by an instruction. Every tool takes a session ID, which lets clients such as ChatGPT that reconnect on each call keep working in the same browser. Options turn on proxies, Browserbase Verified for sites with bot checks, and keep-alive sessions.

Browserbase runs the server at mcp.browserbase.com, and its docs recommend that hosted endpoint over running it locally with npx. The open-source repo browserbase/mcp-server-browserbase was archived in 2026 and is kept only as a reference, so the hosted server is the maintained route.

Tools it gives your agent

  • start
  • end
  • navigate
  • act
  • observe
  • extract

When to use Browserbase

  • You want browser automation without running Chrome on your own machine.
  • Your agent needs many browsers at once, for example to check prices on dozens of sites.
  • You prefer to describe actions in words and let the server work out the clicks.
  • A site blocks ordinary headless browsers and you need proxies or verified browsing.

When to pick something else

  • Free heavy use: the Free plan includes only a little browser time, and every session runs on paid cloud time after that.
  • Precise, repeatable test steps; plain-language actions go through a model and can vary between runs, where Playwright MCP is deterministic.

What Browserbase needs

  • A Browserbase account and API key

What the Browserbase MCP server costs

Browser time is billed to your Browserbase account; the Free plan has a small monthly allowance, and paid plans add browser hours and concurrency.

Current prices: www.browserbase.com . We do not list prices: vendors change them often, so check the publisher's own page.

  • Browser Use: The Browser Use MCP server gives AI agents the Browser Use browsing agent, either as a local open-source server with direct browser tools or as a cloud server that runs whole web tasks.
  • Chrome DevTools: The Chrome DevTools MCP server gives AI agents control of a live Chrome browser with DevTools access: performance traces, network requests, console errors, Lighthouse audits, memory snapshots and page automation.
  • Playwright: The Playwright MCP server gives AI agents a real browser driven by Microsoft's Playwright: navigate, click, type and fill forms using the page's accessibility tree instead of screenshots.