Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@cogito-mem what did we call the staging server?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Long-term memory for Claude Code, on your own machine. Cogi the squirrel keeps every message you and Claude exchange, and brings back what Claude forgot. No API key, no cloud, no AI calls to store.
Claude stops forgetting. Every message and reply is kept word for word, with its date. When something has dropped out of the context window, or happened last week, the relevant part comes back with your next prompt.
It remembers what you did, too. The commands you ran (and whether they failed) and the files you touched, without their output.
Private and free. One folder on your computer. No account, no API key, no AI calls to save a message. Nothing leaves your machine.
Tested. On LongMemEval-S, the past session holding the answer is among the first five Cogi finds for 99.0% of 500 questions, with no AI model involved; other local memory plugins published 95.2–98.0% as of October 2026. On LoCoMo, the 1,000 tokens Cogi hands back answer 74.7% of questions right, level with rereading the whole conversation (76.5%). A search over 10 million tokens takes 26 ms on a laptop CPU. See the results.
Related MCP server: Claude Persistent Memory
You need Claude Code and uv, on macOS or Linux (Windows is experimental). Then, in a terminal:
claude plugin install cogito-mem --marketplace meridian21lab/cogito-memThe first start downloads the model (310 MB, about a minute). To get updates, turn on auto-update once: /plugin → Marketplaces → cogito-mem → Enable auto-update.
Step-by-step guide · Codex, Claude Desktop, Docker
Tell Claude: Let's call the staging server "acorn".
Clear its short-term memory: /clear
Ask: What did we call the staging server? Claude answers "acorn": Cogi brought it back.
Runs: four Claude Code hooks and one MCP server, cogi. Each runs the released cogito-mem package from PyPI at the exact version the plugin pins (uvx cogito-mem==<version>); the plugin's uv.lock lists that release and numpy with their checksums. After each reply and at the end of a session, the hooks save the new messages from the session's transcript. At the start of a session and with each prompt, they add the few most relevant memories (at most 300 tokens per prompt). The MCP server gives Claude two tools, memory_query and memory_append, answered by a small service that listens on your computer only (127.0.0.1:7327).
Downloads, once, over HTTPS: cogito-mem and its one dependency, numpy, from PyPI (by uv); llama.cpp's llama-server from llama.cpp's official GitHub releases (skipped if you already have it); and the EmbeddingGemma 2 model (310 MB) from Hugging Face. After that, Cogi makes no network calls.
Stores: everything in ~/.cogito-mem/ on your computer: your messages, and a short note of what each turn did, in one SQLite file. API keys, tokens, private keys and passwords are replaced with [redacted] before anything is saved; tool output and file contents are never saved. Text inside <private>…</private> is skipped, and COGITO_MEM_CAPTURE=off pauses saving.
Sends: nothing. No account, no analytics, no telemetry. (The optional benchmark command, cogito-mem eval locomo-qa, which only you would run, sends benchmark questions to the LLM API you set up for it, with your own key.)
Removes cleanly: claude plugin uninstall cogito-mem@cogito-mem, then delete ~/.cogito-mem.
Every file, download and connection, with links to the source: What you install.
cogito-mem | |||||
AI calls to store a message | none | an observer model per tool call (Haiku on your Claude plan by default) | extraction on Mem0's servers | extraction with your LLM key or | in Supermemory's service |
Account or API key | none | optional sign-in | Mem0 Platform API key | an LLM key or the Claude CLI | API key or login |
Where your memory lives | your computer | your computer (cloud sync optional) | Mem0's cloud | your computer (cloud optional) | Supermemory's cloud (local mode available) |
What comes back | your exact words, with dates | AI-written observations | extracted memories | graph facts and summaries | extracted memories |
Searchable after | the same turn | the observer's run | a batch (every 5 exchanges) | the next graph run | the background save |
Keep your project's rules in CLAUDE.md, and let Cogi remember what happened.
Collect, keep, find: what Cogi stores and how it finds it | |
The numbers, and how to reproduce them | |
HTTP, Python, terminal, settings, FAQ, roadmap | |
Every file, download and connection; privacy and terms | |
Running the tests and the evaluations |
Early access. v0.2 is new, built and tested (over 200 tests), and still being measured. Feedback and issues are very welcome.
This server cannot be deployed
Persistent memory for Claude Code and Cursor. Stop re-explaining your project every session.
Shared work memory for Claude Code, Codex, Cursor and chat, scoped to each repository.
Private memory for AI agents: save and recall facts across Claude Code, Codex, Cursor and ChatGPT.
Shared memory for AI tools: save once, recall word for word from Claude, ChatGPT, Codex or Gemini.