browser-mcp vs browser-tools-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.; browser-tools-mcp: BrowserTools MCP empowers AI applications to monitor and interact with browsers through a Chrome extension and Anthropic's Model Context Protocol. It offers a suite of tools for web development audits, including accessibility, performance, and SEO analysis, enhancing AI's capability to understand and improve web pages.
TL;DR
Automate operations on platforms with no public API (e.g., legacy systems, social media).
- You use Cursor or a similar IDE agent and want it to read console logs, network activity, screenshots and the currently selected DOM element from your own Chrome.
- You want Lighthouse-based audits for accessibility, performance, SEO and best practices from within the agent.
- You want browser logs kept local: the README says logs are stored on your machine and never sent to a third-party service.
- You want the agent to click through and drive pages; this tool is aimed at monitoring and auditing, not full automation.
- You do not want to install a Chrome extension and run a separate local Node server alongside the MCP server.
- You want the most actively developed option: the latest release in the data we checked was v2.0.2 on 2026-08-12.
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.