What is the key difference between Mengram and Recallnest?

Mengram 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 Mengram 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 Mengram and Recallnest free or paid?

Mengram operates under a Freemium model (API Key required). Recallnest operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Mengram lists 6 tools with 2 views and 195 GitHub stars. Recallnest lists 6 tools with 2 views and 15 GitHub stars.

Can I use both Mengram 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

Mengram vs Recallnest

In-depth architectural comparison of the Mengram 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

Mengram

Knowledge & Memory · Local stdio

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

Recallnest

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Mengram 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 Mengram when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: MENGRAM_API_KEY.
Primary tools included: Semantic, episodic, and procedural memory types, Procedures evolve from failure feedback, Native multilingual retrieval (23 languages).

Explore Mengram 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: .

Feature & Specification Comparison

Specification	Mengram alibaizhanov Knowledge & Memory	Recallnest AliceLJY Knowledge & Memory
Summary	Human-like memory layer for AI agents with semantic, episodic, and procedural memory. Claude Code hooks (auto-save, auto-recall, cognitive profile). 29 MCP tools, knowledge graph, smart triggers, multi-user isolation. Python & JS SDKs.	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

Mengram Tools (6)

Semantic, episodic, and procedural memory types

Procedures evolve from failure feedback

Native multilingual retrieval (23 languages)

Knowledge graph and smart triggers

Claude Code hooks for auto-save, auto-recall, and session persistence

Multi-user data isolation

Recallnest Tools (6)

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

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

Mengram Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "alibaizhanov-mengram": {
      "command": "uvx",
      "args": [
        "mengram-ai"
      ],
      "env": {
        "MENGRAM_API_KEY": "YOUR_MENGRAM_API_KEY_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

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

More alternatives to Mengram More alternatives to Recallnest Knowledge & Memory category hub