What is the key difference between Mnemo MCP and Recallnest?

Mnemo MCP belongs to the Knowledge & Memory category with local stdio execution, while Recallnest belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mnemo MCP or Recallnest in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Mnemo MCP and Recallnest free or paid?

Mnemo MCP operates under a Free / Open Source model (No auth required). Recallnest operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Mnemo MCP lists 3 tools with 2 views and 11 GitHub stars. Recallnest lists 6 tools with 2 views and 15 GitHub stars.

Can I use both Mnemo MCP and Recallnest together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Mnemo MCP vs Recallnest

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

Mnemo MCP

Knowledge & Memory · Local stdio

Quality: 57/100 (Good) | Auth: No auth required

Recallnest

Knowledge & Memory · Local stdio

Quality: 59/100 (Good) | Auth: API Key required

Verdict Summary: Choose Mnemo MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Recallnest 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 Mnemo MCP 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: MNEMO_MCP_RCLONE_REMOTE, MNEMO_MCP_SYNC_PASSPORT_KEY, MNEMO_MCP_DB_PATH, MNEMO_MCP_LOG_LEVEL.
Primary tools included: config, help, config__open_relay.

Explore Mnemo MCP Details

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.

Feature & Specification Comparison

Specification	Mnemo MCP n24q02m Knowledge & Memory	Recallnest AliceLJY Knowledge & Memory
Summary	Persistent AI memory with SQLite hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, rclone sync across machines. Zero config, no cloud, no limits.	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.
Category & Scope

Tools & Capabilities Breakdown

Mnemo MCP Tools (3)

config

Server status, trigger sync, update settings, pre-download embedding model, authenticate sync provider, manage HTTP setup form lifecycle, passport export/import

help

Full documentation for any tool

config__open_relay

Open the zero-config relay setup form (registered via mcp-core)

Recallnest Tools (6)

Hybrid retrieval: vector, BM25, multi-vector levels, and knowledge graph PPR

Session checkpoint and resume with repo-state guarding

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

Mnemo MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "n24q02m-mnemo-mcp": {
      "command": "uvx",
      "args": [
        "invocation"
      ],
      "env": {
        "MNEMO_MCP_RCLONE_REMOTE": "YOUR_MNEMO_MCP_RCLONE_REMOTE_HERE",
        "MNEMO_MCP_SYNC_PASSPORT_KEY": "YOUR_MNEMO_MCP_SYNC_PASSPORT_KEY_HERE",
        "MNEMO_MCP_DB_PATH": "YOUR_MNEMO_MCP_DB_PATH_HERE",
        "MNEMO_MCP_LOG_LEVEL": "YOUR_MNEMO_MCP_LOG_LEVEL_HERE"
      }
    }
  }
}

Recallnest Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Mnemo MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Recallnest belongs to Knowledge & Memory using local stdio subprocess. Select Mnemo MCP when you need capabilities focused on knowledge & memory and Recallnest when you require tools for knowledge & memory.

More alternatives to Mnemo MCP More alternatives to Recallnest Knowledge & Memory category hub Canonical compare URL