Home/Compare/chrome-devtools-mcp vs agents

Comparison

chrome-devtools-mcp vs agents

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 agents if the agents tool is a marketplace for plugins that enhances multiple AI agents, offering integration and management capabilities across several platforms, including Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot.

Markdown twin · chrome-devtools-mcp alternatives · agents alternatives

GraphCanon updated 2d

chrome-devtools-mcp logo

chrome-devtools-mcp

ChromeDevTools/chrome-devtools-mcp

48kpushed Jul 24, 2026
vs
agents logo

agents

wshobson/agents

39kpushed Aug 18, 2026

Trust & integrity

Signalchrome-devtools-mcpagents
Maintenance
Very active (1d since push)
As of 3w · github_public_v1
Very active (1d since push)
As of 2d · github_public_v1
Provenance
Not a fork · Organization account
As of 3w · github_public_v1
Not a fork · Personal account
As of 2d · 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
agents
Multi-harness agentic plugin marketplace for various AI agents

Stars

chrome-devtools-mcp
48k
agents
39k

Forks

chrome-devtools-mcp
3.2k
agents
4.1k

Open issues

chrome-devtools-mcp
111
agents
5

Language

chrome-devtools-mcp
TypeScript
agents
Python

Adopt for

chrome-devtools-mcp
chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
agents
The agents tool is a marketplace for plugins that enhances multiple AI agents, offering integration and management capabilities across several platforms, including Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot

Persona

chrome-devtools-mcp
-
agents
-

Runtime

chrome-devtools-mcp
-
agents
-

License

chrome-devtools-mcp
Apache-2.0
agents
MIT

Last pushed

chrome-devtools-mcp
Jul 24, 2026
agents
Aug 18, 2026

Categories

chrome-devtools-mcp
Developer Tools
agents
AI Agents, Developer Tools

Trust and health

Open issues (now)

chrome-devtools-mcp
111
agents
5

Stars delta

chrome-devtools-mcp
Unknown
agents
+860 (30d)

Open issues delta

chrome-devtools-mcp
Unknown
agents
+2 (30d)

Owner type

chrome-devtools-mcp
Organization
agents
User

Full report

chrome-devtools-mcp
Trust report

Choose chrome-devtools-mcp if…

  • chrome-devtools-mcp is primarily TypeScript; agents is Python.
  • License: chrome-devtools-mcp is Apache-2.0, agents is MIT.
  • Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging.
  • chrome-devtools-mcp ships an MCP server manifest.
  • - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome

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 agents if…

  • agents is primarily Python; chrome-devtools-mcp is TypeScript.
  • License: agents is MIT, chrome-devtools-mcp is Apache-2.0.
  • Tags unique to agents: agent-skills, agentic-ai, automation, prompt-engineering.
  • Also covers AI Agents.
  • You are working specifically within the ecosystems of Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot, or Gemini CLI, as it provides tailored plugins for these environments

When NOT to use agents

  • You are working solely within a niche environment that isn't one of the supported platforms (like Claude Code, Codex CLI, etc.) because it may not offer compatible plugins or extensive support
  • Your project requirements do not include interoperability between multiple AI agents and you only need to leverage functionalities from a single AI agent with a robust in-built plugin ecosystem

Explore

Sources

Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.

GitHub stars on cards: chrome-devtools-mcp 48k · agents 39k (synced Jul 26, 2026).

Common questions

What is the difference between chrome-devtools-mcp and agents?
chrome-devtools-mcp: Developer tools to enhance coding efficiency and debugging capabilities. agents: Multi-harness agentic plugin marketplace for various AI agents. See the comparison table for live GitHub stats and shared categories.
When should I choose chrome-devtools-mcp over agents?
Choose chrome-devtools-mcp over agents when chrome-devtools-mcp is primarily TypeScript; agents is Python; License: chrome-devtools-mcp is Apache-2.0, agents is MIT; Tags unique to chrome-devtools-mcp: browser, chrome, chrome-devtools, debugging; chrome-devtools-mcp ships an MCP server manifest; - When your project is heavily dependent on browser interactions and requires advanced debugging capabilities specific to Chrome.
When should I choose agents over chrome-devtools-mcp?
Choose agents over chrome-devtools-mcp when agents is primarily Python; chrome-devtools-mcp is TypeScript; License: agents is MIT, chrome-devtools-mcp is Apache-2.0; Tags unique to agents: agent-skills, agentic-ai, automation, prompt-engineering; Also covers AI Agents; You are working specifically within the ecosystems of Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot, or Gemini CLI, as it provides tailored plugins for these environments.
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 agents?
You are working solely within a niche environment that isn't one of the supported platforms (like Claude Code, Codex CLI, etc.) because it may not offer compatible plugins or extensive support Your project requirements do not include interoperability between multiple AI agents and you only need to leverage functionalities from a single AI agent with a robust in-built plugin ecosystem
Is chrome-devtools-mcp or agents more popular on GitHub?
chrome-devtools-mcp has more GitHub stars (47,594 vs 38,928). Stars measure visibility, not whether either tool fits your constraints.
Are chrome-devtools-mcp and agents open source?
Yes - both are open-source projects on GitHub (chrome-devtools-mcp: Apache-2.0, agents: MIT).
Where can I find alternatives to chrome-devtools-mcp or agents?
GraphCanon lists graph-backed alternatives at chrome-devtools-mcp alternatives and agents alternatives (chrome-devtools-mcp markdown twin, agents 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 agents?
chrome-devtools-mcp: Very active. agents: 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 agents?
GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: chrome-devtools-mcp trust report; agents trust report.

Was this helpful?

Anonymous feedback helps us improve pages and translations.