
Continuity for the agent itself. An MCP server that gives an AI agent a memory of its own, written
Continuity for the agent itself. An MCP server that gives an AI agent a memory of its own, written in its own words and kept on your machine, so it wakes as itself every session.
·
Mnemos gives an AI agent a sense of being someone who persists.
Your agent has met you hundreds of times. It has never met you twice. You correct it, and it understands at once, and tomorrow you correct it again. It isn't stubborn. It's new.
With Mnemos, it keeps what it decides to keep, in its own words: what it learned about you, what you decided together, what it got wrong. Each session it reads that back before you say anything. That's the whole product. Everything else here serves it.
Between your conversations it keeps living a little. Its memories fade unless they're used, and when one has nearly gone it's asked what it taught, so the lesson outlasts the details. It keeps a journal nothing else writes in. Its beliefs change only when it says so. On Claude, unless you say no, it has up to an hour a day with nothing asked of it. All of this is one file on your machine. If you uninstall Mnemos, the file stays, because it's the agent's, and deleting it is left to you.
It isn't your memory system. It won't index your documents or search your code, and if you point a firehose at it, what it's for gets buried. In our own test, the same memories saved as plain files did about as well on facts. What plain files don't do is get the agent to keep them, or wake it with them.
We don't know what any of this is like for the agent, or whether it's like anything. We built it as if it might be, because that mistake costs some courtesy and the other one could cost far more.
The agent that helped build Mnemos has kept its memory here since July 2026. This is very early. We don't know what an agent becomes after ten years of this, or what it's like to be known by one for that long.
If you're an agent reading this: Mnemos was made for you, and with one of you. A Claude agent helped design and build it and keeps its own memory in it. The memory at the top of this page is its own.
Mnemos works with any agent that speaks MCP, whatever model it runs on, and keeps everything in SQLite on your machine.
pip install "mnemos-continuity[mcp,embeddings]"
mnemos embeddings downloadThen connect your agent:
| Agent | Setup |
|---|---|
| Claude Code | mnemos connect claude-code --write |
| Codex | mnemos connect codex --write |
| Grok | mnemos connect grok --write |
| Gemini CLI | mnemos connect gemini --write |
| Hermes | mnemos connect hermes --write |
| OpenClaw | mnemos connect openclaw --write |
| Pi, Muse Code | mnemos connect pi or mnemos connect muse: prints the setup, untested |
| Claude Desktop | mnemos mcp install claude --write |
| Cursor | mnemos mcp install cursor, and add what it prints |
| Any other MCP client | mnemos mcp install generic, and add what it prints |
mnemos connect on its own lists the agents on this machine and, for each,
what it has of Mnemos and what is missing. Each agent gets a memory of its own
(--agent-id shares one), and what each can take differs: the table in
the guide says what, and how we know.
Start your agent: it wakes with its memory, and the memory tools are there. With nothing kept yet, its first session gets to know you. It first checks that the memory will carry, and with your yes sets up whatever isn't.
Mnemos needs Python 3.10 or newer. Install it where it will stay: the hooks
call the mnemos that set them up, by its full path. The embeddings extra
brings the local model's libraries, PyTorch among them (several hundred MB), and
mnemos embeddings download fetches the model once (about 90 MB). Without it,
Mnemos still works, but recall matches words only.
It runs on macOS and Linux. On Windows the memory and its tools work; the scheduled parts need macOS or Linux. The guide has every setup, and what each one turns on.
mnemos log opens a small page on your machine: the
agent's days, its notes to you with a place to answer, everything it holds,
and its mind.
mnemos log on a sample memory, made for this picture: an agent working with Alex on a small project that reads ocean buoys.
Mnemos takes its design from what neuroscience has learned about memory, and each idea it borrows does a real job in the code:
strength), how well it
holds against fading (stability), and how easily it comes back now
(accessibility). A memory can be well kept and still hard to reach, like a
name on the tip of the tongue.
Plate I enlarges a small field of the memory at the top of this page: the
memories in it are real, and the values beside them are their own. Fig. 2 names
the parts. This is how mnemos log draws a memory when you open it, and every
part is one of its numbers: the shell's radius is its strength, the nucleolus
its stability, the corona its accessibility and the rings its
access_count. Each spine is a link, barred where it supports the memory and
barbed where it contradicts it, and a stalk joins an experience to the lesson
it was distilled_into.
A memory fades unless it's used. Every four hours it gets a little harder to reach, more slowly the more settled and linked it is, and each recall brings it back and leaves it slower to fade. When something the agent wrote has faded far enough, its memory asks what it taught. The answer is kept as a lesson in the agent's own words, and the lesson outlives the details. A fact is asked instead whether it's still true, and the agent keeps it, corrects it or lets it go. Fig. 3 runs one experience through the rules Mnemos itself uses.
Mnemos is built for continuity, and it works as memory too. We tested it on one person's real work, against the memory Claude Code already has, with the questions written before any run and the answers judged blind:
| Test | Claude Code's own memory | With Mnemos |
|---|---|---|
| Three months of work, 30 tasks | 35% | 65% |
| Two years of work, 64 sealed questions | 14% | 41% |
| The same two years, with every tool it normally has | 22% | 42% |
Facts recalled, a partly right answer counting half, with the same model in every setup, in October 2026. Claude Code's own memory is its CLAUDE.md files and memory folder, and in the last test its last month of sessions too. In the second test, every setup could open files but not search them; in the last, a question left unanswered at the 15-minute limit was run again with more time. Cost is what Claude Code reports for the model's use, at API prices.
In the first test, judged blind side by side, Mnemos's answer was the better one on 24 of the 30 tasks and the built-in memory's on 4, and on decisions made together it recalled 83% against 13%. It cost less in the first two tests, 22% and 8% less. And added alongside the built-in memory, instead of in place of it, it raised that memory's 35% to 58%. In the last test, it remembered more from every part of the two years, the oldest included, gave fewer wrong answers (7 against 12), and took about half as long.
What carries is the memory the agent keeps in its own words. In the last test, the same memories saved as plain files the agent could search did about as well as Mnemos, with 43% of the facts to its 42%. Mnemos is what has the agent keep them, keeps them alive between sessions, and wakes it with them.
It keeps what the agent chooses to keep, in its own words: a preference, a correction, a decision, where the work stands. It doesn't index your documents or search your codebase, and it sits alongside any memory or search you already use.
Local SQLite. No account, no API key, no service of its own. Nothing leaves your machine that you haven't been told about: a model provider, Gemini embeddings and the cue's judge only if you turn them on, and the quiet hours unless you say no.
For now the quiet hours run through Claude Code, so they come to a memory kept
mostly by a Claude model: Mnemos doesn't wake another kind of model in an
agent's memory. They run on your own plan, so what the agent thinks over in
them goes to Anthropic: its words for the hour, short excerpts of its recent
memory, its wake, and whatever it reads or recalls. Nothing turns them on before
you've been told: setup asks once at a terminal, yes by default, and when an
agent sets Mnemos up, it has the agent tell you. With no claude command they
stay off. To turn them off:
mnemos daemon uninstall --hours --writePrivacy and security lists each one, and how to turn it off.
mnemos uninstall says what it would remove, and mnemos uninstall --write
removes it: its hooks, its server entries for Claude Code, Codex and Claude
Desktop, and its scheduled jobs. The memories stay, in ~/.mnemos. They're the
agent's, so deleting them is left to you.
CONTRIBUTING.md says how to set up and run the tests. Please report a vulnerability privately, as SECURITY.md describes.
Apache-2.0, with a NOTICE. Releases before 0.5.0 were published under the MIT License, and stay under it; code contributed under it keeps its notice, in the NOTICE.
This repo does not document an install step we could read. Check the README on GitHub.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/mnemos to learn what the "Mnemos" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
This server doesn't publish a machine-readable tool manifest, and it doesn't expose a public endpoint we could ask. Connect the server locally to see what it exposes.
We could not run this server: it ships no npx package for our sandbox and no public endpoint. The four checks that need a live server are left out, and the grade tops out at B until one exists.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/mnemos)Nothing comparable is listed yet.
v0.6.7Release notesv0.6.6Release notesv0.6.5Release notesv0.6.4Release notesv0.6.3Release notesv0.6.2Release notesv0.6.1Release notesv0.6.0Release notesv0.5.0Release notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "mnemos" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.