code-memory
★ 41
vs
trace-mcp
★ 82
code-memory vs trace-mcp
code-memory: code-memory is a deterministic, high-precision code intelligence layer exposed as a Model Context Protocol (MCP) server, designed to provide accurate and token-efficient code context for LLMs. It runs entirely locally, indexing codebases for semantic search, architecture understanding, and Git history analysis, addressing the cost and inaccuracy of traditional context retrieval methods.; trace-mcp: trace-mcp is a framework-aware code intelligence MCP server that builds cross-language dependency graphs from source code. It enables AI agents to understand framework-specific relationships, track request flows, analyze change impact, and remember past decisions across sessions, significantly reducing token usage.
01
TL;DR
Choose code-memory if…Finding definitions, references, and understanding code structure within a codebase
Choose trace-mcp if…Understanding full-stack web applications with cross-language relationships
02
Side-by-Side Comparison
03
Features
code-memory01Fully local operation without API keys, leveraging sentence-transformers for embeddings
02High token efficiency (up to 50% saving) through precise code retrieval instead of dumping entire files
03Deep code understanding via AST parsing for multiple programming languages
04Multi-faceted codebase analysis with dedicated tools for code, documentation, and Git history search
trace-mcp01Framework-aware dependency graph across languages
02Code-linked decision memory
03Cross-session intelligence and context carryover
04Change impact analysis with risk scoring
05Up to 99% token reduction
04
Use Cases
code-memory↳Finding definitions, references, and understanding code structure within a codebase
↳Understanding architectural patterns and workflows of a project
↳Debugging regressions and understanding developer intent through Git history
↳Performing semantic searches across code, documentation, and docstrings
trace-mcp↳Understanding full-stack web applications with cross-language relationships
↳Impact analysis for changes across multiple languages and frameworks
↳Reducing token consumption and context window pressure in large codebases
05
Best For
code-memoryTrendingRAG / Knowledge BaseMemory & Context
trace-mcpTrendingCode AssistantObservability
FAQ
FAQ
What is the difference between code-memory and trace-mcp?
Both code-memory and trace-mcp are in the RAG / Knowledge Base category. code-memory has 41 stars, while trace-mcp has 82 stars.
Which is better, code-memory or trace-mcp?
The best choice depends on your use case. Choose code-memory if Finding definitions, references, and understanding code structure within a codebase, and trace-mcp if Understanding full-stack web applications with cross-language relationships.
Is code-memory free or open source?
Yes, code-memory is open source on GitHub (MIT).
Is trace-mcp free or open source?
Yes, trace-mcp is open source on GitHub (MIT).
→