firefox-devtools-mcp and chrome-devtools-mcp
These two tools are competitors, as they both aim to provide a Model Context Protocol server for their respective browser's DevTools, enabling AI assistants to inspect and control either Firefox or Chrome through their remote debugging protocols.
About firefox-devtools-mcp
padenot/firefox-devtools-mcp
Model Context Protocol server for Firefox DevTools - enables AI assistants to inspect and control Firefox browser through the Remote Debugging Protocol
This tool enables AI assistants like Claude Code to automate tasks within the Firefox browser. It takes instructions from an AI and translates them into actions like navigating pages, clicking buttons, filling forms, and capturing screenshots. Web developers, quality assurance engineers, and AI developers can use this to automate browser testing, build AI-powered agents, or interact with web content through an AI.
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