chrome-devtools-mcp
★ 54.0k
vs
firefox-devtools-mcp
★ 516
chrome-devtools-mcp vs firefox-devtools-mcp
chrome-devtools-mcp: chrome-devtools-mcp enables AI coding assistants like Gemini, Claude, and Copilot to interact with a live Chrome browser via the Model-Context-Protocol (MCP). It grants AI full access to Chrome DevTools for reliable automation, deep debugging, and detailed performance insights.; firefox-devtools-mcp: Firefox DevTools MCP is a Model Context Protocol server that automates Firefox using WebDriver BiDi through Selenium. It enables AI assistants like Claude to control browser actions such as navigation, screenshots, and network monitoring. It integrates with various MCP clients including Claude Code, Cursor, and Cline.
01
TL;DR
chrome-devtools-mcpBrowser Automation · ★ 54.0k
When to choose:
- You want an agent to record a Chrome performance trace and get insights from it; the README lists performance_start_trace, performance_stop_trace and performance_analyze_insight.
- You need to inspect network requests, console messages and screenshots of a page while debugging it.
- You want the agent to attach to a Chrome you already have running, using --browser-url, --ws-endpoint or --autoConnect (Chrome 144+).
When to skip:
- You need Firefox or Safari: the project is built on Chrome DevTools and targets Chrome.
- You want a general-purpose automation or test runner across browsers; Playwright MCP is the closer fit.
- You cannot run Node.js 20.19 or newer, which the README lists as a requirement.
firefox-devtools-mcpBrowser Automation · ★ 516
AI-driven browser automation for testing and scraping
02
Side-by-Side Comparison
Field
chrome-devtools-mcpfirefox-devtools-mcpCategory
Browser Automation
Browser Automation
Stars
★ 54.0k
★ 516
License
Apache-2.0
MIT
Install Command
npx -y chrome-devtools-mcp@latest
npx firefox-devtools-mcp@latest
Updated
1d ago
1d ago
Open Source
Yes
Yes
Tags
Chrome DevTools, AI Assistant, Browser Automation
claude-code, firefox, mcp
03
Features
chrome-devtools-mcp01Get performance insights using Chrome DevTools
02Advanced browser debugging (network, screenshots, console)
03Reliable automation using Puppeteer
04Input automation (click, drag, fill, etc.)
05Navigation automation (new page, navigate, wait for, etc.)
firefox-devtools-mcp01Automate Firefox via WebDriver BiDi
02Snapshot-based interaction with UIDs for clicking, filling, etc.
03Always-on network and console message capture
04Privileged context and extension management tools
05Supports headless mode, custom viewport, and connection to existing Firefox
04
Use Cases
chrome-devtools-mcp↳Automating browser interactions for testing or data extraction
↳Debugging web applications by analyzing network requests and console messages
↳Analyzing website performance by recording traces and extracting insights
firefox-devtools-mcp↳AI-driven browser automation for testing and scraping
↳Integrating browser control into AI coding assistants
↳Automated web interaction for debugging and monitoring
05
Best For
chrome-devtools-mcpMost PopularEssentialTrending
firefox-devtools-mcpTrending
FAQ
FAQ
What is the difference between chrome-devtools-mcp and firefox-devtools-mcp?
Both chrome-devtools-mcp and firefox-devtools-mcp are in the Browser Automation category. chrome-devtools-mcp has 54.0k stars, while firefox-devtools-mcp has 516 stars.
Which is better, chrome-devtools-mcp or firefox-devtools-mcp?
The best choice depends on your use case. Choose chrome-devtools-mcp if Automating browser interactions for testing or data extraction, and firefox-devtools-mcp if AI-driven browser automation for testing and scraping.
Is chrome-devtools-mcp free or open source?
Yes, chrome-devtools-mcp is open source on GitHub (Apache-2.0).
Is firefox-devtools-mcp free or open source?
Yes, firefox-devtools-mcp is open source on GitHub (MIT).
Cloud Infrastructure
AdDeploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.
→