Comparison
automa vs chrome-devtools-mcp
Verdict
Pick automa if automa is known for its ease of implementation and browser agnostic design enabling users to streamline tasks on multiple platforms; pick chrome-devtools-mcp if chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
Markdown twin · automa alternatives · chrome-devtools-mcp alternatives
GraphCanon updated 1w
vs
Trust & integrity
| Signal | automa | chrome-devtools-mcp |
|---|---|---|
| Maintenance | Slowing (160d since push) As of 1w · github_public_v1 | Very active (1d since push) As of 4w · github_public_v1 |
| Provenance | Not a fork · Organization account As of 1w · 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
- automa
- A browser extension for automating your browser by connecting blocks
- chrome-devtools-mcp
- Developer tools to enhance coding efficiency and debugging capabilities
Stars
- automa
- 22k
- chrome-devtools-mcp
- 48k
Forks
- automa
- 2.3k
- chrome-devtools-mcp
- 3.2k
Open issues
- automa
- 372
- chrome-devtools-mcp
- 111
Language
- automa
- Vue
- chrome-devtools-mcp
- TypeScript
Adopt for
- automa
- Automa is known for its ease of implementation and browser agnostic design enabling users to streamline tasks on multiple platforms.
- chrome-devtools-mcp
- chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
Persona
- automa
- -
- chrome-devtools-mcp
- -
Runtime
- automa
- -
- chrome-devtools-mcp
- -
License
- automa
- Other
- chrome-devtools-mcp
- Apache-2.0
Last pushed
- automa
- Mar 2, 2026
- chrome-devtools-mcp
- Jul 24, 2026
Categories
- automa
- Developer Tools
- chrome-devtools-mcp
- Developer Tools
Trust and health
Maintenance
- automa
- Slowing (36%)
- chrome-devtools-mcp
- Very active (96%)
Days since push
- automa
- 160d
- chrome-devtools-mcp
- 1d
Open issues (now)
- automa
- 372
- chrome-devtools-mcp
- 111
Full report
- automa
- Trust report
- chrome-devtools-mcp
- Trust report
Choose automa if…
- automa is primarily Vue; chrome-devtools-mcp is TypeScript.
- License: automa is Other, chrome-devtools-mcp is Apache-2.0.
- Tags unique to automa: automation, browser-automation, chrome-extension, firefox-extension.
- If you are working with Chrome or Firefox browsers and require the capability to interconnect blocks to automate repetitive, browser-based actions.
When NOT to use automa
- When specific automation tasks demand customization via coding rather than block connectivity since Automa is more suited for visual scripting.
- If your project involves non-browser-based workflows, as Automa's functionality is limited to browser extensions like Chrome and Firefox.
Choose chrome-devtools-mcp if…
- chrome-devtools-mcp is primarily TypeScript; automa is Vue.
- License: chrome-devtools-mcp is Apache-2.0, automa is Other.
- 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
Explore
Sources
Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.
- GitHub stars (AutomaApp/automa) · observed Aug 10, 2026
- GitHub forks (AutomaApp/automa) · observed Aug 10, 2026
- Last push (AutomaApp/automa) · observed Mar 2, 2026
- License file (Other) · observed Aug 10, 2026
- Decision facts (enrichment) · observed Jul 16, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
- 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 on cards: automa 22k · chrome-devtools-mcp 48k (synced Aug 10, 2026).
Common questions
- What is the difference between automa and chrome-devtools-mcp?
- automa: A browser extension for automating your browser by connecting blocks. chrome-devtools-mcp: Developer tools to enhance coding efficiency and debugging capabilities. See the comparison table for live GitHub stats and shared categories.
- When should I choose automa over chrome-devtools-mcp?
- Choose automa over chrome-devtools-mcp when automa is primarily Vue; chrome-devtools-mcp is TypeScript; License: automa is Other, chrome-devtools-mcp is Apache-2.0; Tags unique to automa: automation, browser-automation, chrome-extension, firefox-extension; If you are working with Chrome or Firefox browsers and require the capability to interconnect blocks to automate repetitive, browser-based actions.
- When should I choose chrome-devtools-mcp over automa?
- Choose chrome-devtools-mcp over automa when chrome-devtools-mcp is primarily TypeScript; automa is Vue; License: chrome-devtools-mcp is Apache-2.0, automa is Other; 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 avoid automa?
- When specific automation tasks demand customization via coding rather than block connectivity since Automa is more suited for visual scripting. If your project involves non-browser-based workflows, as Automa's functionality is limited to browser extensions like Chrome and Firefox.
- 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
- Is automa or chrome-devtools-mcp more popular on GitHub?
- chrome-devtools-mcp has more GitHub stars (47,594 vs 21,546). Stars measure visibility, not whether either tool fits your constraints.
- Are automa and chrome-devtools-mcp open source?
- Yes - both are open-source projects on GitHub (automa: Other, chrome-devtools-mcp: Apache-2.0).
- Where can I find alternatives to automa or chrome-devtools-mcp?
- GraphCanon lists graph-backed alternatives at automa alternatives and chrome-devtools-mcp alternatives (automa markdown twin, chrome-devtools-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, automa or chrome-devtools-mcp?
- automa: Slowing. chrome-devtools-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 automa and chrome-devtools-mcp?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: automa trust report; chrome-devtools-mcp trust report.