Comparison
chrome-devtools-mcp vs codehamr
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 codehamr if codehamr is an AI-based coding assistant tool built to enhance terminal coding productivity, emphasizing minimalism and local processing.
Markdown twin · chrome-devtools-mcp alternatives · codehamr alternatives
GraphCanon updated Sep 20, 2026
11views this month
vs
Trust & integrity
| Signal | chrome-devtools-mcp | codehamr |
|---|---|---|
| Maintenance | Very active (0d since push) As of Sep 20, 2026 · github_public_v1 | Very active (0d since push) As of Sep 20, 2026 · github_public_v1 |
| Provenance | Not a fork · Organization account As of Sep 20, 2026 · github_public_v1 | Not a fork · Organization account As of Sep 20, 2026 · github_public_v1 |
| OSV dependency advisories | No lockfile (source not queried) As of Jul 11, 2026 · osv@v1 | No lockfile (source not queried) As of Jul 15, 2026 · 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
- codehamr
- A minimal, local-first coding agent for the terminal
Stars
- chrome-devtools-mcp
- 52k
- codehamr
- 218
Forks
- chrome-devtools-mcp
- 4.3k
- codehamr
- 19
Open issues
- chrome-devtools-mcp
- 117
- codehamr
- 0
Language
- chrome-devtools-mcp
- TypeScript
- codehamr
- Go
Adopt for
- chrome-devtools-mcp
- chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.
- codehamr
- Codehamr is an AI-based coding assistant tool built to enhance terminal coding productivity, emphasizing minimalism and local processing.
Persona
- chrome-devtools-mcp
- -
- codehamr
- -
Runtime
- chrome-devtools-mcp
- -
- codehamr
- -
License
- chrome-devtools-mcp
- Apache-2.0
- codehamr
- MIT
Last pushed
- chrome-devtools-mcp
- Sep 20, 2026
- codehamr
- Sep 19, 2026
Categories
- chrome-devtools-mcp
- Developer Tools
- codehamr
- AI Agents, Developer Tools
Trust and health
Open issues (now)
- chrome-devtools-mcp
- 117
- codehamr
- 0
Stars delta
- chrome-devtools-mcp
- +4.7k (30d)
- codehamr
- +11 (30d)
Open issues delta
- chrome-devtools-mcp
- +6 (30d)
- codehamr
- 0 (30d)
Full report
- chrome-devtools-mcp
- Trust report
- codehamr
- Trust report
Choose chrome-devtools-mcp if…
- chrome-devtools-mcp is primarily TypeScript; codehamr is Go.
- License: chrome-devtools-mcp is Apache-2.0, codehamr 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 codehamr if…
- codehamr is primarily Go; chrome-devtools-mcp is TypeScript.
- License: codehamr is MIT, chrome-devtools-mcp is Apache-2.0.
- Tags unique to codehamr: ai-agent, coding-agent, local-llm.
- Also covers AI Agents.
- codehamr ships Docker support for self-hosted deployment.
- If you prefer tools that operate locally without relying on cloud services for their core functionality.
When NOT to use codehamr
- If your priority is using features provided by larger, more comprehensive AI agents that may require cloud connections.
- If you need advanced coding assistance not covered in the minimalistic approach of Codehamr.
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 Sep 20, 2026
- GitHub forks (ChromeDevTools/chrome-devtools-mcp) · observed Sep 20, 2026
- Last push (ChromeDevTools/chrome-devtools-mcp) · observed Sep 20, 2026
- License file (Apache-2.0) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 11, 2026
- GitHub stars (codehamr/codehamr) · observed Sep 20, 2026
- GitHub forks (codehamr/codehamr) · observed Sep 20, 2026
- Last push (codehamr/codehamr) · observed Sep 19, 2026
- License file (MIT) · observed Sep 20, 2026
- Decision facts (enrichment) · observed Jul 17, 2026
- Trust scan (lockfile / OSV) · observed Jul 15, 2026
GitHub stars on cards: chrome-devtools-mcp 52k · codehamr 218 (synced Sep 20, 2026).
Common questions
- What is the difference between chrome-devtools-mcp and codehamr?
- chrome-devtools-mcp: Developer tools to enhance coding efficiency and debugging capabilities. codehamr: A minimal, local-first coding agent for the terminal. See the comparison table for live GitHub stats and shared categories.
- When should I choose chrome-devtools-mcp over codehamr?
- Choose chrome-devtools-mcp over codehamr when chrome-devtools-mcp is primarily TypeScript; codehamr is Go; License: chrome-devtools-mcp is Apache-2.0, codehamr 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 codehamr over chrome-devtools-mcp?
- Choose codehamr over chrome-devtools-mcp when codehamr is primarily Go; chrome-devtools-mcp is TypeScript; License: codehamr is MIT, chrome-devtools-mcp is Apache-2.0; Tags unique to codehamr: ai-agent, coding-agent, local-llm; Also covers AI Agents; codehamr ships Docker support for self-hosted deployment; If you prefer tools that operate locally without relying on cloud services for their core functionality.
- 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 codehamr?
- If your priority is using features provided by larger, more comprehensive AI agents that may require cloud connections. If you need advanced coding assistance not covered in the minimalistic approach of Codehamr.
- Is chrome-devtools-mcp or codehamr more popular on GitHub?
- chrome-devtools-mcp has more GitHub stars (52,333 vs 218). Stars measure visibility, not whether either tool fits your constraints.
- Are chrome-devtools-mcp and codehamr open source?
- Yes - both are open-source projects on GitHub (chrome-devtools-mcp: Apache-2.0, codehamr: MIT).
- Where can I find alternatives to chrome-devtools-mcp or codehamr?
- GraphCanon lists graph-backed alternatives at chrome-devtools-mcp alternatives and codehamr alternatives (chrome-devtools-mcp markdown twin, codehamr 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 codehamr?
- chrome-devtools-mcp: Very active. codehamr: 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 codehamr?
- GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: chrome-devtools-mcp trust report; codehamr trust report.