MCP server · Memory + knowledge

CommunitySource ValidatedLocal executionMITUpdated August 2026

Codebase Memory MCP

A native, local MCP server that indexes a repository into a persistent knowledge graph — functions, classes, call chains, routes — for fast queries.

InstallSource repository

Quick verdict

Worth it for agents that live in a big codebase. Install it from a release or npm, run the built-in installer, and index the repo you actually work in.

  • MaintainerDeusData (community)
  • Security scopeLocal execution
  • Transportsstdio
  • Install channelnpm · codebase-memory-mcp
  • EvidenceSource Validated
  • LicenseMIT · Open source

Codebase Memory MCP (DeusData) indexes a codebase into a persistent, local knowledge graph of functions, classes, call chains, HTTP routes and cross-service links, then answers structural questions over it: search_graph, query_graph (a read-only openCypher subset), trace_path, get_architecture, detect_changes and more — 15 tools in all. It is a single native binary (pure C, no language runtime), speaks MCP over stdio, and keeps its index in SQLite under ~/.cache/codebase-memory-mcp/ plus a .codebase-memory/ artifact inside the indexed repo. Distributed as pre-built releases and through npm, PyPI, Homebrew, Scoop, winget, Chocolatey and AUR; the npm package is a wrapper that downloads and checksum-verifies the release binary. codebase-memory-mcp install writes the MCP entry into every coding agent it detects.

MCP security best practices

Install Codebase Memory MCP

Config entry (mcpServers)
{
  "mcpServers": {
    "codebase-memory-mcp": {
      "command": "<PATH_TO_CODEBASE_MEMORY_MCP>",
      "args": []
    }
  }
}

npm install -g codebase-memory-mcp (a wrapper that downloads the verified native binary), the upstream install.sh / install.ps1, Homebrew, Scoop or winget all put the codebase-memory-mcp binary on your PATH; then `codebase-memory-mcp install` configures every coding agent it detects. The manual entry below points a client at the binary's absolute path.

Credentials

No credentials required.

Verified configurations

Not run by us yet. This profile is Source Validated: the install channel, config entry, credentials and license were checked against the source and upstream metadata, but no configuration has been installed, discovered and executed in a recorded environment. When one is, it appears here with the eight scope dimensions below.

Best for

Coding agents working in large or multi-service repositories that need to answer 'who calls this' and 'what changed' structurally, across sessions, without re-reading files every turn.

Why use it

The graph persists between sessions and queries return in sub-millisecond time, so an agent spends tokens on the answer rather than on re-scanning the tree. Everything runs locally — no hosted service, no API key — and one install command wires it into dozens of clients at once.

Tradeoffs

It reads your entire codebase, writes to your agents' configuration files, spawns a background daemon and stores an index on disk — by design, but understand it before installing. Initial indexing scales with repository size, tools/list marks most tools as potentially mutating out of caution, and the release binary has been flagged as a false positive by Microsoft Defender. Note the upstream docs disagree on whether it phones home for update checks (SECURITY.md says it requests release metadata after initialize; the README says it never does).

Upstream state

npm package published · repository active · in the official MCP Registry (active). Lifecycle is derived from a committed upstream snapshot at build time, never authored by hand.

Official MCP Registry name: io.github.DeusData/codebase-memory-mcp

Editorial review

Reviewed byOpenSourcesAI EditorialLast updatedAugust 2026SourcesDeusData/codebase-memory-mcp README — install paths, manual MCP entry, tool table, security and trust section, storage locations; DeusData/codebase-memory-mcp SECURITY.md — what it reads, writes and spawns; update-check behaviour; npm: codebase-memory-mcp; Official MCP Registry entry io.github.DeusData/codebase-memory-mcp

Grade B — Source Validated. Re-review is due by 2027-02-16. Config entries, credential names and package status can change upstream; verify against the source repository before granting an agent access.

Sources

  • Context7Upstash's MCP server that puts current, version-specific library docs and code examples in the prompt so a coding agent stops guessing at APIs.
  • MemoryReference MCP server that gives an agent persistent memory as a local knowledge graph — entities, relations and observations stored in a JSONL file.
  • Notion MCPSearch, read and update authorized Notion workspace content through Notion's official hosted MCP server.

Related guides

All MCP servers →