chrome-devtools-mcp and firefox-devtools-mcp
These are complementary tools that enable browser automation across different engines—Chrome DevTools MCP controls Chromium-based browsers while Firefox DevTools MCP controls Firefox through their respective debugging protocols, allowing users to choose or combine based on their target browser environment.
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 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
Leverages WebDriver BiDi protocol through Selenium WebDriver for browser automation, exposing tools for DOM inspection (snapshots with UIDs), network monitoring, console access, and script evaluation. Integrates with Claude Code, Claude Desktop, Cursor, and Cline via stdio transport, with support for headless operation, custom Firefox profiles, and privileged chrome context access for Firefox development workflows.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work