Cognition Cloud is an MCP-native memory layer that persists what your AI learns about your business — so every session picks up exactly where the last one left off.
Every AI session starts cold. You re-explain your business, your audience, your preferences. Your AI gives generic answers because it doesn't know what you actually need. Hours of context — gone every time.
Your AI carries forward what it learned — your clients, your goals, what worked, what didn't. It builds a working model of your business that sharpens with every session. The longer you use it, the better it gets.
Three steps to connect — then one guided conversation teaches your AI who you are.
Sign up at cognition.publicmcp.org/signup — email in,
magic link back, your cog_ key shown once. Free, no card.
VS Code: install the
Cognition Cloud extension,
run Cognition: Set API Key, paste your key. Claude, Cursor, Windsurf, or any MCP client:
add https://cognition.publicmcp.org/mcp with your key.
Open a chat and say start my onboarding — a 10–15 minute guided conversation, a few questions at a time. Every answer is saved as a memory while you watch, and it closes with a live recall demo plus your first session brief. Skip anything; your agent circles back later.
From then on, the daily rhythm is two phrases: open work with load my context — your AI pulls your brief and the memories that matter today — and wrap up with end session so it saves what happened and primes tomorrow. That closing habit is what makes the memory compound.
Not every piece of information deserves to be remembered forever. Cognition Cloud knows what to keep, what to surface, and when. The result is a system that gets more precise over time, not noisier.
What your AI learns in one session carries into the next. Business context, decisions, client details, preferences — retained across every conversation without manual re-entry.
Not everything stored gets surfaced. Cognition Cloud determines what's relevant to the current session and surfaces it — without you managing what to include or exclude. The right context appears when it's needed.
Connects directly to Claude, Cursor, Windsurf, or any MCP-compatible agent via a single endpoint. No plugins, no integrations, no custom wrappers. Works with what you already use.
Your memory store is isolated — no shared infrastructure, no cross-tenant data, no training on your content. What your AI learns about your business stays in your business.
The longer you use it, the more precisely it knows what's worth surfacing. It improves on its own. Set it up once. Let it compound.
Cognition Cloud connects over the Model Context Protocol. Install the Cursor plugin or add your endpoint and API key once — no code changes, no vendor lock-in.
Manual context pasting is fragile — it depends on you remembering what to include, and it costs tokens every session. The MCP Memory Server loads only the most relevant context automatically, prioritized by what the system has learned is actually useful to your specific workflow. It's the difference between rereading your notes and having an assistant who already knows what you need.
Yes. Add your Memory Server endpoint under Settings → Connectors in claude.ai. Once connected, your AI will automatically load relevant context at the start of each session. Works with Claude Code, Cursor, and Windsurf as well.
The system manages memory relevance automatically over time. You don't need to curate it manually — things that matter stay accessible, things that don't gradually stop surfacing. Some entries can be marked permanent if they should never be forgotten.
No. Your memory store is private, isolated, and never used for model training. No third-party AI provider ever receives your memory content — it stays entirely within your instance.
The current beta supports one memory store per endpoint. For teams that want shared memory on a private single-tenant server, use the team / private deployment form on the signup page.
