firefox-devtools-mcp and chrome-devtools-mcp
These two tools are **competitors**, as they both provide a Model Context Protocol server for their respective browser's DevTools, enabling AI assistants to inspect and control either Firefox or Chrome, but not both simultaneously with a single tool.
About firefox-devtools-mcp
freema/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 project lets AI assistants like Claude Code inspect and control Firefox browser sessions through the Remote Debugging Protocol. It takes commands from an AI assistant, automates browser actions (like navigating pages, clicking elements, or filling forms), and outputs browser state information, screenshots, and network activity. It's designed for developers building or using AI agents that need to interact with web applications.
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