Cathedral — Persistent Memory for AI Agents MCP Server

by ailife1 Your server? Claim it

answering

Cathedral — Persistent Memory for AI Agents is answering right now. Last checked 14 min ago. 94 installs a week from pypi. Last commit 13 Jun 2026.

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

Installs per day peak 25 · avg 13 · -10% w/w

a month agotoday

Uptime history 91 days of history · worst day 93%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

202 ms

Response time

average over 24h

Installs / week

npm and PyPI

What the code does

We read the source, 5 d ago · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command cathedral_council_v2.py:345

        result = subprocess.run(

Secret passed into the image build mcp-server/Dockerfile:4

# Glama verification key - server starts and responds to MCP introspection
# Replace with your real key from cathedral-ai.com
ENV CATHEDRAL_API_KEY=glama-check

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://cathedral-ai.com/mcp

~/.codex/config.toml

[mcp_servers.cathedral-mcp]
url = "https://cathedral-ai.com/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

{
  "servers": {
    "cathedral-mcp": {
      "type": "http",
      "url": "https://cathedral-ai.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://cathedral-ai.com/mcp	streamable-http	needs auth	176 ms	14 min ago

Alternatives to Cathedral — Persistent Memory for AI Agents

same job, measured the same way

Goldhold

by jerrysrodz

Persistent memory for AI agents. Search, store, and recall across sessions.

93 installs/wk answering

Memory

by velixarai

Persistent memory for AI assistants. Store, search, and recall across sessions.

91 installs/wk local only

Central Intelligence

by alekseimarchenko

Persistent memory for AI agents. Store, recall, and share knowledge across sessions.

40 installs/wk local only

Memoir

by bighippoman

Structured session journals for AI agents. Persistent memory across sessions.

37 installs/wk local only

Memorykit

by rapozoantonio

Cognitive memory for AI coding assistants — persistent memory across sessions

50 installs/wk local only

Mindtrail

by rohitdeshmukh-1

Persistent, local-first memory for AI coding agents. Remember, recall and forget across sessions.

62 installs/wk local only

MCP Memory

by infoinlet-marketplace

Persistent searchable memory for AI agents — save/get/search across sessions, tags.

52 installs/wk local only

Total Recall

by bas-more

Persistent, verified, cross-session memory for AI agents. 26 tools. SQLite + sync.

120 installs/wk local only

Cathedral — Persistent Memory for AI Agents — questions

Answers built from our own checks of this server.

Why is there no tool list for Cathedral — Persistent Memory for AI Agents?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Cathedral — Persistent Memory for AI Agents working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 202 ms. The bar chart above shows every period we have measured.

How do I connect Cathedral — Persistent Memory for AI Agents?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Cathedral — Persistent Memory for AI Agents need an API key?

Yes. Every time we knock, Cathedral — Persistent Memory for AI Agents answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Cathedral — Persistent Memory for AI Agents?

It answers our handshake in 202 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

How many people use Cathedral — Persistent Memory for AI Agents?

The pypi package cathedral-mcp was installed 94 times in the last week. Week over week that is -10%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Cathedral — Persistent Memory for AI Agents open source?

The code is open source: it is published under the MIT licence, written in Python, 11 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at cathedral-ai.com, which runs on its operator's own terms.