Skip to main content
Keynodex Memory is in the Claude Connectors Directory. Connect in a minute
Keynodex Memory (KM) · Live now · Free to start

One memory. Every AI. No starting over.

Keynodex Memory carries your persistent, verifiable context across AI models, agents, apps and sessions, so every AI can pick up where the last one left off, with you in control.

Start freeSee it work
Sign in with GoogleNo SDK or API keysYour account only
FOUR AIS · ONE MEMORY

ChatGPT picks up where you left off. Continue my repair website work from Claude. It finds the saved handoff in Keynodex Memory, checks that nothing newer was saved, then drafts the next step: the request form.

Real recordings from our own work, trimmed and sped up in places. No sound.

Works withClaudeChatGPT (beta)Claude CodeCodexOpenCodeand other MCP apps with sign-in
Why it matters

Every new chat starts cold. It doesn't have to.

Without shared memory

  • You paste the same summary from one AI into the next.
  • Your rules and preferences get forgotten between sessions.
  • Decisions made in one app never reach the others.
Every session starts from zero

With Keynodex Memory

  • Save a decision once. Any connected AI can read it.
  • Standing rules load at the start of a session.
  • Leave a handoff in one AI and pick it up in another.
One memory across every AI you connect
What it remembers

Context that keeps its value.

Not a chat log. Keynodex Memory (KM for short) is structured memory your AIs can search, trust and build on.

Decisions and rules

Tell it once. Standing rules and past decisions load when a session starts.

Loaded when a session starts

Handoffs

Save where you stopped and what's next, so the next AI starts from there.

Pick it up in any connected AI

Playbooks

Turn a fix you worked out once into steps any AI can run again.

Runs again, step by step

Verified facts

Attach a check to a fact, so stale information gets flagged instead of repeated.

Stale facts get flagged

Session briefs

Each session starts with a short brief of what matters now.

One short brief per session

Organized for you

Each memory is filed into a workspace, with the reason it went there. Anything unclear waits for you in your vault.

Filed for you, with the reason why
Start free
How it works

Save in one AI. Recall in the next.

One private memory sits between the AIs you use. Here is what happens on each side.

Save
  1. You tell your AI what mattersA decision, a rule, or where you stopped and what's next.
  2. Keynodex Memory keeps itIt's stored in your private account, not in one app's history.
  3. It stays until you change itEdit or archive anything later in your vault.
Recall
  1. Open any connected AIAsk it to pick up where you left off.
  2. It finds what mattersKM returns the decisions, rules and next steps for this work.
  3. Your AI keeps goingNo summary to paste. No starting over.
Connect

Up and running in a minute.

One address for every AI: sign in with Google, no API key to create or manage.

Claude, web and desktop

  1. Open Settings, then Connectors.
  2. Search for "Keynodex Memory" and choose Connect.
  3. Sign in with Google on the consent page.

Or add a custom connector with this address:

https://memory.keynodex.com/mcp
You stay in control

SDK-first memory layers
  • Install an SDK and wire it into each agent.
  • Create, store and rotate API keys yourself.
  • Only the apps you integrate can use it.
Integration work for every agent
Keynodex Memory
  • Terminal agents like Claude Code, Codex and OpenCode connect to one address.
  • Chat apps add it as a connector. No code needed.
  • Sign in with Google. No keys to leak.
  • Your account only. We don't train on your memories.
  • See and edit everything it remembers in your vault.
Built for developers. No SDK required.
Security

Private by design. Tested on every build.

What you tell your AIs is personal. Here is how Keynodex Memory keeps it yours, with nothing on this list we can't back up.

OAuth 2.1 · PKCE

No keys to leak

You sign in with Google. Apps connect through OAuth 2.1 with PKCE, so there's no API key to create, paste or lose.

1 store per account

Your own private store

Every account gets its own separate database. Your verified sign-in decides which one a request reaches, never what an app claims, and anything ambiguous is refused.

CI · isolation test

Checked on every build

An automated test checks that one account can't read another's memories. It runs every time we build.

Tokens · 1 hour

Short-lived access

Connected apps get access that lasts an hour at a time, then have to refresh it with a grant you can end.

Logs · no content

Kept out of the logs

Request logs record what happened, like the time, route and status, never what your memories say. Private responses are never cached.

Policy · in writing

Never used for training

We don't train models on your memories, and we don't sell your data. It's written into our privacy policy.

Source · stamped

Every memory knows its source

The server records which app wrote each memory, and an AI can't fake it.

Erasure · 30 days

You decide what stays

Edit, archive or delete any memory from any connected AI. Deleting hides it right away. For permanent erasure, ask us and it's done within 30 days.

Everything travels over HTTPS, with rate limits on every connection. Security questions or reports: [email protected]. Read the privacy details

In the wild

Real mentions from around the web. Hover to pause.

Tell us how it fits your stack. We'd love to feature real stories from real users. Share yours
+Your nameUsing Keynodex Memory?
Just use keynodex memory mcp and thank me later.
r/Reply on r/opencodeCLIReddit thread
Keynodex Memory gives coding agents (OpenCode, Claude Code, ChatGPT, Codex) persistent memory across sessions.
GGlamaMCP connector listing
If I had to disconnect it right now, that would be a problem.
KKeynodex founderKeynodex
Keynodex Memory is a private, tenant-scoped memory store for Claude and other MCP clients.
MManufactMCP catalog listing
Plans

Free to start. Pro when you need more.

FREE

Free

  • Up to 100 active memories
  • Every connector and tool
  • We tell you before you reach the limit. Nothing is deleted.
Start free
PRO

Pro

  • Unlimited memories
  • Priority support
  • Upgrade any time from your account
See plans
Questions

Good to know.

What is Keynodex Memory (KM)?

Keynodex Memory, or KM for short, is a private memory your AIs share. You connect it to the AI apps you use, and they can save and read the decisions, rules and next steps you want kept, so a new chat or a different AI doesn't start from zero.

Which AIs work with it?

Claude (web, desktop and Claude Code), ChatGPT (beta, through developer mode), Codex, OpenCode, and other apps that support remote MCP servers with sign-in.

Do I need an API key or an SDK?

No. You add a connector and sign in with Google. There is no API key to create or manage.

Is my memory private?

Your memory belongs to your account only. We don't train on your memories, and you can see and edit everything in your vault.

What happens when I reach the free limit?

You're told when you're near 100 active memories. Nothing is deleted. Upgrade to Pro for unlimited memories.

Stop starting over.

Keynodex Memory. One memory for every AI you use.

Start freeRead the setup guide