Cairn.ink Memory vs MemAuthority

In-depth architectural comparison of the Cairn.ink Memory and MemAuthority 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?

C

Choose Cairn.ink Memory 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 Cairn.ink Memory Details

Choose MemAuthority 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 MemAuthority Details

Feature & Specification Comparison

Specification	C Cairn.ink Memory Knowledge & Memory	MemAuthority Knowledge & Memory
Summary	Cross-session memory for AI agents with a Source Receipt for every memory, over MCP.	Git-backed long-term memory authority for AI agents via MCP.
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

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": {
    "cairn-ink-memory": {
      "command": "npx",
      "args": [
        "-y",
        "cairn-ink-memory"
      ]
    }
  }
}

{
  "mcpServers": {
    "memauthority": {
      "command": "npx",
      "args": [
        "-y",
        "memauthority"
      ]
    }
  }
}

Related MCP Server Comparisons