What is the key difference between Mnemostack and Memora?

Mnemostack belongs to the Knowledge & Memory category with local stdio execution, while Memora belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mnemostack or Memora 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 Mnemostack and Memora free or paid?

Mnemostack operates under a BYOK (Pay Provider Direct) model (API Key required). Memora operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Mnemostack lists 6 tools with 4 views and 7 GitHub stars. Memora lists 6 tools with 2 views and 719 GitHub stars.

Can I use both Mnemostack and Memora 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

Mnemostack vs Memora

In-depth architectural comparison of the Mnemostack and Memora 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

Mnemostack

Knowledge & Memory · Local stdio

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

Memora

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Mnemostack if you need specialized Knowledge & Memory tools running via a local process. Choose Memora 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 Mnemostack when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: GEMINI_API_KEY.
Primary tools included: Hybrid vector, BM25, temporal, and graph retrieval, Reciprocal rank fusion with multi-stage reranking, Qdrant-backed persistent storage.

Explore Mnemostack Details

Choose Memora when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: MEMORA_DB_PATH, MEMORA_STORAGE_URI, CLOUDFLARE_API_TOKEN, AWS_PROFILE, AWS_ENDPOINT_URL, MEMORA_CLOUD_ENCRYPT, MEMORA_ALLOW_ANY_TAG, MEMORA_GRAPH_PORT.

Feature & Specification Comparison

Specification	Mnemostack udjin-labs Knowledge & Memory	Memora agentic-mcp-tools Knowledge & Memory
Summary	Durable hybrid memory for AI agents. Combines vector search, BM25, temporal retrieval, and optional Memgraph knowledge graph via reciprocal rank fusion. 6 MCP tools: health, search, answer, feedback, graphquery, graphaddtriple. Self-hosted with Qdrant backend. 82.5% strict accuracy on LoCoMo benchmark. pip install 'mnemostack[mcp]'	Persistent memory with knowledge graph visualization, semantic/hybrid search, cloud sync (S3/R2), and cross-session context management.
Category & Scope

Tools & Capabilities Breakdown

Mnemostack Tools (6)

Hybrid vector, BM25, temporal, and graph retrieval

Reciprocal rank fusion with multi-stage reranking

Qdrant-backed persistent storage

Optional Memgraph knowledge graph

MCP tools for search, answers, feedback, and graph operations

Payload filters for scoped retrieval

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

Mnemostack Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "udjin-labs-mnemostack": {
      "command": "uvx",
      "args": [
        "mnemostack"
      ],
      "env": {
        "GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE"
      }
    }
  }
}

Memora Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "agentic-mcp-tools-memora": {
      "command": "npx",
      "args": [
        "-y",
        "wrangler"
      ],
      "env": {
        "MEMORA_DB_PATH": "YOUR_MEMORA_DB_PATH_HERE",
        "MEMORA_STORAGE_URI": "YOUR_MEMORA_STORAGE_URI_HERE",
        "CLOUDFLARE_API_TOKEN": "YOUR_CLOUDFLARE_API_TOKEN_HERE",
        "AWS_PROFILE": "YOUR_AWS_PROFILE_HERE",
        "AWS_ENDPOINT_URL": "YOUR_AWS_ENDPOINT_URL_HERE",
        "MEMORA_CLOUD_ENCRYPT": "YOUR_MEMORA_CLOUD_ENCRYPT_HERE",
        "MEMORA_ALLOW_ANY_TAG": "YOUR_MEMORA_ALLOW_ANY_TAG_HERE",
        "MEMORA_GRAPH_PORT": "YOUR_MEMORA_GRAPH_PORT_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Mnemostack More alternatives to Memora Knowledge & Memory category hub Canonical compare URL