Chrome DevTools MCP vs Firefox DevTools MCP
Both are browser automation MCP servers, and we ran both through the same test (click reveal) in each app. Chrome DevTools MCP passed 4 of 4 apps we tested it in; Firefox DevTools MCP passed 3 of 3.
Test results side by side
| Chrome DevTools MCP | Firefox DevTools MCP | |
|---|---|---|
| Claude Code | Passed 2026-10-20 | Passed 2026-10-23 |
| Cursor | Passed 2026-10-20 | Passed 2026-10-23 |
| Claude Desktop | Passed 2026-10-20 | Not tested yet |
| ChatGPT (Codex) | Passed 2026-10-20 | Passed 2026-10-23 |
| Tools exposed (protocol check) | 32 tools | 35 tools |
| GitHub stars | 53,544 | 509 |
| License | Apache-2.0 | NOASSERTION |
| Last push | 2026-10-14 | 2026-10-20 |
Results from our own harness runs, dated per cell. Stars and last push from GitHub at our last data refresh. We don’t pick a winner here: which one fits depends on your app and setup.
What each does
Chrome DevTools MCP: Google's Chrome DevTools server: browse, inspect network/console and record performance traces in Chrome.
Firefox DevTools MCP: Mozilla's server that lets an agent drive and inspect Firefox over WebDriver BiDi: browse, fill forms, read the console and network, and debug web pages.
