Cathedral — Persistent Memory For AI Agents MCP Server

Persistent memory and drift detection for AI agents across session restarts.

Remote serverstreamable-httpPython

What is the Cathedral — Persistent Memory For AI Agents MCP server?

Connect Cathedral — Persistent Memory For AI Agents to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Persistent memory and drift detection for AI agents across session restarts. The cathedral — persistent memory for ai agents mcp server is what makes that connection.

What the server does

c = Cathedral(api_key="cathedral_...") context = c.wake() # full identity reconstruction c.remember("something important", category="experience", importance=0.8) ```

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Method — Endpoint
  • POST — /register
  • GET — /wake

Credentials and setup notes

Configuration is passed through the environment: CATHEDRAL_API_KEY, CATHEDRAL_CORS_ORIGINS, CATHEDRAL_TTL_DAYS. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cathedral — Persistent Memory For AI Agents's toolset — Method, POST, GET — is a fair guide to whether it matches your workflow. It is maintained by AILIFE1; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
MethodEndpoint
POST/register
GET/wake

How to install the Cathedral — Persistent Memory For AI Agents MCP server

Add to `~/.claude/settings.json`:

```json
{
  "mcpServers": {
    "cathedral": {
      "command": "uvx",
      "args": ["cathedral-mcp"],
      "env": { "CATHEDRAL_API_KEY": "your_key" }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
CATHEDRAL_API_KEYCredential the server authenticates with.Yes
CATHEDRAL_CORS_ORIGINSConfiguration value read at startup.Optional
CATHEDRAL_TTL_DAYSConfiguration value read at startup.Optional

Example prompts to try

  • Use Cathedral — Persistent Memory For AI Agents to Method.
  • Use Cathedral — Persistent Memory For AI Agents to POST.
  • Use Cathedral — Persistent Memory For AI Agents to GET.

Frequently asked questions

It connects Cathedral — Persistent Memory For AI Agents to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (Method, POST, GET) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Cathedral — Persistent Memory For AI Agents directly.