Alternatives · MCP Servers
chrome-devtools-mcp alternatives
These records overlap with chrome-devtools-mcp's recorded tasks and have the same product type. The selection uses task text, then information completeness; stars and sponsorship do not set the order. Check the specific capability you need before switching.
Chrome DevTools for coding agents
Costs not checked · 57k stars · TypeScript · Open source · repository push Nov 2026
chrome-devtools-mcp's record says to avoid it if: You cannot expose browser contents to an agent — it can read any page data.
Task-related research candidates
Recorded task overlap: browser interaction; coding workflow. Compare the documented setup and limits before treating it as a substitute. The recorded use cases differ: chrome-devtools-mcp — Giving a coding agent live Chrome control for debugging and performance traces; Colab MCP — Letting a local coding agent use Colab's hosted runtime, including its accelerators, from your own terminal.
Recorded task overlap: browser interaction; coding workflow. Compare the documented setup and limits before treating it as a substitute. Recorded repository licenses differ: chrome-devtools-mcp — Apache-2.0; glance — MIT. Check the product and service terms separately.
Recorded task overlap: browser interaction. Compare the documented setup and limits before treating it as a substitute. The recorded use cases differ: chrome-devtools-mcp — Giving a coding agent live Chrome control for debugging and performance traces; Playwriter — Automating tasks that depend on your real, logged-in browser state.
Recorded task overlap: coding workflow. Compare the documented setup and limits before treating it as a substitute. The recorded use cases differ: chrome-devtools-mcp — Giving a coding agent live Chrome control for debugging and performance traces; context7 — Giving coding agents up-to-date library documentation via MCP.
Recorded task overlap: browser interaction. Compare the documented setup and limits before treating it as a substitute. The recorded use cases differ: chrome-devtools-mcp — Giving a coding agent live Chrome control for debugging and performance traces; browser-tools-mcp — Debugging a web application from an MCP-compatible editor, capturing browser logs and screenshots plus Lighthouse SEO, performance, accessibility and best-practice audits.
Recorded task overlap: browser interaction. Compare the documented setup and limits before treating it as a substitute. The recorded use cases differ: chrome-devtools-mcp — Giving a coding agent live Chrome control for debugging and performance traces; Draw.io MCP Server (community) — Iterating on a diagram with an agent while watching it change in the editor.
Recorded task overlap: browser interaction. Compare the documented setup and limits before treating it as a substitute. The recorded use cases differ: chrome-devtools-mcp — Giving a coding agent live Chrome control for debugging and performance traces; Chrome MCP Server (mcp-chrome) — Letting an assistant work in the browser you already use instead of a clean automation profile.
Recorded task overlap: coding workflow. Compare the documented setup and limits before treating it as a substitute. The recorded use cases differ: chrome-devtools-mcp — Giving a coding agent live Chrome control for debugging and performance traces; wigolo — Giving a coding agent web search and page fetching without a paid search API.
Frequently asked
- How were alternatives to chrome-devtools-mcp selected?
- Recorded task topics and meaningful shared terms qualify same-type candidates in the same category. Results are ordered by that overlap, then information completeness and a stable identifier. Sponsorship and GitHub stars do not participate. The method can miss suitable tools whose records lack task information.
- Does inclusion mean a tested replacement?
- No. These are catalogue-based research candidates. Check current sources, costs, permissions and deployment requirements, then test your own task. ASE has not run a performance benchmark of this shortlist.