High-performance MCP server that indexes codebases into a persistent knowledge graph for structural search, call tracing, architecture summaries, dead-code detection, and cross-repo analysis.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first. Includes a review or approval gate.
Safety & privacy surface
5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access, third-party handling.
{
"mcpServers": {
"codebase-memory": {
"command": "npx",
"args": ["-y", "codebase-memory-mcp"]
}
}
}Codebase Memory MCP indexes repositories into a persistent code knowledge graph that Claude can query through MCP. It supports structural search, call tracing, architecture summaries, impact analysis, dead-code detection, cross-service links, ADR management, and cross-repo graph intelligence.
The upstream README documents release binaries, package manager availability,
agent auto-configuration, optional graph visualization, auto-indexing, and the
codebase-memory-mcp command. The repository also ships a server.json
manifest for MCP registry metadata and release package hashes.
These sources were reviewed on 2026-06-05. Prefer the live repository, README, server manifest, security policy, latest release metadata, and package registry metadata for current binaries, checksums, install options, supported platforms, MCP tools, and verification guidance.
Install the NPM package globally:
npm install -g codebase-memory-mcp
For MCP clients that launch stdio servers without a global install:
{
"mcpServers": {
"codebase-memory": {
"command": "npx",
"args": ["-y", "codebase-memory-mcp"]
}
}
}
Restart the MCP client after installing the package and adding or refreshing the server configuration. For manual binary installs, download a platform archive from the latest release and verify checksums before running it.
Codebase Memory MCP is intentionally deep in the local development environment. It reads source files, stores derived graph data, and can write agent configuration, skills, hooks, and instruction files during installation. Audit the source and verify release artifacts before running it in sensitive workspaces.
Limit indexing to approved repositories and review ignored paths before turning on auto-indexing or watchers. Treat persistent graph databases and shared graph artifacts as derived copies of source intelligence that may reveal proprietary architecture, route names, service boundaries, comments, and accidentally committed secrets.
No DeusData/codebase-memory-mcp entry, codebase-memory-mcp command entry, or
matching source URL was found in content/mcp.
Show that Codebase Memory MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/codebase-memory-mcp-server)Codebase Memory MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | High-performance MCP server that indexes codebases into a persistent knowledge graph for structural search, call tracing, architecture summaries, dead-code detection, and cross-repo analysis. Open dossier | MCP server for semantic codebase intelligence, combining AST structure, embeddings, clustering, feature hubs, restore points, and memory graph tools. Open dossier | Stdio MCP server that lets Claude ask the Google Gemini CLI for large-file, codebase, brainstorming, and sandboxed analysis while preserving MCP tool and prompt workflows inside Claude Code or compatible MCP clients. Open dossier | Local-first context-engineering MCP server and CLI that gives Claude token-efficient file reads, shell-output compression, code search, graph queries, persistent session memory, context packaging, verification tools, and dashboard-style token accounting through a single Rust binary. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| Submitter | oktofeesh1 | oktofeesh1 | oktofeesh1 | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | ||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | DeusData | forloopcodes | jamubc | Yves Gude |
| Added | 2026-06-05 | 2026-06-05 | 2026-06-06 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Codebase Memory MCP reads source files across indexed repositories and writes MCP entries, instruction files, skills, hooks, and agent configuration files during install. The background watcher and auto-index features can keep graph data updated as source files change. The optional graph UI exposes a local visualization server on a localhost port. Shared graph artifacts and SQLite databases can persist source metadata after an MCP session ends. Verify downloaded release binaries, checksums, signatures, and provenance before running them in sensitive environments. | ✓Context+ can inspect source files, build AST and embedding indexes, run static analysis, create memory graph nodes, and propose code changes. The `propose_commit` tool is designed to write code after validation and creates shadow restore points before saving. Static analysis tools may invoke local compilers, linters, or language tools depending on the repository. Runtime caches and memory graph data can persist source-derived embeddings and relationships after the MCP session ends. External embedding providers can receive source-derived text, identifiers, prompts, and cluster-labeling context. | ✓Gemini MCP Tool runs locally but invokes the Gemini CLI, so prompts, file references, and command output can leave the local machine through the configured Google Gemini account or API path. The `ask-gemini` tool can pass `@` file or directory references to Gemini CLI; current source checks that references stay under the working directory, but users should still scope prompts carefully. Sandbox mode is exposed as an option on `ask-gemini` and forwards the Gemini CLI sandbox flag; review generated scripts, network calls, package installs, and filesystem changes before relying on sandboxed output. Change mode can generate structured edit suggestions for Claude to apply; inspect proposed OLD/NEW replacements before applying them to source files. Treat the project as an unofficial third-party bridge, not an official Google MCP server. | ✓LeanCTX can read local files, run shell commands invoked through its tools, cache outputs, install shell/editor hooks, and persist session state. Review generated MCP and shell-hook changes before enabling them across all agents or shells. Keep path jail enforcement enabled for normal use, and allow extra roots only when a project genuinely needs them. Disable or restrict command-execution and unsafe I/O tools for regulated repositories, untrusted workspaces, or shared team environments. Treat compressed shell output and cached reads as summaries; switch to full reads or raw command output when exact source text matters. |
| Privacy notes | ✓Source code, filenames, paths, symbols, comments, imports, routes, call graphs, architecture summaries, ADRs, graph queries, prompts, and tool outputs may be visible to the MCP client and model provider. Persistent graph databases and shared artifacts can retain proprietary architecture, internal package names, route names, service boundaries, and accidentally committed secrets. Auto-indexing broad workspace roots can include unrelated private repositories or generated files. Avoid committing shared graph artifacts unless the repository owners explicitly approve storing derived code intelligence in version control. | ✓Source code, file paths, symbol names, comments, identifiers, embeddings, memory nodes, relations, prompts, API keys, static-analysis output, proposed diffs, and tool results may be visible to the MCP client and model provider. Proprietary codebases can expose internal architecture, feature maps, naming conventions, secrets accidentally present in code, and product plans. Keep API keys and provider base URLs out of committed MCP configs, logs, screenshots, and shared prompts. Review `.mcp_data` and generated restore-point data before sharing workspaces or artifacts. | ✓Prompts, selected source files, directory context, code snippets, local paths, command output, change-mode chunks, and brainstorming context may be sent to Gemini CLI and the configured Gemini service. Avoid referencing `.env` files, credentials, private keys, customer data, unreleased product plans, or regulated datasets in `@` references. The MCP server and Gemini CLI may log execution details locally; protect terminal history, MCP client logs, and Gemini CLI configuration files. Google account, project, retention, and telemetry behavior depends on the user's Gemini CLI configuration and Google service terms. | ✓Local code, file paths, command output, search terms, session notes, context packages, knowledge graph data, token metrics, and dashboard statistics can be sent to the MCP client and model. LeanCTX stores local stats and session state under its own configuration/data directories; protect these files if they contain project decisions, findings, or sensitive paths. Secret-like paths are blocked or role-gated by default according to upstream security docs, but users should still avoid prompting agents to read credentials, private keys, tokens, or ignored files. The upstream security policy describes optional update checks and opt-in anonymous stats sharing; disable network checks when working in confidential or offline environments. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Give Claude semantic and structural code context with AST trees, skeletons, semantic search, blast radius, static analysis, memory graph, and restore points.
Ask the Gemini CLI for large-context analysis from Claude.
Source-backed guides for putting this to work.
Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.