Recallnest vs Projectmem

In-depth architectural comparison of the Recallnest and Projectmem 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.

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.

Explore Recallnest Details

Choose Projectmem 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: Local-first memory stored in .projectmem directory, Typed event storage: issues, attempts, fixes, decisions, notes, Pre-commit git hook warnings for repeated mistakes.

Feature & Specification Comparison

Specification	Recallnest AliceLJY Knowledge & Memory	Projectmem riponcm Knowledge & Memory
Summary	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.	Local-first memory and judgment layer for AI coding agents. Captures issues, failed attempts, fixes, and decisions in readable Markdown + JSONL, re-injects them into future sessions, and warns at git commit before you repeat a mistake. 14 tools, works with Claude, Cursor, Antigravity, and Codex.
Category & Scope

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "aliceljy-recallnest": {
      "command": "npx",
      "args": [
        "-y",
        "recallnest"
      ],
      "env": {
        "JINA_API_KEY": "YOUR_JINA_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "riponcm-projectmem": {
      "command": "npx",
      "args": [
        "-y",
        "riponcm-projectmem"
      ]
    }
  }
}

Related MCP Server Comparisons