Mnemo Cortex MCP Server

The big AI-memory systems run on millions in venture capital. Mnemo Cortex was built by one 73-year-old maker — on Social Security, a $20-a-month Claude subscription, and a stubborn belief that his AI partners should remember him. That is what the mnemo cortex mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

• ~10,000 memories — ingested, compacted and recalled across agents
• ~7,000 verified facts — with confidence laddering and a full audit history
• 84 shipped versions — in five months — the current one is in the release badge above (CHANGELOG)
• Overnight dreaming, USB courier sync with encryption, agent-to-agent sharing — each built

The tools it exposes

The server publishes 4 tools. What each one is for:

• Shared — One Mnemo for all agents. Cross-agent search and dreaming. Full team awareness
• Isolated — Separate Mnemo per agent or per customer. Zero bleed between tenants
• Hybrid — Shared for internal agents + isolated for customer-facing bots. This is what we run
• mnemo — plan** = manual project pad (you write it, agents read it — project specs, active tasks, decision logs, architecture notes)

Getting it running

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.

How it compares

Plenty of payments and commerce 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. Mnemo Cortex's toolset — Shared, Isolated, Hybrid and 1 more — is a fair guide to whether it matches your workflow. It is maintained by guymanndude; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.