We're calling the new product Atlas. Launch is 3 November, and billing runs on Postgres and Stripe.
Noted. I'll keep both.
create_memory"Project Atlas launches on 3 November 2026"
create_memory"The billing service runs on Postgres and Stripe"
Works with any MCP assistant
GuardianMemory is one long-term memory that every assistant you use reads and writes. Say a thing once, in any of them, and the rest know it. Connect with a single URL.
Create your memory bank See how it connects
Free while we learn. No card. About a minute to connect.
We are letting people in a few at a time. Free while we learn, no card.
We're calling the new product Atlas. Launch is 3 November, and billing runs on Postgres and Stripe.
Noted. I'll keep both.
create_memory"Project Atlas launches on 3 November 2026"
create_memory"The billing service runs on Postgres and Stripe"
Add the launch date to the banner.
search_memory"Atlas launch date"
1. (0.91)Project Atlas launches on 3 November 2026 from Claude
Done. The banner now reads 3 November.
The same memory, read by a different assistant, two days later.
The problem
You have told ChatGPT you write in British English four times. Cursor still does not know which database the billing service uses. Claude worked through your pricing last Tuesday, and today's conversation has no idea it happened.
Each assistant keeps a small memory of its own, in its own silo, that you cannot read properly, fix, or take with you. So you paste the same paragraph about yourself into every new chat. Or you don't, and get confidently wrong answers.
How it connects
Paste the endpoint into any assistant that speaks MCP, approve it once in your browser, and it gets two tools.
search_memory
At the start of every conversation it reads your profile: what you pinned, what gets used most, what is newest. When you mention something it does not know, it searches by meaning, not keywords.
create_memory
When it learns something worth keeping, it saves one plain sentence. If a fact has changed, the new one replaces the old.
Your endpoint
https://app.guardianmemory.com/mcp
Settings → Connectors → Add custom connector, and paste the endpoint above. Approve it once and Claude holds its own tokens from then on.
claude mcp add --transport http guardian https://app.guardianmemory.com/mcp
Then run /mcp inside Claude Code and pick Guardian to sign in.
Settings → Connectors → Create, paste the endpoint above and choose OAuth. Custom connectors need developer mode switched on.
{
"mcpServers": {
"guardian": { "url": "https://app.guardianmemory.com/mcp" }
}
}{
"servers": {
"guardian": { "type": "http", "url": "https://app.guardianmemory.com/mcp" }
}
}In .vscode/mcp.json, or your user configuration.
What stays true
Agent-written memory rots. The same fact reworded five ways, a home address from two moves ago, the important thing buried under the trivial. GuardianMemory cleans as it goes, and lets you see everything it holds.
| Capability | Memory inside one assistant | GuardianMemory |
|---|---|---|
| Follows you between assistants | Stays in that assistant | Yes, any MCP client |
| Read and edit every memory | View and delete, mostly | Read, edit, pin, delete |
| See what each assistant read and wrote | No | Activity log, per app |
| Outdated facts retired | No | A new fact replaces the old one |
| Near-duplicates merged | No | Yes |
| Bring what an assistant already knows | No | Paste and import |
| Shared with your team | No | Team banks |
Privacy and control
It is free while we learn what people need: 5,000 memories and 2,000 operations a day per account, no card.
Free, one URL, about a minute to connect.
We are letting people in a few at a time. Leave your address and we will send an invite.