Browserbase MCP — Cloud Browser Automation Tools

Practical Notes

• Exposes 6 tools: start/end/navigate/act/observe/extract (README tool table)
• Supports both hosted SHTTP and self-hosted STDIO; flags like viewport and port are configurable (README config section)

Make Browser Automation Predictable

Browser tools become flaky when prompts are vague. A few tactics help:

• Always observe before you act so the agent uses stable element affordances.
• Keep your extraction requests structured (“extract a table with columns X/Y/Z”) instead of “summarize”.
• For CI-style runs, pin viewport size and avoid infinite-scroll pages.

If you need a 100% local deployment, the README documents two options:

git clone https://github.com/browserbase/mcp-server-browserbase.git
cd mcp-server-browserbase
npm install && npm run build

Then run the server via node (or Docker) and point your MCP client at it.

FAQ

Q: What credentials do I need? A: At minimum: BROWSERBASE_API_KEY + BROWSERBASE_PROJECT_ID; a model API key may be required depending on your setup.

Q: Hosted vs self-hosted? A: Hosted SHTTP is the easiest; self-hosted STDIO is available via npx @browserbasehq/mcp or Docker.

Q: How do I reduce flakiness? A: Use observe→act, keep instructions structured, and pin viewport/inputs.