MCP Browser
Drive the user’s own Chromium session from your agent—run JS, reuse auth cookies, and work around basic bot friction while building web-dependent features.
Overview
MCP Browser is a Build-phase MCP server that automates the user’s Chromium session with JS execution, authentication reuse, and anti-bot support over stdio MCP.
What is this MCP server?
- Automates via the user’s Chromium session—not a disposable anonymous profile only
- JavaScript execution, authenticated navigation, and anti-bot oriented support
- Ships as npm mcpbrowser 0.3.58 stdio and optional mcpb bundle with published SHA256
- VS Code extension icon assets—ecosystem ties to MCPBrowser tooling
- Monorepo subfolder MCPBrowser on GitHub with documented readme
- Version 0.3.58
- npm identifier mcpbrowser with stdio transport
- Optional mcpb bundle with fileSha256 ce489d65456d0c68141282014c25211883fa55fca819017e60278612d9bfde1e
Community signal: 7 GitHub stars.
What problem does it solve?
Agents stall on modern web apps that need real cookies, client-side JS, and human-like browsers—not bare HTTP calls.
Who is it for?
Solo builders automating login-gated workflows, in-browser QA, and integration probes against production-like sessions.
Skip if: Server-only backends with no browser surface, or catalog research where a remote SaaS directory MCP is enough.
What do I get? / Deliverables
Your agent can navigate, execute script, and read authenticated pages through MCP tools grounded in your Chromium profile.
- Agent-driven navigation and script execution in a real browser session
- Authenticated access paths for integration and regression checks
- Reusable MCP tooling for web-dependent agent workflows
Recommended MCP Servers
Journey fit
Full browser automation lands in build when you integrate agents with real product UIs, third-party portals, and flows that APIs do not expose. Reusing the user’s Chromium profile is an integration pattern for solo builders who test and script against live sites daily.
How it compares
Full Chromium-session automation MCP—not the slimmer CDP page-load variant or team-wide orchestration DSLs.
Common Questions / FAQ
Who is MCP Browser for?
It is for developers who want coding agents to control their own Chromium browser for auth-heavy sites, JS-rendered UIs, and practical integration testing.
When should I use MCP Browser?
Use it during build and ship prep when you need repeatable agent actions in a logged-in browser, including pages that resist simple scrapers.
How do I add MCP Browser to my agent?
Install npm package mcpbrowser at 0.3.58 for stdio MCP, or use the published mcpb bundle if your client supports it, following github.com/cherchyk/MCPBrowser setup steps.