Codebase Memory MCP server
io.github.DeusData · Updated
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
At a glance
Codebase Memory is an MCP server in the AI & Memory category. It runs locally over stdio via `npx -y codebase-memory-mcp`, and declares no required credentials. It exposes 17 tools, including index_repository, list_projects and delete_project. It scores A (99/100) on the MCP Skills Hub health score as of Oct 27, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install Codebase Memory in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install Codebase Memory in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add codebase-memory-mcp -- npx -y codebase-memory-mcpVerify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes (e.g. index_repository, list_projects, delete_project). It discovers them automatically.
How to install Codebase Memory in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "codebase-memory-mcp": { "command": "npx", "args": [ "-y", "codebase-memory-mcp" ] } } }Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install Codebase Memory in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "codebase-memory-mcp": { "command": "npx", "args": [ "-y", "codebase-memory-mcp" ] } } }Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install Codebase Memory in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.codebase-memory-mcp] command = "npx" args = ["-y", "codebase-memory-mcp"]Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install Codebase Memory in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "codebase-memory-mcp": { "command": "npx", "args": [ "-y", "codebase-memory-mcp" ] } } }Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install Codebase Memory in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "codebase-memory-mcp": { "command": "npx", "args": [ "-y", "codebase-memory-mcp" ] } } }
How to install Codebase Memory in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "codebase-memory-mcp": { "type": "stdio", "command": "npx", "args": [ "-y", "codebase-memory-mcp" ] } } }Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What tools does Codebase Memory expose? (17)
Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.
- index_repositoryIndex a repository into the graph. A successful call from an active MCP session registers the target for auto-sync while that session remains connected, subject to the global `auto_watch` setting; CLI calls do not register watches. Waits fo
- list_projectsList indexed projects with paging; use `detail: "stats"` for node/edge counts and database sizes.
- delete_projectRemove a project and all its graph data.
- index_statusCheck indexing status of a project.
- check_index_coverageCheck whether exact paths or a scope are indexed and fresh. A clean result means no recorded gap, not proof of completeness.
- search_graphStructural, BM25, and semantic search. Page structural rows with `offset`/`limit` and ranked semantic rows independently with `semantic_offset`/`semantic_limit`.
- trace_pathTrace callers, callees, data flow, or cross-service paths (alias: `trace_call_path`). Depth 1 to 15; tests are excluded by default. `mode`: `calls` (default), `data_flow`, `cross_service`, `topology` (Kubernetes objects, routes, controllers
- detect_changesMap git diff to affected symbols + blast radius with risk classification.
- query_graphExecute Cypher-like graph queries (read-only).
- get_graph_schemaNode/edge counts, relationship patterns, property definitions per label. Run this first.
- compare_graphsCompare two indexed snapshots: node/edge additions and removals between a base and a target.
- get_code_snippetRead source code for a function by qualified name.
- get_file_outlineDeclaration outline of one repository-relative file in source order, with optional label filter and paging.
- get_architectureCodebase overview: languages, packages, routes, hotspots, clusters, ADR.
- search_codeGrep-like text search within indexed project files.
- manage_adrCRUD for Architecture Decision Records (`get` reads, `update` replaces the whole document, `set_sections` rewrites only the named sections and leaves every other byte untouched, `sections` lists headings). Query modes do not wait behind a s
- ingest_tracesStore observed call paths or caller/callee pairs under a run label. Both endpoints must resolve to indexed symbols; unresolved names are reported.
What the code can do
Read from the published package source — never executed. Parsed 2 of 2 source files.
This server can run other programs on your machine, read and write files and make network requests.
How it was published
- Runs postinstall on install — this executes when you install the package, before you deliberately run anything.
- Has a provenance attestation tying this artifact to the commit it was built from.
- 1 npm maintainer — a single point of compromise · last published by deusdata.
Maintainer of this package and think something here is wrong? Tell us and we'll correct it.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
- Downloads at launch — The package is fetched from its registry each run unless you pin a version.
- Last commit today — Actively maintained.
- 48k GitHub stars — Community adoption signal.
- 7.3k weekly downloads — Regularly installed by other developers.
Client compatibility
Health score
A · 99Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%100%
Last commit 0 days ago.
- Adoption20%95%
47696 stars, 7284 weekly downloads.
- Transparency20%100%
4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.
- Provenance15%100%
Package and registry entry point at the same repository.
- Packaging15%100%
Publishes a pinned version (0.12.1).
Documentation
Full READMEcodebase-memory-mcp: local code intelligence for AI agents via MCP
Understand your repository, from source code to the systems around it. codebase-memory-mcp is an MCP server that connects code, documentation, configuration, and infrastructure in a persistent local knowledge graph. Use it to find an unfamiliar feature, follow a call across services, trace a deployment back to its source, or assess which parts of a project a change could affect.
Give your coding agent structural context through Model Context Protocol (MCP), or query the graph directly from the CLI. The MCP server is the core of the project. Its optional visual companion, CBM Lens, is in open beta (v0.0.1), with a source reader, architecture maps, the Galaxy graph, coverage diagnostics, architecture decisions, and local code chat.
The native C backend exposes 17 MCP tools, parses languages and file formats with vendored grammars, and adds Hybrid LSP type resolution for supported languages. The installer supports 45 automatic or conditional client integrations, including client configuration, skills, agent profiles, and applicable hooks. Indexing and graph queries need no hosted service or API key. Focused graph queries can reduce repeated file reads and token use; see the measured results.
Quick start · Capabilities · Documentation · Infrastructure · Smart CI · Explore CBM Lens · Agent setup · MCP tools
Local processing: Source analysis and graph storage run on your machine. CBM Lens can optionally download a model for browser AI after you enable it; inference stays on the device. The installer writes agent configuration for the clients you select. See Security for release verification and SECURITY.md for reporting issues.
See the graph with CBM Lens (open beta v0.0.1). Folders become nested platforms, files and symbols become selectable blocks, and arrows show indexed relationships. The recording opens src/foundation in the map of this repository, selects arena.c and opens its source. Height can show source size; hotspot gravity reflects static fan-in. Still image.
Galaxy. Explore the code knowledge graph in 3D. The recording follows the outgoing relationships of cbm_arena_alloc one layer further, switches to the hierarchy and shows the two-hop call path to cbm_alloc. Edge pulses show relationship direction; they do not represent live execution. Still: two dependency layers around `cbm_max_file_bytes`.
Explore. Browse files in an IDE-style workspace, read syntax-highlighted source in Monaco, and keep the code graph alongside it. File impact shows what depends on the open file, and Code details shows the callers and calls of the symbol under the caret. Select code to ask the local chat about it.
<details> <summary>More views: system structure and behavior</summary>
System structure groups symbols into components and lets you inspect their dependencies.
Behavior shows possible calls from a selected operation and the source evidence behind them.
</details>
The high-resolution GIFs show CBM Lens Beta on 20 October 2026; the still images were captured on 12–13 October. All show public source from this repository. See capture details for each capture's build, indexed scope and recording setup.
Excerpt — the full document is on GitHub.
Alternatives to Codebase Memory
- hmem — Humanlike Memory for AI AgentsA · 86Persistent 5-level hierarchical memory for AI agents. SQLite-backed, lazy-loaded.
- NeonA · 93Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.
- ai-contextA · 85Local-first MCP server: version-correct library docs, code map, and offline drift for your repo.
- Server4AgentB · 68Servers your AI assistant builds on. It writes the code, runs it and ships each app to a live URL.
Maintain Codebase Memory? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/io-github-deusdata-codebase-memory-mcp)Catalog data refreshed . Something wrong? Report it.