---
title: "chrome-devtools-mcp vs codehamr"
type: "comparison"
canonical_url: "https://www.graphcanon.com/compare/chromedevtools-chrome-devtools-mcp-vs-codehamr-codehamr"
tools: ["chromedevtools-chrome-devtools-mcp", "codehamr-codehamr"]
---

# chrome-devtools-mcp vs codehamr

*GraphCanon updated Aug 25, 2026*

## 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.

[chrome-devtools-mcp](https://npmjs.org/package/chrome-devtools-mcp) reports 50k GitHub stars, 3.5k forks, and 90 open issues, last pushed Aug 25, 2026. [codehamr](https://codehamr.com) has 207 stars, 18 forks, and 0 open issues, last pushed Jul 12, 2026. Figures are from public GitHub metadata via [chrome-devtools-mcp's repository](https://github.com/ChromeDevTools/chrome-devtools-mcp) and [codehamr's repository](https://github.com/codehamr/codehamr).

| | [chrome-devtools-mcp](/tools/chromedevtools-chrome-devtools-mcp.md) | [codehamr](/tools/codehamr-codehamr.md) |
| --- | --- | --- |
| Tagline | Developer tools to enhance coding efficiency and debugging capabilities | A minimal, local-first coding agent for the terminal |
| Stars | 49,700 | 207 |
| Forks | 3,480 | 18 |
| Open issues | 90 | 0 |
| Language | TypeScript | Go |
| Adopt for | chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript. | Codehamr is an AI-based coding assistant tool built to enhance terminal coding productivity, emphasizing minimalism and local processing. |
| Persona | - | - |
| Runtime | - | - |
| License | Apache-2.0 | MIT |
| Categories | Developer Tools | AI Agents, Developer Tools |

## Trust and health

_Sourced signals - not a safety guarantee. No winner column._

| | [chrome-devtools-mcp](/tools/chromedevtools-chrome-devtools-mcp.md) | [codehamr](/tools/codehamr-codehamr.md) |
| --- | --- | --- |
| Maintenance | Very active (96%) | Steady (60%) |
| Days since push | 0d | 31d |
| Open issues (now) | 90 | 0 |
| Stars delta | +2.1k (30d) | Unknown |
| Open issues delta | -21 (30d) | Unknown |
| Full report | [trust report](/tools/chromedevtools-chrome-devtools-mcp/trust.md) | [trust report](/tools/codehamr-codehamr/trust.md) |

## Decision facts: chrome-devtools-mcp

- **Adopt for:** chrome-devtools-mcp offers specialized tools for browser-based development and debugging aimed specifically at coding agents using TypeScript.

## Decision facts: codehamr

- **Adopt for:** Codehamr is an AI-based coding assistant tool built to enhance terminal coding productivity, emphasizing minimalism and local processing.

## Choose when

### 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

### 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 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 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.

## 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 (49,700 vs 207). 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](/tools/chromedevtools-chrome-devtools-mcp/alternatives) and [codehamr alternatives](/tools/codehamr-codehamr/alternatives) ([chrome-devtools-mcp markdown twin](/tools/chromedevtools-chrome-devtools-mcp/alternatives.md), [codehamr markdown twin](/tools/codehamr-codehamr/alternatives.md)), 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](/compare/chromedevtools-chrome-devtools-mcp-vs-codehamr-codehamr.md) 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: Steady. 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](/tools/chromedevtools-chrome-devtools-mcp/trust); [codehamr trust report](/tools/codehamr-codehamr/trust).

---

**Machine-readable endpoints**

- JSON: [`/api/graphcanon/graph?tool=chromedevtools-chrome-devtools-mcp`](/api/graphcanon/graph?tool=chromedevtools-chrome-devtools-mcp)
- LLM index: [/llms.txt](/llms.txt)
- Full corpus: [/llms-full.txt](/llms-full.txt)

_GraphCanon - The knowledge graph for AI development. https://www.graphcanon.com/_
