Persistent codebase knowledge graph. Survives session restarts and context compaction.
Connect Codebase Memory to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Persistent codebase knowledge graph. Survives session restarts and context compaction. The codebase memory mcp server is what makes that connection.
Built-in 3D graph visualization (UI variant) — explore your knowledge graph at localhost:9749
Installation goes through your MCP client rather than a global install: point it at codebase-memory-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Built — in graph visualization** — 3D interactive UI at localhost:9749 (optional UI binary variant)Infrastructure-as — code indexing** — Dockerfiles, Kubernetes manifests, and Kustomize overlays indexed as graph nodes with cross-references. Resource nodes for K8scodebase-memory-mcp — -.tar.gz (macOS/Linux) or .zip (Windows) — standardcodebase-memory-mcp-ui — -.tar.gz / .zip — with graph visualizationinstall.sh — ** add --ui (see Quick Start)PyPI — ** CBM_VARIANT=ui pip install codebase-memory-mcpManual — ** download the codebase-memory-mcp-ui-- archiveCypher — like queries**: MATCH (f:Function)-[:CALLS]->(g) WHERE f.name = 'main' RETURN g.nameMulti — galaxy 3D UI layout** for cross-repo architecture visualizationCross — repo architecture summary** combining services, routes, and dependencies across the indexed fleetRAM — first pipeline**: LZ4 compression, in-memory SQLite, single dump at end. Memory released afterAuto-sync — Background watcher detects file changes and re-indexes automaticallyThis sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Codebase Memory's toolset — Built, Infrastructure-as, codebase-memory-mcp and 11 more — is a fair guide to whether it matches your workflow. It is maintained by DeusData; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Codebase Memory's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Built | in graph visualization** — 3D interactive UI at localhost:9749 (optional UI binary variant). |
| Infrastructure-as | code indexing** — Dockerfiles, Kubernetes manifests, and Kustomize overlays indexed as graph nodes with cross-references. Resource nodes for K8s kinds, Module nodes for Kustomize overlays with IMPORTS edges to referenced |
| codebase-memory-mcp | <os>-<arch>.tar.gz (macOS/Linux) or .zip (Windows) — standard |
| codebase-memory-mcp-ui | <os>-<arch>.tar.gz / .zip — with graph visualization |
| install.sh | ** add --ui (see [Quick Start](#quick-start)) |
| PyPI | ** CBM_VARIANT=ui pip install codebase-memory-mcp |
| Manual | ** download the codebase-memory-mcp-ui-<os>-<arch> archive |
| Cypher | like queries**: MATCH (f:Function)-[:CALLS]->(g) WHERE f.name = 'main' RETURN g.name |
| Multi | galaxy 3D UI layout** for cross-repo architecture visualization |
| Cross | repo architecture summary** combining services, routes, and dependencies across the indexed fleet |
| RAM | first pipeline**: LZ4 compression, in-memory SQLite, single dump at end. Memory released after. |
| Auto-sync | Background watcher detects file changes and re-indexes automatically |
| Format | SQLite database, indexes stripped, VACUUM INTO compacted, then zstd 1.5.7 compressed (8–13:1 ratio typical) |
| Bootstrap | when no local DB exists but the artifact is present, index_repository imports the artifact first, then runs incremental indexing — avoiding the full reindex cost |
{
"mcpServers": {
"codebase-memory": {
"command": "npx",
"args": ["-y", "codebase-memory-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.