Browserbase
Spin up remote browser sessions from your agent to exercise flows, scrape pages, or validate UI without maintaining local Chrome drivers.
Overview
com.mcparmory/browserbase is a MCP server for the Ship phase that creates and controls Browserbase sessions for web automation, testing, and agent-driven browsing.
What is this MCP server?
- Creates and controls cloud browser sessions for automation and AI agent tasks
- stdio MCP v1.0.4 with PyPI (mcparmory-browserbase) and Docker OCI install options
- Fits web automation and testing pipelines without local Selenium grid setup
- Registry-hosted package from mcparmory for consistent agent wiring
- Useful for reproducing user journeys agents cannot see from static code alone
- Version 1.0.4 with 2 packages (PyPI + Docker OCI)
- stdio MCP transport
- Repository: github.com/mcparmory/registry
Community signal: 25 GitHub stars.
What problem does it solve?
Local browsers and drivers break often, and agents cannot reliably click through your app without a managed session API.
Who is it for?
Solo builders who ship web apps and want agent-led smoke tests or scripted flows on staging without hosting browsers yourself.
Skip if: Pure API backends with no UI, or teams forbidden from cloud browser vendors.
What do I get? / Deliverables
Your agent can open Browserbase sessions, navigate sites, and run automation steps while you stay in the IDE.
- Agent-controlled browser sessions for navigation and automation
- Repeatable MCP server entry for Ship-phase UI checks
- Documented v1.0.4 dual-package deployment (PyPI + OCI)
Recommended MCP Servers
Journey fit
Ship is the canonical home for pre-release verification; browser sessions are how you prove flows work before users hit production. Testing subphase covers automated navigation, smoke checks, and agent-driven QA that Browserbase sessions are built to support.
How it compares
Remote browser MCP connector, not a Playwright skill that teaches test design patterns.
Common Questions / FAQ
Who is com.mcparmory/browserbase for?
Developers using AI agents who need real browser sessions for QA, scraping, or workflow automation via Browserbase.
When should I use com.mcparmory/browserbase?
During Ship testing (and selective Build integrations) when you must validate UI flows, OAuth redirects, or dynamic pages before release.
How do I add com.mcparmory/browserbase to my agent?
Configure stdio MCP with `uvx mcparmory-browserbase` or `ghcr.io/mcparmory/browserbase:1.0.4`, and set Browserbase API keys in your environment or MCP config.