What is the key difference between Lore and Memory Vault?

Lore belongs to the Knowledge & Memory category with local stdio execution, while Memory Vault belongs to the Knowledge & Memory category with cloud HTTP/SSE execution.

How do I install Lore or Memory Vault 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 Memory Vault free or paid?

Lore operates under a Free / Open Source model (No auth required). Memory Vault 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. Memory Vault lists 6 tools with 1 views and 63 GitHub stars.

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

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

Memory Vault

Knowledge & Memory · Remote HTTP/SSE

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

Verdict Summary: Choose Lore if you need specialized Knowledge & Memory tools running via a local process. Choose Memory Vault if your workspace requires Knowledge & Memory integration with remote web transport. 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 Memory Vault when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: recall, remember, forget.

Explore Memory Vault Details

Feature & Specification Comparison

Specification	Lore Knowledge & Memory	Memory Vault Knowledge & Memory
Summary	Cross-agent memory over MCP: hybrid recall, knowledge graph, private/shared visibility, redaction.	Local-first AI memory layer with hybrid search. Postgres + pgvector. Self-hosted, MIT.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

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"
      ]
    }
  }
}

Memory Vault Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "memory-vault": {
      "url": "http://192.168.1.50:8000/api/mcp/sse"
    }
  }
}

Frequently Asked Questions

Lore is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memory Vault belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select Lore when you need capabilities focused on knowledge & memory and Memory Vault when you require tools for knowledge & memory.