chrome-devtools-mcp and chrome-local-mcp
These are competitors offering different approaches to Chrome automation—DevTools provides a protocol-level interface for agent coding with mature production adoption, while Puppeteer-based local automation offers a simpler, self-contained alternative for Claude-specific workflows.
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 chrome-local-mcp
callmehuyv/chrome-local-mcp
A local Chrome browser automation MCP server for Claude Code, powered by Puppeteer
Implements persistent browser sessions with real Chrome profiles, accessibility snapshots (reducing vision token costs), and batch actions—all via a single stdio-based MCP server that requires zero configuration. Includes 22 specialized tools optimized for Claude Code workflows, plus optional local OCR via Apple Vision and a REST API for external integrations.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work