Kage vs Agent Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Kage vs Agent Memory
In-depth architectural comparison of the Kage and Agent Memory MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Kage
Knowledge & Memory · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Agent Memory
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose Kage if you need specialized Knowledge & Memory tools running via a local process. Choose Agent Memory if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Kage when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: OKF-compatible Markdown memory in Git, Citation validation at write and recall time, Local BM25 and vector retrieval.
Verified, git-native memory for coding agents. Memory is plain JSON packets committed in your repo, each checked against the code it cites — hallucinated citations rejected at write, stale or changed memory withheld at recall, plus diff-time stale-catch. Local-only (BM25 + vectors), no account, no API key. npx -y @kage-core/kage-graph-mcp install
Git-native project memory for coding agents: Markdown source of truth committed to your repo, reviewable staged updates (review --diff → apply), secret/PII-safe, branch-aware — no cloud, no vector DB.
Category & Scope
Tools & Capabilities Breakdown
Kage Tools (6)
OKF-compatible Markdown memory in Git
Citation validation at write and recall time
Local BM25 and vector retrieval
Isolated worktree orchestration
Independent test, diff, and citation checks
Agent setup and local project UI
Agent Memory Tools (3)
memory.fetch_context
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Kage is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Agent Memory belongs to Knowledge & Memory using local stdio subprocess. Select Kage when you need capabilities focused on knowledge & memory and Agent Memory when you require tools for knowledge & memory.