chrome-local-mcp and chrome-devtools-mcp
These are complements: the Puppeteer-based tool provides high-level browser automation primitives, while the Chrome DevTools Protocol tool offers lower-level access to Chrome's internals, and they can be used together for comprehensive browser control—Puppeteer operations can be inspected/debugged via DevTools Protocol, or DevTools Protocol can handle advanced scenarios that Puppeteer doesn't directly expose.
About chrome-local-mcp
callmehuyv/chrome-local-mcp
A local Chrome browser automation MCP server for Claude Code, powered by Puppeteer
This tool helps you automate repetitive web tasks by giving Claude Code direct control over a real Chrome browser. You can instruct Claude Code in plain language to navigate websites, fill out forms, click buttons, extract text, and take screenshots. This is ideal for anyone who uses Claude Code and needs to interact with web pages to gather information or perform actions without manual intervention.
About chrome-devtools-mcp
benjaminr/chrome-devtools-mcp
An MCP Server for Chrome DevTools, following the Chrome DevTools Protocol. Integrates with Claude Desktop and Claude Code.
This tool helps web developers, QA engineers, and operations engineers debug web applications efficiently. It connects Claude (a conversational AI assistant) to Chrome's developer tools, allowing you to monitor web application behavior by asking natural language questions. You input a web application running in Chrome and receive insights into network traffic, console errors, performance metrics, and JavaScript objects, all through conversational prompts.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work