Verified memory for coding agents: claims cited against code, stale withheld, savings receipts.
Most knowledge and memory work still happens through a UI a human drives. Kage MCP server moves it into the conversation instead. Verified memory for coding agents: claims cited against code, stale withheld, savings receipts.
In June 2026 Google shipped OKF (Open Knowledge Format): a standard for keeping knowledge as plain Markdown concept files in your repo, vendor-neutral, no lock-in. It standardizes the store and stops there. Verification, freshness, and staleness are explicitly out of scope for v0.1. Kage is the framework that maintains it. It captures what your coding agents learn as a conformant OKF bundle in git, then keeps every concept honest against your real code: a memory whose cited code no longer exists is rejected at write time, and one
Kage is a memory layer for coding agents. As your agent works, it captures what it learns (decisions, bug fixes, conventions, how the code fits together) as Open Knowledge Format (OKF) concept files committed in your repo under .agent_memory/. The next session (yours or a teammate's) starts already knowing it, instead of re-reading or re-asking.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: ANTHROPIC_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by com.kage-core; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Kage's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"kage": {
"command": "npx",
"args": ["-y", "@kage-core/kage-graph-mcp"],
"env": {
"ANTHROPIC_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ANTHROPIC_BASE_URL | Endpoint or connection string the server talks to. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.