MCP memory server
Your agents forget everything. Keynodex Memory doesn't.
Keynodex Memory is a model-agnostic MCP memory server your AI agents share: persistent memories, executable playbooks, and verified claims that survive every session. Works with Claude, ChatGPT, and any MCP client. Live now.
- Protocol
- MCP
- Persistence
- Durable
- Scope
- Cross-agent
- Isolation
- Per-account
How it fits
One store. Every agent.
Your agent already speaks MCP. Keynodex Memory sits on the other side of the protocol as durable storage: what one session learns, every future session inherits.
- 1. CONNECT
Sign in and add the connector to Claude, ChatGPT, or any MCP client.
- 2. WORK
Your agent pulls the right memories before it repeats work, and saves new facts, decisions, and fixes as they surface.
- 3. RETURN
The next session starts already briefed. No re-explaining your stack, your project, or your rules.
Capabilities
What your agents get
Memories that persist.
Durable, atomic facts about your projects, preferences, and decisions. Saved once, recalled in any future session.
Playbooks.
Repeatable procedures with steps and run history. The fix you found last month becomes the fix your agent applies next time.
Verified claims.
Facts can carry a verification command and a staleness window, so your agent can tell fresh truth from rot.
Session briefs.
Start every session with standing rules and recent context pre-loaded instead of starting from zero.
Cross-agent by design.
One store shared across Claude, Claude Code, ChatGPT, and any MCP client. Switch tools without losing what they know.
Isolated by default.
Every account gets its own isolated store. Your memory is yours alone.
“If I had to disconnect it right now, that would be a problem.”Connect
Add it like any MCP server
Keynodex Memory registers in your MCP client the same way any memory server does. Because it speaks the Model Context Protocol, it connects to any MCP-compatible client, so your agents share one memory instead of keeping separate, siloed context.
- Claude
- ChatGPT
- Claude Code
- Codex
Model-agnostic by design. The guided connect steps live on the product at memory.keynodex.com. Sign-in happens in the browser; there is no API key to manage.
claude mcp add --transport http keynodex-memory https://memory.keynodex.com/mcpOne command from a terminal, or add the same URL as a connector in claude.ai or ChatGPT. Sign-in happens in the browser.
Frequently asked questions
01
What is an MCP memory server?
MCP (Model Context Protocol) is the open standard AI tools use to talk to external services. An MCP memory server is durable storage on the other side of that protocol: your agent reads and writes memory through standard tool calls, and the store persists after the session ends.
02
Which AI tools does it work with?
Keynodex Memory works with Claude (web and Claude Code), ChatGPT, and any client that supports MCP connectors. It is model-agnostic: the store belongs to you, not to any one assistant.
03
What does it actually store?
Three kinds of records. Memories: atomic, durable facts. Playbooks: repeatable procedures with run history. Claims: facts that carry a verification command and a staleness window. You decide what gets saved.
04
Is my data shared with other users?
No. Every account gets its own isolated store. No other account can read your memories. Keynodex does not train models on your memories.
05
What happens on day one, before anything is saved?
The store starts empty and fills as you work. Save your stack, your conventions, and one recurring fix, and the next session already starts ahead of the last one.
06
How do I connect it?
Sign in with Google at memory.keynodex.com, then add the connector to your client. Claude and ChatGPT both take the connector URL directly. From a terminal: claude mcp add --transport http keynodex-memory https://memory.keynodex.com/mcp
07
What is an MCP server for AI?
For AI, an MCP server is how an assistant like Claude or ChatGPT reaches beyond its own text: reading data, calling an API, or recalling context from a past session. The AI acts as the MCP client and the server provides tools and resources. Because MCP is a shared standard, one memory server works across every AI app that speaks MCP.
08
How do I add an MCP server to Claude Code?
Use the claude mcp add command: for a local server give it the launch command, for a remote server give it the URL. Claude Code lists the server's tools and makes them available to the agent. Keynodex Memory is a remote server, so it is one line: claude mcp add --transport http keynodex-memory https://memory.keynodex.com/mcp, then authenticate from the /mcp menu. Sign-in happens in the browser; there is no API key to manage.
Available now
Give your agents a memory.
Live now. Setup takes a minute at memory.keynodex.com.