Log inSubmit server
Codebase Memory MCP logo

Codebase Memory MCP

by DeusData

Indexes repositories into a local knowledge graph for symbol search, call tracing, architecture analysis, and change impact review.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Codebase Memory MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "deusdata-codebase-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "codebase-memory-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

DeusData/codebase-memory-mcp builds a persistent local knowledge graph from source code and related project files, exposing repository intelligence through MCP tools. It combines tree-sitter parsing with Hybrid LSP type resolution, then supports symbol search, Cypher graph queries, call-path tracing, architecture views, snippets, and change analysis. Use it when an agent needs relationships and structure across a codebase rather than repeated raw file searches. Indexes and queries run locally, with no hosted service or API key required.

Use cases

  • Index a repository for local code-aware agent sessions
  • Find symbols and their callers across services
  • Trace dependencies and data flow before changing code
  • Compare indexed snapshots to review structural changes
  • Inspect architecture, coverage gaps, and project hotspots

Key features

  • Persistent local repository knowledge graph
  • BM25, regex, semantic, and graph-ranked code search
  • Read-only Cypher queries with pagination
  • Caller, callee, data-flow, and cross-service tracing
  • Architecture summaries and Git change impact analysis
  • Coverage diagnostics and indexed project management

Tools17

What Codebase Memory MCP lets your agent do. Expand a tool for its parameters.

Verified live~3.7k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

96/96 checks healthy over the last 77d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · codebase-memory-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars47kStargazers on the source repository.
npm downloads36kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Tools exposed17Callable tools this server registers over MCP.
Directory activity1 installs · 1 upvotesConfig copies, upvotes, and views on AllMCPs.

How Codebase Memory MCP works

What DeusData/codebase-memory-mcp does

DeusData/codebase-memory-mcp turns a repository into a persistent graph of code and surrounding technical artifacts. The graph can represent symbols, declarations, calls, inheritance, implementations, usage relationships, HTTP routes, and links across services. It also works with documentation, configuration, infrastructure files, architecture decisions, and other supported project formats.

The MCP surface is intended for code agents that need to locate an unfamiliar feature, inspect how components depend on one another, follow a call across service boundaries, or estimate the impact of a change. Results retain repository-relative paths, qualified names, source lines, relationship types, and coverage information where applicable.

How it works

Indexing uses vendored tree-sitter grammars together with Hybrid LSP-based type resolution for supported languages. The resulting graph is stored locally and remains available between sessions. A repository can be indexed with different semantics: full and moderate modes include more relationship information, while fast mode omits some semantics. Cross-repository intelligence can link services when indexing multiple projects.

Graph-oriented tools return bounded, paged results. query_graph accepts read-only Cypher for multi-hop traversal, aggregation, complexity checks, and cross-service analysis. Continuation cursors allow an agent to retrieve additional pages. trace_path follows callers, callees, data flow, or cross-service paths, while detect_changes maps a Git diff to affected files and related graph impact.

Coverage is surfaced rather than assumed. Index status and coverage checks report gaps, freshness, and relevant paths, and the missed graph can expose files flagged during indexing. A clean result is not proof that every file or relationship was captured.

Setup and configuration

The project can be launched with the package command:

Terminal
npx codebase-memory-mcp

The native release is distributed as a static binary and is available for macOS, Linux, and Windows. The documented installer for macOS and Linux is:

Terminal
curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bash

The native runtime does not require Docker or a language runtime. Indexing and graph queries do not require a hosted service or API key. The installer can configure supported agent clients, along with applicable guidance, skills, profiles, and hooks.

Tools and capabilities

  • index_repository creates or updates a repository graph and reports coverage gaps.
  • search_graph supports BM25, regular-expression name or qualified-name filters, and semantic queries. Results include symbol identity, locations, and incoming or outgoing relationships.
  • query_graph runs read-only Cypher with bounded, cursor-based output.
  • trace_path follows code relationships and returns hop, relation, total, and continuation data.
  • get_code_snippet retrieves bounded source or outlines for indexed symbols; get_file_outline lists declarations in source order.
  • get_graph_schema reports node and edge counts, with optional diagnostic property details.
  • compare_graphs compares indexed snapshots using stable node and edge identities.
  • get_architecture summarizes languages, packages, entry points, dependencies, routes, layers, clusters, cycles, hotspots, boundaries, or file trees.
  • search_code provides graph-ranked text search for symbols, bounded source, or paths.
  • list_projects, delete_project, and index_status manage indexed projects and readiness information.
  • check_index_coverage checks path or scope coverage and freshness; detect_changes analyzes Git changes.
  • manage_adr outlines, reads, or replaces architecture decision records.
  • ingest_traces validates and counts traces, but does not create graph edges from them.

Limitations and notes

Several responses are deliberately bounded. Graph queries default to a visible row limit, and snapshot comparisons also enforce item and byte budgets; totals and truncation reasons accompany these results. Large source containers are returned as outlines unless a fuller bounded request is made.

Tracing excludes tests and resolver evidence by default. Coverage, status, and freshness checks are best-effort, so cited paths should be verified when completeness matters. The visual CBM Lens companion is a separate open-beta component; the MCP server is the core interface for agent access.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Codebase Memory MCP

DeusData/codebase-memory-mcp is an MCP server that connects coding agents to a persistent local graph of source code, documentation, configuration, and infrastructure. Its main tools index repositories, search symbols, run read-only Cypher, trace call paths, retrieve snippets, inspect architecture, check coverage, and analyze Git changes without a hosted service.

Install it with `npx codebase-memory-mcp`, or use the native installer on macOS and Linux. The native distribution is a static binary for macOS, Linux, and Windows, and does not require Docker or a language runtime.

No, indexing and graph queries run locally without a hosted service or API key. The server stores and analyzes repository data on the machine where it runs.

Use `trace_path` for caller, callee, data-flow, or cross-service paths, or use `search_graph` to find symbols and their relationships. `query_graph` supports read-only Cypher for multi-hop and aggregation analysis, with paged results for larger traversals.

Yes. `index_status` and `check_index_coverage` report readiness, freshness, and coverage details, while `detect_changes` maps a Git diff to files and graph impact. Coverage results are best-effort and should not be treated as proof of completeness.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewCodebase Memory MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/deusdata-codebase-memory-mcp?style=directory)](https://allmcps.com/mcp/deusdata-codebase-memory-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/deusdata-codebase-memory-mcp"><img src="https://allmcps.com/api/badge/deusdata-codebase-memory-mcp?style=directory" alt="Codebase Memory MCP on AllMCPs" /></a>