What is the key difference between Lore and Engram MCP?

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

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

Lore operates under a Free / Open Source model (No auth required). Engram MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Lore lists 46 tools with 0 views and 8 GitHub stars. Engram MCP lists 11 tools with 2 views and 1 GitHub stars.

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

Lore vs Engram MCP

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

Lore

Knowledge & Memory · Local stdio

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

Engram MCP

Knowledge & Memory · Local stdio

Quality: 39/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Lore if you need specialized Knowledge & Memory tools running via a local process. Choose Engram 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 Lore 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: remember, recall, forget.

Explore Lore Details

Choose Engram 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: ENGRAM_DB, ENGRAM_EMBEDDING_URL.
Primary tools included: remember, recall, search.

Explore Engram MCP Details

Feature & Specification Comparison

Specification	Lore Knowledge & Memory	Engram MCP Cartisien Knowledge & Memory
Summary	Cross-agent memory over MCP: hybrid recall, knowledge graph, private/shared visibility, redaction.	Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings (nomic-embed-text) with keyword fallback. remember, recall, history, forget, and stats tools. Works with Claude Desktop, Cursor, and any MCP client.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Lore Tools (46)

remember

Store a memory with type, tier, tags, metadata

recall

Semantic search with temporal/graph-enhanced retrieval

forget

Delete a memory by ID

list_memories

List memories with filtering

stats

Memory statistics (total, by type/tier)

upvote_memory

Boost memory ranking

downvote_memory

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

Lore Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lore": {
      "command": "uvx",
      "args": [
        "lore-sdk"
      ]
    }
  }
}

Engram MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "cartisien-engram-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@cartisien/engram-mcp"
      ],
      "env": {
        "ENGRAM_DB": "YOUR_ENGRAM_DB_HERE",
        "ENGRAM_EMBEDDING_URL": "YOUR_ENGRAM_EMBEDDING_URL_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

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