Comparison
chrome-devtools-mcp vs playwright-mcp
Verdict
Pick chrome-devtools-mcp if chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript; pick playwright-mcp if playwright MCP server implementation in TypeScript under Apache-2.0 license.
Markdown twin · chrome-devtools-mcp alternatives · playwright-mcp alternatives
GraphCanon updated 4w
vs
Trust & integrity
| Signal | chrome-devtools-mcp | playwright-mcp |
|---|---|---|
| Maintenance | Very active (1d since push) As of 4w · github_public_v1 | Very active (0d since push) As of 4w · github_public_v1 |
| Provenance | Not a fork · Organization account As of 4w · github_public_v1 | Not a fork · Organization account As of 4w · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of 1mo · osv@v1 | No lockfile (source not queried) As of 1mo · osv@v1 |
| deps.dev advisories | Not queried deps.dev@v1 | Not queried deps.dev@v1 |
| OpenSSF Scorecard | Not queried openssf-scorecard@v1 | Not queried openssf-scorecard@v1 |
Tagline
- chrome-devtools-mcp
- Developer tools to enhance coding efficiency and debugging capabilities
- playwright-mcp
- Playwright MCP server
Stars
- chrome-devtools-mcp
- 48k
- playwright-mcp
- 35k
Forks
- chrome-devtools-mcp
- 3.2k
- playwright-mcp
- 3.0k
Open issues
- chrome-devtools-mcp
- 111
- playwright-mcp
- 6
Language
- chrome-devtools-mcp
- TypeScript
- playwright-mcp
- TypeScript
Adopt for
- chrome-devtools-mcp
- chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
- playwright-mcp
- Playwright MCP server implementation in TypeScript under Apache-2.0 license.
Persona
- chrome-devtools-mcp
- -
- playwright-mcp
- -
Runtime
- chrome-devtools-mcp
- -
- playwright-mcp
- -
License
- chrome-devtools-mcp
- Apache-2.0
- playwright-mcp
- Apache-2.0
Last pushed
- chrome-devtools-mcp
- Jul 24, 2026
- playwright-mcp
- Jul 25, 2026
Categories
- chrome-devtools-mcp
- Developer Tools
- playwright-mcp
- Developer Tools
Trust and health
Days since push
- chrome-devtools-mcp
- 1d
- playwright-mcp
- 0d
Open issues (now)
- chrome-devtools-mcp
- 111
- playwright-mcp
- 6
Full report
- chrome-devtools-mcp
- Trust report
- playwright-mcp
- Trust report
Shared compatibility
- Node.js · chrome-devtools-mcp: Node.js runtime · playwright-mcp: Node.js runtime
Choose chrome-devtools-mcp if…
- Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging.
- - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome
- More GitHub stars (48k vs 35k) - visibility, not fit.
When NOT to use chrome-devtools-mcp
- - If your development environment does not revolve around Chrome or if browser compatibility across different browsers is a primary concern
- - When you are working on non-TypeScript projects, as this tool may not provide the same level of utility and customization options
Choose playwright-mcp if…
- Tags unique to playwright-mcp: playwright.
- playwright-mcp ships Docker support for self-hosted deployment.
- Need a TypeScript-based Playwright MCP server to scale your automated browser testing.
When NOT to use playwright-mcp
- Don't require TypeScript or are looking for a different language implementation of playwright MCP services.
- Do not need multi-client support or can manage with single-client interactions without needing an MCP server setup.
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (ChromeDevTools/chrome-devtools-mcp) · observed Jul 26, 2026
- GitHub forks (ChromeDevTools/chrome-devtools-mcp) · observed Jul 26, 2026
- Last push (ChromeDevTools/chrome-devtools-mcp) · observed Jul 24, 2026
- License file (Apache-2.0) · observed Jul 26, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (microsoft/playwright-mcp) · observed Jul 26, 2026
- GitHub forks (microsoft/playwright-mcp) · observed Jul 26, 2026
- Last push (microsoft/playwright-mcp) · observed Jul 25, 2026
- License file (Apache-2.0) · observed Jul 26, 2026
- Decision facts (enrichment) · observed Jul 12, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
GitHub stars on cards: chrome-devtools-mcp 48k · playwright-mcp 35k (synced Jul 26, 2026).
Common questions
- What is the difference between chrome-devtools-mcp and playwright-mcp?
- chrome-devtools-mcp: Developer tools to enhance coding efficiency and debugging capabilities. playwright-mcp: Playwright MCP server. See the comparison table for live GitHub stats and shared categories.
- When should I choose chrome-devtools-mcp over playwright-mcp?
- Choose chrome-devtools-mcp over playwright-mcp when Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging; - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome; More GitHub stars (48k vs 35k) - visibility, not fit.
- When should I choose playwright-mcp over chrome-devtools-mcp?
- Choose playwright-mcp over chrome-devtools-mcp when Tags unique to playwright-mcp: playwright; playwright-mcp ships Docker support for self-hosted deployment; Need a TypeScript-based Playwright MCP server to scale your automated browser testing.
- When should I avoid chrome-devtools-mcp?
- - If your development environment does not revolve around Chrome or if browser compatibility across different browsers is a primary concern - When you are working on non-TypeScript projects, as this tool may not provide the same level of utility and customization options
- When should I avoid playwright-mcp?
- Don't require TypeScript or are looking for a different language implementation of playwright MCP services. Do not need multi-client support or can manage with single-client interactions without needing an MCP server setup.
- Is chrome-devtools-mcp or playwright-mcp more popular on GitHub?
- chrome-devtools-mcp has more GitHub stars (47,594 vs 35,492). Stars measure visibility, not whether either tool fits your constraints.
- Are chrome-devtools-mcp and playwright-mcp open source?
- Yes - both are open-source projects on GitHub (chrome-devtools-mcp: Apache-2.0, playwright-mcp: Apache-2.0).
- Where can I find alternatives to chrome-devtools-mcp or playwright-mcp?
- GraphCanon lists graph-backed alternatives at chrome-devtools-mcp alternatives and playwright-mcp alternatives (chrome-devtools-mcp markdown twin, playwright-mcp markdown twin), ranked by typed relationship edges rather than popularity votes.
- Is there a machine-readable version of this comparison?
- Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
- Which is better maintained, chrome-devtools-mcp or playwright-mcp?
- chrome-devtools-mcp: Very active. playwright-mcp: Very active. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
- Where are the full trust reports for chrome-devtools-mcp and playwright-mcp?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: chrome-devtools-mcp trust report; playwright-mcp trust report.