codebase-memory-mcp

Topics in the source

• Codebase Memory MCP
• Evidence Levels
• Workflow
• Rooted Filesystem Fallback
• Indexing Modes
• Safety and Fallbacks

Use the configured Codebase Memory graph as a discovery accelerator, not as the sole source of truth. Confirm graph-derived conclusions with source snippets or local files before editing code or making strong claims. Scout — Provisional positive orientation only. Do not make absence, exhaustive, dead-code, or complete-impact claims. Verify — Default for task-directed work. Check freshness where material, exact source snippets, relevant traces, path coverage, and every result page needed by the claim. Auditor — Use for negative, exhaustive, security, dead-code, architecture-boundary, and complete-impact work. Require the current index generation, a bounded scope, complete result streams, coverage inspection, and source checks for gaps. Match the evidence level to the claim. If Auditor evidence cannot be completed, state the bounded limitation instead of making an absolute claim. 1. Discover the Codebase Memory tools exposed by the current MCP client; clients may prefix or rename tool namespaces. 2. Call listprojects first. Select only the entry whose canonical rootpath matches the live checkout, and retain both its exact project name and root for later calls. If no entry matches, co

This is an excerpt. Refer to the complete source and its current requirements.