chrome-devtools-mcp and openchrome
These are complements: Chrome DevTools provides low-level debugging and inspection capabilities via the Chrome DevTools Protocol, while OpenChrome wraps that protocol in an MCP server interface to enable AI agents to control Chrome browsers at a higher abstraction level.
About chrome-devtools-mcp
ChromeDevTools/chrome-devtools-mcp
Chrome DevTools for coding agents
Implements a Model-Context-Protocol (MCP) server that bridges AI coding agents with Chrome's DevTools Protocol, enabling performance tracing, network inspection, and automated browser actions through Puppeteer. Supports both full-featured and lightweight ("slim") modes, integrating with agents like Claude, Gemini, and Cursor for debugging, screenshot capture, and source-mapped stack trace analysis.
About openchrome
shaun0927/openchrome
Open-source browser automation MCP server. Control your real Chrome from any AI agent.
Implements MCP server that connects directly to Chrome via Chrome DevTools Protocol (CDP), eliminating middleware overhead while maintaining real browser sessions and login state across parallel tabs. Includes 27 harness subsystems—hint engine with 30+ rules, outcome classification, pattern learning, and DOM compression achieving 15x token efficiency—that guide AI agents and prevent costly error cascades. Achieves ~300MB memory for 20 parallel sessions versus 5GB+ for traditional approaches, while remaining invisible to bot detection and enabling authenticated cross-site operations.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work