firefox-devtools-mcp and chrome-devtools-mcp
These are ecosystem siblings that implement the same Model Context Protocol standard for different browser engines, allowing AI assistants to choose between Firefox or Chrome browser automation depending on their deployment environment.
About firefox-devtools-mcp
mozilla/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 helps AI assistants like Claude automate tasks in Firefox. It allows an AI to control a Firefox browser to perform actions like navigating pages, clicking elements, filling forms, taking screenshots, and inspecting network requests and console messages. This is useful for AI developers creating agents that need to interact with websites through a real browser.
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