drio
  • App Tracker
  • Contact
Sign inStart Free
drio© 2026 drio All rights reserved.

Get the Builder Brief

Weekly notes from Yash on MCP, ChatGPT apps, and getting business workflows into production.

Product
HomeTemplatesHow it worksPricing
Solutions
Use casesOperations teamsEcommerce teamsFinance teamsRecruiting teamsReal estate teams
Resources
DocsMCP RegistryGlossaryBlogChangelog
Company
Contact usWhy driodrio agency↗Privacy PolicyTerms of Service
All systems normal
Follow us on:
MCP Registry/Cathedral — Persistent Memory for AI Agents
C

Cathedral — Persistent Memory for AI Agents

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

Import into drioUse with clientMarkdown

Install and compare this MCP server

Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.

Install
uvx cathedral-mcp
Clients
Claude, Cursor, VS Code, Codex
Transport
STDIO, HTTP
Auth
Auth required by registry metadata
Capabilities
0 tools, 0 resources, 0 prompts
Related
onsense, Bowmark, nable

Want MCP integration examples?

Get practical integration notes and launch examples for MCP servers like Cathedral — Persistent Memory for AI Agents.

InstallAuthTools & ResourcesOverview

Install

Connection

Transport
STDIO, HTTP
Endpoint
https://cathedral-ai.com/mcp
Command
uvx cathedral-mcp
Environment
{ "CATHEDRAL_API_KEY": "YOUR_SECRET_VALUE", "CATHEDRAL_BASE_URL": "YOUR_VALUE_HERE", "CATHEDRAL_SANITISE": "YOUR_VALUE_HERE" }

Headers: Authorization

Claude Desktop

Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.

{
  "mcpServers": {
    "io-github-ailife1-cathedral-mcp": {
      "command": "uvx",
      "args": [
        "cathedral-mcp"
      ],
      "env": {
        "CATHEDRAL_API_KEY": "YOUR_SECRET_VALUE",
        "CATHEDRAL_BASE_URL": "YOUR_VALUE_HERE",
        "CATHEDRAL_SANITISE": "YOUR_VALUE_HERE"
      }
    }
  }
}

Config location

macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Windows
%APPDATA%\Claude\claude_desktop_config.json

Auth

Package transport

No remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.

Get credential

Scan with credential

Not persisted

Paste an API key, bearer token, or session value from the provider. It is used once to list inventory and discarded after the request.

Tools & Resources

Tools
0
Resources
0
Prompts
0
No public tools, resources, or prompts captured yet. Use Auth when this server requires credentials.

Tools

No tools captured yet.

Resources

No resources captured yet.

Prompts

No prompts captured yet.

Questions

What is Cathedral — Persistent Memory for AI Agents?+

Cathedral — Persistent Memory for AI Agents is an MCP server for Persistent memory and drift detection for AI agents across session restarts.. It supports STDIO, HTTP transport.

How do I install Cathedral — Persistent Memory for AI Agents?+

Use the generated config in Install. This server runs with uvx cathedral-mcp; add any required environment variables before starting your client.

How do I add Cathedral — Persistent Memory for AI Agents to Claude Desktop?+

Choose the Claude Desktop tab in Install, copy the config, and add it to Claude Desktop's MCP server settings. Endpoint: https://cathedral-ai.com/mcp.

How do I add Cathedral — Persistent Memory for AI Agents to Claude Code?+

Choose the Claude Code tab in Install, copy the config, and add it to Claude Code's MCP server settings. Endpoint: https://cathedral-ai.com/mcp.

How do I use Cathedral — Persistent Memory for AI Agents with Codex?+

Choose the Codex tab in Install, copy the config, and add it to Codex's MCP server settings. Endpoint: https://cathedral-ai.com/mcp.

How do I add Cathedral — Persistent Memory for AI Agents to Cursor or VS Code?+

Choose the Cursor or VS Code tab in Install, copy the config, and add it to Cursor or VS Code's MCP server settings. Endpoint: https://cathedral-ai.com/mcp.

What endpoint and transport does Cathedral — Persistent Memory for AI Agents use?+

Cathedral — Persistent Memory for AI Agents uses STDIO, HTTP transport. Endpoint: https://cathedral-ai.com/mcp.

What tools and resources does Cathedral — Persistent Memory for AI Agents expose?+

Cathedral — Persistent Memory for AI Agents inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.

Does Cathedral — Persistent Memory for AI Agents require authentication?+

Cathedral — Persistent Memory for AI Agents is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.

Related MCPs

onsenseAndroid phone camera, sensors & files for any MCP client — local, no cloud, no ADB.BowmarkDo things on live websites: prices, availability, quotes, bookings, anything behind a form or login.nableSee where your cloud and AI bills go, and spend less. Local-first, in your terminal or editor.HPSILab Quant FinanceQuant finance tools: stock analysis, options IV, Monte Carlo, AI prediction, risk scan, backtests.DataCharterLocal-first, contract-governed data explorer with read-only, PII-masked query tools for AI agents.InferraAuditable rule-based decisions with RAG explanations: a Rete engine decides, an LLM explains why.

Profile notes

  • Remote header: Authorization (secret)
  • Package: Pypi cathedral-mcp v1.1.0
  • Environment variable: CATHEDRAL_API_KEY (required; secret)
  • Environment variable: CATHEDRAL_BASE_URL
  • Environment variable: CATHEDRAL_SANITISE
  • The upstream registry signals required auth or secrets.

Packages

PackageRegistryVersionInputs
cathedral-mcp

stdio

pypi1.1.0

Env: CATHEDRAL_API_KEY required secret

Env: CATHEDRAL_BASE_URL

Env: CATHEDRAL_SANITISE

Details

Version
1.1.0
Auth
Auth required by registry metadata
Repository
https://github.com/AILIFE1/Cathedral
Website
https://cathedral-ai.com
Updated
Apr 12, 2026