In-depth architectural comparison of the Recallnest and Mcp Memory Gateway 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
Recallnest
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Mcp Memory Gateway
Knowledge & Memory · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose Recallnest if you need specialized Knowledge & Memory tools running via a local process. Choose Mcp Memory Gateway 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 Recallnest when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: JINA_API_KEY.
Primary tools included: Hybrid retrieval: vector, BM25, multi-vector levels, and knowledge graph PPR, Session checkpoint and resume with repo-state guarding, Multi-scope isolation with related scope sidecar search.
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Primary tools included: PreToolUse and pre-action tool-call checks, Hard blocks for secret leaks and self-disable attempts, Warnings and logs for selected high-risk commands.
Persistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph with PPR traversal, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB + SQLite, zero external dependencies.
Pre-action gates that prevent AI coding agents from repeating known mistakes. Captures explicit feedback, auto-promotes failures into prevention rules, and enforces them via hooks.
Category & Scope
Tools & Capabilities Breakdown
Recallnest Tools (6)
Hybrid retrieval: vector, BM25, multi-vector levels, and knowledge graph PPR
Session checkpoint and resume with repo-state guarding
Multi-scope isolation with related scope sidecar search
Memory lifecycle management: decay, consolidation, promotion, and archival
Privacy tiers with cascade forgetting and write-time admission control
Dual interface: MCP stdio for CLI and HTTP API for custom clients
Mcp Memory Gateway Tools (6)
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).
Recallnest is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Mcp Memory Gateway belongs to Knowledge & Memory using local stdio subprocess. Select Recallnest when you need capabilities focused on knowledge & memory and Mcp Memory Gateway when you require tools for knowledge & memory.