Repository intelligenceRepositories
⌘K
Home / Repositories / DeusData/codebase-memory-mcp
MCP server · established

DeusData/codebase-memory-mcp

Local native code-intelligence MCP server that indexes repositories into a persistent structural knowledge graph and answers graph, architecture, impact, and source queries.

code intelligenceMCPknowledge graphs
GitHubMatrix
Installation GuideInstruction Manual

What it contains

A C executable with tree-sitter parsing, hybrid type resolution, persistent local indexes, 14 documented MCP tools, client installers, coordination daemon, and a built-in graph UI.

Typical uses

Give coding agents fast structural context, call paths, change impact, architecture summaries, code snippets, and cross-repository relationships without uploading the codebase.

Why people choose it

Choose it when repeated file-by-file exploration is expensive and structural graph queries are more useful than a one-time repository snapshot.

License
MIT
Maintenance
active
Latest release
See GitHub Releases
Last meaningful update
2026-08-18
Maturity
established
Production readiness
production

Classification

Subject domains

code intelligenceMCPknowledge graphs

Task categories

repository indexingcode searchchange impact

Project phases

discoveryimplementationreviewmaintenance

Secondary types

CLIlocal service

Select when

  • Need persistent structural knowledge across large or multi-repository codebases
  • Need call-path, architecture, or change-impact queries through MCP
  • Source code must remain local

Do not select when

  • Need semantic similarity over prose rather than code structure
  • Cannot allow a tool to read the repository and edit agent MCP configuration
  • A tiny repository does not justify persistent indexing
Implementation complexity
medium
Setup effort
low
Learning curve
medium
Confidence
high

Routing heuristic 100.0%

Routing specificity
5/5
Setup simplicity
5/5
Operational maturity
5/5
Composability
5/5
Local control
5/5
Security boundary clarity
5/5
First-party routing documentation
5/5

Strengths

  • Native Apple-silicon release
  • No language runtime or API key for normal use
  • Local persistent graph with documented security evidence

Poor-fit scenarios

  • Need semantic similarity over prose rather than code structure
  • Cannot allow a tool to read the repository and edit agent MCP configuration
  • A tiny repository does not justify persistent indexing

Limitations

  • Installer intentionally changes detected agent configuration
  • Structural analysis does not contain an LLM
  • Index accuracy varies with language grammar and resolvable program structure
src/mcp/

Index a repository into the persistent graph and hand subsequent freshness to auto-sync.

indexing
list_projects MCP tool
src/mcp/

List indexed projects and their current node and edge counts.

inventory
src/mcp/

Remove a selected project and its graph data after an explicit request.

index management
index_status MCP tool
src/mcp/

Report whether a project is indexing, ready, stale, or failed.

status
search_graph MCP tool
src/mcp/

Search graph nodes with label, name, file, degree, pagination, and other structural filters.

graph search
trace_path MCP tool
src/mcp/

Traverse incoming or outgoing call relationships to explain who calls a symbol and what it calls.

call graph
src/mcp/

Map a Git diff to affected symbols, blast radius, and a risk classification.

change impact
query_graph MCP tool
src/cypher/

Run a supported read-only Cypher-like query against the project graph.

Cypher
src/mcp/

Describe available labels, properties, relationship patterns, and counts before custom queries are written.

schema
src/mcp/

Return source for a function or method identified by its qualified name.

source code
src/mcp/

Summarize languages, packages, routes, hotspots, clusters, and architectural decisions.

architecture
search_code MCP tool
src/mcp/

Run grep-like text search over files in an indexed project.

text search
manage_adr MCP tool
src/mcp/

Create, read, update, and organize Architecture Decision Records under the project mutation guard.

ADR
ingest_traces MCP tool
src/mcp/

Ingest runtime traces that can validate or refine inferred HTTP-call relationships.

runtime traces
src/daemon/frontend.c

Explore the local repository graph visually through the built-in localhost interface.

visualization
Languages
C
Frameworks
MCP, tree-sitter, Hybrid LSP, openCypher read subset
Runtimes
Native static executable
Operating systems
macOS arm64/amd64, Linux arm64/amd64, Windows amd64
Installation methods
Verified release installer, package managers, or source build
Interfaces
MCP stdio server, CLI, local coordination daemon, localhost graph UI
Required credentials
None
External services
None for normal operation
Hardware
No special hardware
Major dependencies
Release-owned runtime assets; compiler and zlib only for source builds

Compatibility notes

The upstream release includes macOS arm64. The installer can configure detected agent clients and remove quarantine attributes, so inspect the downloaded script and back up agent configuration before running it.

One-sentence semantic summary

Local native code-intelligence MCP server that indexes repositories into a persistent structural knowledge graph and answers graph, architecture, impact, and source queries.

Capability keywords

codebase memoryknowledge graphMCPcall graphimpact analysistree-sitterlocal

User intent phrases

  • Need fast persistent structural code intelligence
  • Need code graph queries without uploading source

Negative match phrases

  • Need a vector database for natural-language documents
  • Do not permit agent-configuration changes

Differentiators

Ships a local native executable that combines broad tree-sitter parsing with lightweight semantic resolution and persistent graph queries.

Security considerations

The installer reads code and writes supported agent configuration, hooks, and skills. Review the installer, checksum provenance, and the exact clients it detects before activation.

Privacy considerations

Normal indexing and queries are documented as local with no telemetry or API key; diagnostic logs leave the machine only if the user chooses to share them.

Uncertainty

Unresolved items

None documented.

Inference notes

Routing guidance is an analyst synthesis based on the first-party repository and README.

Evidence

  • repository_metadata · Repository identity and current GitHub metadata checked on August 18, 2026.
  • readme · Primary first-party README inspected.

Repository usage guidance

installation summary
Download and inspect the macOS installer, run it, then restart the configured agent
basic usage summary
Index a repository once, query its schema and architecture, then use targeted search, path, snippet, and change tools
documented entry points
codebase-memory-mcp binary and MCP tools
key configuration files
Detected agent MCP configuration plus optional CBM environment variables
important directories
src/, docs/, local cache/index directory
documentation paths
README.md, docs/CONFIGURATION.md, SECURITY.md
example paths
scripts/test_mcp_interactive.py

Relationships

alternative
high
Both provide repository retrieval to agents. Codebase Memory emphasizes local structural graphs; Claude Context emphasizes embedding-backed semantic retrieval.

Recommended combinations

Use Repomix for a portable snapshot and Codebase Memory for live structural queries; avoid indexing secrets that the connected agent should not see.

Routing rules

rule_051: Need local persistent structural code intelligence through MCP P949

Rationale

Local native code-intelligence MCP server that indexes repositories into a persistent structural knowledge graph and answers graph, architecture, impact, and source queries.

Required conditions

Need persistent structural knowledge across large or multi-repository codebases

Preferred

DeusData/codebase-memory-mcp

Fallback

Choose the closest narrowly scoped existing repository only after comparing permissions and workflow ownership.