codebase-memory-mcp

Query a Codebase Memory MCP graph to map architecture, trace dependencies, and verify code claims.

38.5k|4.9k|Updated Jun 11, 2025
One-click install
npx skills add https://github.com/github/awesome-copilot --skill codebase-memory-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-memory-mcp
Source: https://github.com/github/awesome-copilot/tree/main/skills/codebase-memory-mcp
Command: npx skills add https://github.com/github/awesome-copilot --skill codebase-memory-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exploring an unfamiliar codebase is slow and error-prone when you rely only on manual file reading. This Skill guides an AI agent to use a Codebase Memory MCP server's indexed code graph for fast discovery of symbols, architecture, and dependencies, while enforcing evidence standards so graph results are verified against actual source before making claims.

Core Features & Use Cases

  • Graph-Guided Discovery: Use search_graph, get_architecture, and trace_path to find definitions, implementations, callers, callees, data flow, and dependency paths across a repository.
  • Tiered Evidence Levels: Apply Scout, Verify, or Auditor evidence standards so negative, exhaustive, dead-code, and impact claims are backed by index freshness checks, coverage inspection, and source confirmation.
  • Safe Indexing and Fallbacks: Control indexing modes (fast, moderate, full), require explicit approval before mutations like index_repository or delete_project, and fall back to rooted filesystem exploration when the graph is unavailable.
  • Use Case: When asked whether removing a function is safe, the agent traces all callers through the graph, checks index coverage for every cited path, paginates complete result streams, and confirms with source snippets before concluding the function is dead code.

Quick Start

Ask the agent to map the architecture of this repository and trace all callers of a specific function using the Codebase Memory graph, verifying each finding against the actual source files.

Frequently Asked Questions about codebase-memory-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore an unfamiliar codebase with an MCP server?

Start by calling list_projects to match the canonical checkout root, then use get_architecture for structure and search_graph for symbols. Confirm graph findings with get_code_snippet or local files before editing code.

How do I trace callers and dependencies of a function?

Use the trace_path tool with the function's qualified name to follow callers, callees, data flow, and dependency paths. While results are truncated, pass the returned cursor back until the stream is complete.

Can I trust graph results to claim code is dead or unused?

Not without Auditor-level evidence. Verify the index generation is current, check coverage for every cited path and scope, complete all result pages, and inspect source for skipped or excluded files before making negative claims.

What happens if the Codebase Memory MCP server is unavailable?

The workflow falls back to rooted filesystem exploration anchored at the canonical checkout root. It never invents tool results and bounds claims to content actually inspected.

When should I use fast, moderate, or full indexing modes?

Use moderate by default since it retains similarity and semantic edges. Use fast only for smoke indexes with disclosed limitations, and full only when moderate filters omit relevant files and the extra cost is justified.

Does the skill index repositories automatically?

No. Indexing via index_repository requires explicit user request or approval, or a trusted runtime policy pre-authorizing it. The agent announces the exact mutation and target before any indexing, deletion, or trace ingestion.