In-depth architectural comparison of the Iranti and Kage 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
Iranti
Knowledge & Memory · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Kage
Knowledge & Memory · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Iranti if you need specialized Knowledge & Memory tools running via a local process. Choose Kage 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 Iranti 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).
Persistent shared memory for AI coding agents. Stores facts as entity/key/value triples with hybrid semantic search, task checkpoints, and conflict resolution — shared across Claude Code, Codex CLI, and GitHub Copilot.
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
Category & Scope
Tools & Capabilities Breakdown
Iranti Tools (6)
Persistent shared memory
Entity/key/value fact storage
Hybrid semantic search
Task checkpoints
Conflict resolution
Support for Claude Code, Codex CLI, and GitHub Copilot
Kage Tools (6)
OKF-compatible Markdown memory in Git
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).
Iranti is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Kage belongs to Knowledge & Memory using local stdio subprocess. Select Iranti when you need capabilities focused on knowledge & memory and Kage when you require tools for knowledge & memory.