chrome-devtools-mcp and firefox-devtools-mcp
These are complements that serve the same automation purpose across different browsers—developers would use them together to achieve cross-browser testing and control, with Chrome DevTools providing vastly more mature tooling through its established Remote Debugging Protocol implementation compared to Firefox's nascent MCP server.
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
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
Exposes WebDriver BiDi automation through 30+ tools covering page navigation, element interaction, network monitoring, console access, and JavaScript evaluation—all coordinated via a single snapshot/UID system for stable cross-navigation element references. Integrates with Claude Code, Cursor, Cline, and other MCP clients through stdio transport, supporting both headless and headed Firefox instances, connect-to-existing sessions, and optional privileged context access for browser preference management and extension installation.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work