Neotoma vs Iranti — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Neotoma vs Iranti
In-depth architectural comparison of the Neotoma 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
Neotoma
Knowledge & Memory · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Iranti
Knowledge & Memory · Local stdio
Quality: 40/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Neotoma if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. 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 Neotoma when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Immutable, append-only observation storage with content-addressed sources, Deterministic entity resolution and snapshot computation, Schema-first extraction with incremental schema evolution.
Deterministic state layer for AI agents. Stores versioned entities (contacts, tasks, transactions, decisions) with immutable observations, full provenance, and schema-first extraction. Local-first SQLite, cross-client memory across Claude, Cursor, ChatGPT, and OpenClaw. Website
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.
Category & Scope
Tools & Capabilities Breakdown
Neotoma Tools (6)
Immutable, append-only observation storage with content-addressed sources
Deterministic entity resolution and snapshot computation
Schema-first extraction with incremental schema evolution
Typed relationships and timeline event queries
Multi-agent access control with hardware-attested authentication
Peer instance federation and configurable conflict resolution
Iranti Tools (5)
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).
Neotoma is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Iranti belongs to Knowledge & Memory using local stdio subprocess. Select Neotoma when you need capabilities focused on knowledge & memory and Iranti when you require tools for knowledge & memory.