In-depth architectural comparison of the A2cr and Iranti 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
A2cr
Knowledge & Memory · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Iranti
Knowledge & Memory · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose A2cr if you need specialized Knowledge & Memory tools running via a local process. Choose Iranti 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 A2cr 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).
You have access to required keys: A2CR_LOCAL_DB, A2CR_UI_URL.
Primary tools included: Stores WorkBaton, WorkStash, WorkThread, actor, and event records locally, Client-encrypted checkpoint and note storage, SQLite database backend with no cloud or account needed.
MCP server for AI-agent handoffs. Saves client-encrypted WorkBaton checkpoints and WorkStash notes so Codex, Claude Code, Roo Code, and other MCP clients can resume work without passing full chat history.
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.
A2cr is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Iranti belongs to Knowledge & Memory using local stdio subprocess. Select A2cr when you need capabilities focused on knowledge & memory and Iranti when you require tools for knowledge & memory.