Kage

MCP.Pizza Chef: kage-core

Kage captures and verifies knowledge about your codebase as your AI coding assistants work, storing it as readable files in your repository. This keeps your AI agents up-to-date with the latest code changes, prevents stale or incorrect suggestions, and shares insights across your team through git. It works with popular AI coding tools like Claude Desktop and Cursor, requires no accounts or API keys, and installs easily with a single command inside your repo.

Coding
Other

Use This MCP server To

Keep my coding assistant’s memory accurate and up-to-date Share coding decisions and fixes with my whole team Avoid re-explaining my codebase to AI agents Trust that AI suggestions reflect the current code Work with multiple AI coding tools seamlessly Store coding knowledge directly in my git repo

README

Kage

Verified memory for coding agents — a Google OKF bundle, kept true to your code

kage viewer: a team's captured decisions, runbooks, and bug fixes mapped to the code they're grounded in, with trust and savings — a live walkthrough

kage viewer: your team's decisions, runbooks, and bug fixes (purple), kept in the repo and linked to the code they are about (blue).

The decisions behind your codebase, the runbook for a tricky deploy, the root cause of a gnarly bug: this knowledge lives in people's heads and scrolls past in chat, then gets lost. Kage captures it as your coding agents work, keeps it as a Google Open Knowledge Format (OKF) bundle in your repo — plain Markdown concept files any OKF consumer can read — and shares it with your whole team through git. The next session, yours or a teammate's, starts already knowing it. Every memory is also checked against the actual code, so what gets shared stays true. OKF standardizes the store; Kage is the verification layer Google left out. No account, no database, no API key.

npx -y @kage-core/kage-graph-mcp install

npm version downloads license zero dependencies no account Built on Google Open Knowledge Format

Kage in numbers: 96% R@5 recall, 0% stale served, 18% faster than grep, 0 dependencies, 340+ tests passing, 15 agents supported

Website · Docs · Live viewer · npm · Book a demo

Works with Claude Code · Codex · Cursor · Windsurf · Gemini CLI · Cline · Goose · Roo Code · Kilo Code · OpenCode · Aider · Claude Desktop · Copilot · OpenClaw · Hermes · any MCP client

🌐 English · 简体中文 · 日本語 · 한국어 · Español · Português (Brasil) · Français · Deutsch · हिन्दी

Kage FAQ

Can I use Kage to keep my coding assistant up-to-date with my codebase?
Yes — Kage ensures your coding assistant remembers and verifies knowledge against your actual code, preventing stale or outdated info.
Can I use Kage with Claude Desktop or Cursor?
Yes — Kage works with Claude Desktop, Cursor, Cline, Goose, Windsurf, Roo Code, and many other MCP clients.
Do I need an account or API key to use Kage?
No — Kage works entirely without accounts or API keys, storing memory as files in your repo.
How hard is it to set up Kage?
Setup is simple — just run one command inside your code repo and restart your coding assistant.
Does Kage require special software or dependencies?
You only need Node.js 18+ and to run the install command; no other dependencies are required.