What is the key difference between Engram Rs and Lore MCP?

Engram Rs belongs to the Knowledge & Memory category with local stdio execution, while Lore MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Engram Rs or Lore MCP 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 Engram Rs and Lore MCP free or paid?

Engram Rs operates under a BYOK (Pay Provider Direct) model (API Key required). Lore MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Engram Rs lists 16 tools with 2 views and 27 GitHub stars. Lore MCP lists 33 tools with 2 views and 4 GitHub stars.

Can I use both Engram Rs and Lore MCP 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

Engram Rs vs Lore MCP

In-depth architectural comparison of the Engram Rs and Lore MCP 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

Engram Rs

Knowledge & Memory · Local stdio

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

Lore MCP

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Engram Rs if you need specialized Knowledge & Memory tools running via a local process. Choose Lore MCP 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 Engram Rs 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: ENGRAM_EMBEDDING_PROVIDER, ENGRAM_EMBEDDING_API_KEY.
Primary tools included: engram_store, engram_recall, engram_recent.

Explore Engram Rs Details

Choose Lore 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).
Primary tools included: kb_add, kb_search, kb_get.

Explore Lore MCP Details

Feature & Specification Comparison

Specification	Engram Rs kael-bit Knowledge & Memory	Lore MCP davidgut1982 Knowledge & Memory
Summary	Hierarchical memory engine for AI agents with automatic decay, promotion, semantic dedup, and self-organizing topic tree. Single Rust binary, zero external dependencies.	Persistent knowledge layer for AI agents. KB, investigation threads, journal with multi-agent attribution. SQLite/PostgreSQL/Supabase.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Engram Rs Tools (16)

engram_store

Store a memory. All memories start in Buffer and promote to Working/Core through access frequency and LLM quality gating. Procedural memories and lessons (tag=lesson) auto-promote to Working after 2h. Use supersedes to replace outdated memories by their ids.

engram_recall

Hybrid semantic + keyword search with budget-aware retrieval. Fast by default (~30ms cached, ~1s first query). Optional expand adds LLM query expansion (+1-2s) — only use for short/vague queries.

engram_recent

List recent memories by creation time. Good for session context recovery.

engram_resume

Full memory bootstrap for session recovery. Returns core (permanent knowledge), working (ongoing context/decisions), buffer (transient), recent activity, and session notes. Use workspace tags to filter by current work context. Compact mode (default) minimizes token usage.

engram_extract

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

Engram Rs Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kael-bit-engram-rs": {
      "command": "npx",
      "args": [
        "-y",
        "engram-rs-mcp"
      ],
      "env": {
        "ENGRAM_EMBEDDING_PROVIDER": "YOUR_ENGRAM_EMBEDDING_PROVIDER_HERE",
        "ENGRAM_EMBEDDING_API_KEY": "YOUR_ENGRAM_EMBEDDING_API_KEY_HERE"
      }
    }
  }
}

Lore MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "davidgut1982-lore-mcp": {
      "command": "uvx",
      "args": [
        "lore-knowledge-mcp"
      ]
    }
  }
}

Frequently Asked Questions

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

More alternatives to Engram Rs More alternatives to Lore MCP Knowledge & Memory category hub Canonical compare URL