browser-mcp vs chrome-devtools-mcp
browser-mcp: Browser MCP enables AI agents like Claude Code to control a user's real Chrome browser, leveraging existing logins, cookies, and 2FA to operate on sites where traditional headless browsers fail. It offers advanced capabilities like multi-session management, human-in-the-loop interaction for sensitive steps, and built-in tools for complex web interactions and CAPTCHA solving.; chrome-devtools-mcp: chrome-devtools-mcp enables AI coding assistants like Gemini, Claude, and Copilot to interact with a live Chrome browser via the Model-Context-Protocol (MCP). It grants AI full access to Chrome DevTools for reliable automation, deep debugging, and detailed performance insights.
TL;DR
Automate operations on platforms with no public API (e.g., legacy systems, social media).
- You want an agent to record a Chrome performance trace and get insights from it; the README lists performance_start_trace, performance_stop_trace and performance_analyze_insight.
- You need to inspect network requests, console messages and screenshots of a page while debugging it.
- You want the agent to attach to a Chrome you already have running, using --browser-url, --ws-endpoint or --autoConnect (Chrome 144+).
- You need Firefox or Safari: the project is built on Chrome DevTools and targets Chrome.
- You want a general-purpose automation or test runner across browsers; Playwright MCP is the closer fit.
- You cannot run Node.js 20.19 or newer, which the README lists as a requirement.
Side-by-Side Comparison
Features
Use Cases
Best For
FAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.