Memxus Remote MCP vs Lore

In-depth architectural comparison of the Memxus Remote MCP and Lore 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.

Which MCP Server Should You Choose?

Choose Memxus Remote MCP 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: remember, recall, get_context.

Explore Memxus Remote MCP Details

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

Feature & Specification Comparison

Specification	Memxus Remote MCP gpitrella Knowledge & Memory	Lore Knowledge & Memory
Summary	Shared context engine for devs and teams. Syncs GitHub, Notion, and saved decisions into reusable project context, so Claude, ChatGPT, Cursor, VS Code and Gemini start each session with the architecture and decisions the team already made. OAuth 2.1 PKCE, AES-256 encrypted, RFC 9728 compliant. https://mcp.memxus.com/mcp	Cross-agent memory over MCP: hybrid recall, knowledge graph, private/shared visibility, redaction.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

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

{
  "mcpServers": {
    "gpitrella-memxus-remote-mcp": {
      "url": "https://mcp.memxus.com/mcp"
    }
  }
}

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

Related MCP Server Comparisons