Memory Fabric vs Memorix

In-depth architectural comparison of the Memory Fabric and Memorix 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 Memory Fabric 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).

Explore Memory Fabric Details

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

Explore Memorix Details

Feature & Specification Comparison

Specification	Memory Fabric Knowledge & Memory	Memorix Knowledge & Memory
Summary	File-first, local-first MCP memory for AI coding assistants: Markdown + YAML, no vector DB.	Local-first persistent project memory for AI coding agents across MCP clients and sessions.
Category & Scope	Knowledge & Memory	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": {
    "memory-fabric": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

{
  "mcpServers": {
    "memorix": {
      "url": "http://localhost:3211/mcp"
    }
  }
}

Related MCP Server Comparisons