Open Source · MIT License · Free
Browser MCP drives your real Chrome.
Works where headless dies.
Browser MCP is a free, open-source MCP server and Chrome extension that gives your AI agent your real, already-logged-in Chrome — cookies, sessions, 2FA — and works on login-gated sites where headless tools get blocked. It can even read an emailed login code from your Gmail tab and finish the sign-in. Works with Claude Code, Cursor, and VS Code agent mode. MIT, free, local-only.
🧩
CAPTCHA Assistance
On sites you're authorised to use: detects reCAPTCHA, hCaptcha and Turnstile, attempts the checkbox, then hands the challenge to you. No third-party solving service.
🔀
10 Concurrent Sessions
Each Claude Code conversation gets its own color-coded Chrome Tab Group. No conflicts.
🔐
Human-in-the-Loop
browser_ask_user shows an overlay for 2FA codes, CAPTCHA, credentials. Your AI asks, you answer.
🔗
9 Provider Integrations
Built-in token extraction for Stripe, HubSpot, Slack, Shopify, Pipedrive, Calendly, Mailchimp, Google, LinkedIn.
🛡️
Works on CSP-Strict Sites
Chrome Debugger API for real mouse/keyboard events. Works on Google Cloud, Stripe, Angular Material.
📡
34 Tools
Navigate, click, fill, screenshot, scroll, hover, fetch, wait for network, solve CAPTCHA, and more.
Frequently asked
What is Browser MCP?
Browser MCP is a free, open-source MCP server and Chrome extension that lets an AI agent (Claude Code, Cursor, VS Code) control your real, already-logged-in Chrome instead of a fresh headless browser. It works on 2FA-, CAPTCHA- and login-gated sites where headless tools get blocked, and runs 100% locally — nothing leaves your machine.
How is this different from Playwright MCP?
Playwright MCP launches a fresh headless browser with no logins, cookies, or extensions. Browser MCP controls your actual Chrome — same profile, same logins, same 2FA. That means your AI can use Stripe, HubSpot, Slack, or anything you're already signed into without re-auth.
Is my data safe? What does the extension see?
Everything stays local. The extension talks to an MCP server running on
127.0.0.1 on your machine — nothing is transmitted to external servers, there's no telemetry, no analytics. Cookies and tokens are extracted only when Claude Code explicitly asks. Source is
open and auditable on GitHub.
Why does it need so many permissions?
Browser MCP is a developer tool that controls Chrome on your behalf. Each permission has a specific reason:
tabs/
scripting for navigation and clicking,
cookies for token extraction (Stripe/HubSpot/etc.),
debugger for real input events on CSP-protected sites like Google Cloud,
<all_urls> because the AI must navigate to whatever URL you ask it to. A full per-permission breakdown is on the
permissions & data page.
Does it work with anything other than Claude Code?
Yes — it speaks the standard MCP (Model Context Protocol) wire format, so any MCP-compatible client works: Claude Desktop, Cline, Continue, Cursor, etc. Setup is the same: run the local MCP server, point your client at it.
How does CAPTCHA assistance actually work?
Three layers. (1) Auto-detect reCAPTCHA, hCaptcha, Turnstile checkboxes and click them automatically. (2) For image-grid challenges, AI vision identifies cells. (3) If automated assistance fails, browser_ask_user shows an overlay so you can solve the challenge once and the AI continues. Nothing is sent to third-party CAPTCHA services.
Is it really free? What's the catch?
It's MIT-licensed, open source, no paywall. Built and maintained by
Agent360 as part of our developer-tools ecosystem. No catch — the catch (if there is one) is that bug reports and PRs are welcome.
How do I uninstall it?
Two parts: remove the Chrome extension from chrome://extensions, and uninstall the MCP server with npm uninstall -g @agent360/browser-mcp. That's it — no leftover state.
