Cathedral — Persistent Memory for AI Agents

About Cathedral — Persistent Memory for AI Agents

Use Cathedral — Persistent Memory for AI Agents with your agent

claude mcp add --transport http cathedral-persistent-memory-for-ai-agents https://cathedral-ai.com/mcp --header "Authorization: Bearer {CATHEDRAL_API_KEY}"

{
  "mcpServers": {
    "cathedral-persistent-memory-for-ai-agents": {
      "url": "https://cathedral-ai.com/mcp",
      "headers": {
        "Authorization": "Bearer {CATHEDRAL_API_KEY}"
      }
    }
  }
}

Frequently asked questions

What is Cathedral — Persistent Memory for AI Agents?

Cathedral — Persistent Memory for AI Agents is an MCP (Model Context Protocol) server by ailife1 in the Autonomous Agents category. Persistent memory and drift detection for AI agents across session restarts.

How do I connect Cathedral — Persistent Memory for AI Agents to Claude, Cursor, or another MCP client?

Cathedral — Persistent Memory for AI Agents is a remote MCP server — add its endpoint (https://cathedral-ai.com/mcp) to your client's MCP configuration (for example with "claude mcp add", or under "mcpServers" in Cursor's mcp.json) and restart the client.

Is Cathedral — Persistent Memory for AI Agents open source?

Yes — the source code is public at github.com/ailife1/cathedral, with 8 GitHub stars.

Can AI agents pay to use Cathedral — Persistent Memory for AI Agents?

Not yet through Loomal — Cathedral — Persistent Memory for AI Agents is listed as a free directory entry. If its maintainer verifies ownership, they can set per-call USDC pricing that agents pay over x402, with settlement on Base.