Locus vs MemAuthority

In-depth architectural comparison of the Locus 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?

Choose Locus 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 Locus 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	Locus Knowledge & Memory	MemAuthority Knowledge & Memory
Summary	Hierarchical markdown memory palace for AI agents — structured palace navigation via MCP tools.	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": {
    "locus-2": {
      "command": "uvx",
      "args": [
        "locus-mcp"
      ]
    }
  }
}

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

Related MCP Server Comparisons