Chrome DevTools MCP alternatives
6 servers that overlap with Chrome DevTools MCP. Compared on install command, provenance, and the tags they share — not on a feature checklist nobody maintains.
What these have in common
All of them overlap with Chrome DevTools MCP on at least one capability tag. Overlap is not equivalence: two servers can both say "database" and solve different problems. Read the full entry for what the current one is actually for before switching.
Side by side
| Server | Install | Source | Shared tags |
|---|---|---|---|
| Chrome DevTools MCP | npx -y chrome-devtools-mcp@latest | Official | browser, performance, debugging |
| Everything | npx -y @modelcontextprotocol/server-everything | Official | testing, reference, debugging |
| Puppeteer | npx -y @modelcontextprotocol/server-puppeteer | Official | browser, screenshots, archived |
| Rollbar MCP | npx -y @rollbar/mcp-server | Official | errors, monitoring, debugging |
| Playwright MCP | npx -y @playwright/mcp@latest | Community | browser, testing, automation |
| Context Mode | npx -y context-mode | Community | context, memory, performance |
| Next.js DevTools MCP | npx -y next-devtools-mcp | Community | nextjs, frontend, debugging |
How to choose
Prefer the official server when one exists, unless its install path or auth model does not fit. Prefer the smaller surface area: a server that exposes four tools you use beats one that exposes forty you do not, because every definition costs context on every request.