
Browser Mcp
Drive your logged-in Chrome from Claude Code for realistic E2E checks, form flows, and sites that block headless automation.
Overview
io.github.Agent360dk/browser-mcp is a MCP server for the Ship phase that controls your real Chrome from Claude Code with 29 tools, CAPTCHA solving, and multi-session support.
What is this MCP server?
- 29 MCP tools to control your real Chrome instance
- CAPTCHA solving support for blocked automation flows
- Multi-session handling for parallel or role-based testing
- Optimized for Claude Code via @agent360/browser-mcp (v1.16.1)
- stdio npm package for standard MCP hosts
- 29 browser control tools
- Package version 1.16.1
- npm identifier @agent360/browser-mcp
Community signal: 13 GitHub stars.
What problem does it solve?
Headless automation cannot reproduce logged-in Chrome behavior, CAPTCHAs, or extension-dependent flows you need before you ship.
Who is it for?
Indie web builders who live in Claude Code and need trustworthy browser control on their own machine.
Skip if: Teams that require cloud browser grids only, or workflows forbidden from solving CAPTCHAs or automating third-party ToS-sensitive sites.
What do I get? / Deliverables
Your agent can drive authenticated, multi-session Chrome sessions so E2E validation matches what real users see.
- Agent-controlled Chrome sessions via 29 tools
- CAPTCHA-aware automation paths
- Parallel multi-session browser workflows
Recommended MCP Servers
Journey fit
How it compares
Real Chrome MCP automation, not a static accessibility linter or API-only test runner.
Common Questions / FAQ
Who is io.github.Agent360dk/browser-mcp for?
Solo developers using Claude Code who need agent-driven control of their local Chrome for QA and integrations.
When should I use io.github.Agent360dk/browser-mcp?
Use it in Ship testing (and adjacent Build UI work) when headless tools fail on auth, CAPTCHA, or real-profile behavior.
How do I add io.github.Agent360dk/browser-mcp to my agent?
Install @agent360/browser-mcp from npm, enable stdio MCP in Claude Code, and connect it to your local Chrome per the Agent360dk repository docs.