Cathedral - Persistent Memory for AI Agents MCP Server

The identity layer for AI agents. Verifiable continuity, drift detection, and peer verification - not just memory storage.

People connecting memory tools to Claude, Cursor, VS Code, or another MCP client. The project is written in Python.

VERIFIED ACTIVE

LAST COMMIT 2026-06-13 · ★ 10 · #147 OF 259 MAINTAINED MEMORY · VERIFIED 2026-08-25

MIT · Python servers · how we verify → /methodology

01 · Install Cathedral - Persistent Memory for AI Agents

before you install - you'll need

Set CATHEDRAL_API_KEY, CATHEDRAL_CORS_ORIGINS, CATHEDRAL_TTL_DAYS before connecting.

Claude Code

claude mcp add ailife1-cathedral --transport http https://cathedral-ai.com/mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "ailife1-cathedral": {
      "url": "https://cathedral-ai.com/mcp"
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

https://cathedral-ai.com/mcp

transport: streamable-http

endpoint alive - authentication required · probed 2026-08-25

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions · remote - your agent's requests go to cathedral-ai.com

endpoint auth requires authentication - rejected our unauthenticated MCP initialize

license MIT - declared in the repository

pypi package cathedral-mcp - check the name against the project README before installing (PyPI has no namespace ownership)

registry namespace io.github.AILIFE1 is GitHub-verified and matches the repo owner

03 · Who maintains Cathedral - Persistent Memory for AI Agents

Cathedral - Persistent Memory for AI Agents is maintained by ailife1. It's the only MCP server we track from this author; the repo dates to Jan 2026.

04 · Facts

category
memory - ranked #147 of 259 actively-maintained memory servers as of 2026-08-25.
registry
io.github.AILIFE1/cathedral-mcp (active, first published 2026-04-07 · 2 versions)
packages
pypi:cathedral-mcp

05 · Cathedral - Persistent Memory for AI Agents FAQ

What is Cathedral - Persistent Memory for AI Agents?

The identity layer for AI agents. Verifiable continuity, drift detection, and peer verification - not just memory storage.

Is Cathedral - Persistent Memory for AI Agents still maintained?

Yes - as of 2026-08-25, its last commit was 2026-06-13. We re-verify nightly.

How do I install Cathedral - Persistent Memory for AI Agents?

Run `uvx cathedral-mcp`. The README documents 3 environment variables (CATHEDRAL_API_KEY, CATHEDRAL_CORS_ORIGINS, CATHEDRAL_TTL_DAYS) to set first. Set CATHEDRAL_API_KEY, CATHEDRAL_CORS_ORIGINS, CATHEDRAL_TTL_DAYS before connecting. You can also paste the ready-made client config above.

Does Cathedral - Persistent Memory for AI Agents require authentication?

Yes - when we probed the endpoint on 2026-08-25, it rejected an unauthenticated MCP initialize; you'll need credentials to connect.

06 · Alternatives to Cathedral - Persistent Memory for AI Agents

Pairs well with

Servers that cover what Cathedral - Persistent Memory for AI Agents doesn't - only shown when the pairing reason fits the companion.

  1. Server Filesystem → filesystem companion filesystem · ★ 38,704
  2. X402 List MCP → filesystem companion filesystem · ★ 58