Code
How deusdata/codebase-memory-mcp is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Likely start-up file
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd a new MCP tool
- Define the tool's job struct and registration in the architecture_jobs.c dispatcher
- Implement tool-specific logic using graph queries via the store interface
- Register the tool in agent_profiles.c to expose capability to connected agents
Add support for a new language
- Create language-specific AST profile in src/semantic/ directory following ast_profile.h conventions
- Register the language parser and symbol extraction rules in semantic.c dispatcher
- Update discover.c to recognize files of the new language type
Extend the graph projection
- Define new node/edge types and query patterns in architecture_projection.h
- Expose projection via new MCP tool following the pattern in architecture_jobs.c
Change the public API
Trace runtime behavior
Add or update tests
Change build or automation
RepoPilot lists up to 500 files, so a file missing here may still exist.
- Files marked “likely” are guessed from their names.