Chrome DevTools for agents vs codebase-memory-mcp
Side-by-side comparison of two AI agent tools
Short answer
- codebase-memory-mcp is growing faster: +1,725 GitHub stars in the last 30 days vs +1,110 for Chrome DevTools for agents.
- Pick Chrome DevTools for agents for: chrome DevTools for coding agents. Pick codebase-memory-mcp for: mCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP.
From GitHub data refreshed daily.
C
Chrome DevTools for agentsopen-source
Chrome DevTools for coding agents
c
codebase-memory-mcpopen-source
MCP server indexing codebases into a persistent knowledge graph with tree-sitter and hybrid LSP
Metrics
| Chrome DevTools for agents | codebase-memory-mcp | |
|---|---|---|
| Stars | 52.9k | 45.7k |
| Star velocity /mo | 1.1k | 1.7k |
| Commits (90d) | 350 | 2.1k |
| Releases (6m) | 10 | 10 |
| Overall score | 0.8440977823877475 | 0.906371149690189 |
FAQ
- Which is more popular, Chrome DevTools for agents or codebase-memory-mcp?
- Chrome DevTools for agents has more GitHub stars (52,884 vs 45,666).
- Which is more actively developed, Chrome DevTools for agents or codebase-memory-mcp?
- codebase-memory-mcp had more commits in the last 90 days (2,093 vs 350).
- Should I use Chrome DevTools for agents or codebase-memory-mcp?
- Compare their capabilities, limitations and "best for" notes above. Both are open source, so trying each on a small task is the fastest way to decide.