kage-core/Kage
by Various
Persistent, verified memory for coding agents — so they stop re-explaining your codebase and never act on stale knowledge. Every memory is checked against your actual code; lives i
MCP
kage-core/Kage
Added 18 June 2026
Overview
Kage gives coding agents persistent memory that is verified against the actual codebase. Memories are stored as plain files in the repository and shared through git. It requires no account or database and is installed via npx.
Best for
Best for
Teams using coding agents that need shared, version-controlled memory across sessions
Use cases
- Reduce context loss when switching between coding sessions
- Prevent agents from re-explaining known parts of the codebase
- Share agent memory across a team via git
Notes
Kage gives coding agents persistent memory that is verified against the actual codebase. Memories are stored as plain files in the repository and shared through git. It requires no account or database and is installed via npx.
6 stars on GitHub. Last updated 2026-06-18. Licensed GPL-3.0.
Use cases
- Reduce context loss when switching between coding sessions
- Prevent agents from re-explaining known parts of the codebase
- Share agent memory across a team via git
Pros
- No account or database required
- Memories are version-controlled with git by living in plain files
- Verified against actual code to avoid stale knowledge
Cons
- Low adoption with only 6 stars on GitHub
- May have limited edge case handling for complex codebases
- Requires manual MCP installation via npx
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- No account or database required
- Memories are version-controlled with git by living in plain files
- Verified against actual code to avoid stale knowledge
Cons
- Low adoption with only 6 stars on GitHub
- May have limited edge case handling for complex codebases
- Requires manual MCP installation via npx
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.