openmymemo
Your AI memory as a local folder you own. Claude, Codex, Cursor and any MCP app share it; you see every change and can undo it.
Install / Use
claude mcp add MyMemoAI -- npx -y github:MyMemoAI/openmymemoIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
AI & Machine LearningSupported Platforms
Our assessment of openmymemo
openmymemo scores 84/100 on our quality scale, 614th of 949 AI & Machine Learning skills we index.
Its MCP Server is 26 KB long, well organised into 21 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.
It has 10 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated today, so openmymemo is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 97/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
openmymemo compared with similar skills
All 4 of these similar skills score higher than openmymemo; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| openmymemo (this skill)by MyMemoAI | 84 | 10 | today | MCP Server |
| claude-memby thedotmack | 100 | 101.9k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 100.1k | today | CLAUDE.md |
| Understand-Anythingby Egonex-AI | 100 | 87.2k | 8d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 76.5k | today | CLAUDE.md |
Frequently asked questions
- How do I install openmymemo?
- Run
claude mcp add MyMemoAI -- npx -y github:MyMemoAI/openmymemo. The install tabs above show the steps for each supported agent. - Which AI agents does openmymemo work with?
- It is written for Claude Code, Claude Desktop, Cursor, Gemini CLI and OpenAI Codex, as a MCP Server file. Other agents that read the same format can often use it too.
- Is openmymemo safe to use?
- It is Apache-2.0-licensed and scores 97/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is openmymemo still maintained?
- The repository was last updated today, so openmymemo is actively maintained.
Skill content
View source on GitHubOpenMyMemo
Your AI memory as a plain folder on your own computer. See exactly what models remember about you; let Claude, Codex, Cursor or any MCP app share it, so what you tell one the others know too, and see every change they make, with one click to undo. If an account gets banned, a vendor shuts down or you switch models, your memory comes with you.
<!-- mcp-name: io.github.MyMemoAI/openmymemo --><picture> <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/MyMemoAI/openmymemo/main/docs/images/panel-memories-dark.png"> <img alt="The OpenMyMemo panel: memories grouped by topic, each showing where it came from, and a note that AI apps made changes to review" src="https://raw.githubusercontent.com/MyMemoAI/openmymemo/main/docs/images/panel-memories-light.png"> </picture>v0.2. What changed in each release: CHANGELOG.md. Product design and status: docs/product-design.md. The folder format, for any tool that wants to read or write it: docs/MEMORY_FORMAT.md.
Why I built this
My OpenAI account was banned on October 2, 2026, with no warning and no specific explanation. I had used ChatGPT since it launched in late 2022, and its year-end recap put me in the top 1% of users. I appealed and never got a reply. Nearly four years of conversations, and everything ChatGPT had learned about me, went with the account.
I had thought of that memory as mine. It wasn't. It lived on OpenAI's servers, in an account they could close at any time, and when they did, the memory went with it, with no one to ask for it back.
OpenMyMemo is what I wish I'd had: my AI memory as a folder on my own computer. Any model can read it, I can see and undo every change a model makes, and no single company can take it away.
— Leo
Get started
There are two ways in. Both use the same memory folder, the same panel and the same core, so you can switch or use both.
The Mac app
For everyone: no terminal, no config files, no Python to install.
- Download the disk image for your Mac from the latest release:
OpenMyMemo-<version>-arm64.dmgfor Apple silicon (M1 and later) orOpenMyMemo-<version>-x86_64.dmgfor an Intel Mac, macOS 12 or later. (Apple menu → About This Mac shows which: "Chip: Apple …" or "Processor: … Intel …".) - Open it and drag OpenMyMemo to Applications. (Opened straight from the disk image, it offers to move itself there.)
- Open OpenMyMemo from Applications. Release builds are signed and notarized and open like any app. A build without a Developer ID signature (one you built, or a fork's) needs one extra step the first time: on macOS 15 and later, try to open it, then go to System Settings → Privacy & Security and click Open Anyway; on earlier versions, right-click the app and choose Open.
- The first start downloads Python and the libraries OpenMyMemo runs on, about 25 MB and usually under a minute, into
~/Library/Application Support/ai.mymemo.openmymemo/. It happens once; after that the app starts in a couple of seconds, also offline. - A short guide connects the AI apps on your Mac with one click each and brings over the memory ChatGPT, Claude or Gemini already have. Your memories live in
~/OpenMyMemo.
The app shows the panel in its own window, puts the number of changes to review in the menu bar, and notifies you when an AI app changes something. To update, download the new disk image and drag it to Applications again; your memory folder isn't touched.
The app also installs an openmymemo command, which the AI apps it connects run (Settings → Advanced shows where). It is the full command line below, so you can use it in Terminal too.
The command line
For developers, and anyone who prefers a terminal. Nothing is fenced in: everything the app does is a command, and the folder format (docs/MEMORY_FORMAT.md) is the interface. Requires uv:
uv tool install openmymemo # from PyPI; `uv tool upgrade openmymemo` updates it
uvx openmymemo … runs it without installing; the AI apps it connects then start it with uvx openmymemo too. For the latest code, install from a clone instead: uv tool install ./openmymemo.
openmymemo init # create ~/OpenMyMemo with 14 default topics
openmymemo apps # the AI apps on this computer, and which are connected
openmymemo connect cursor # connect one: claude-desktop, claude-code, codex, cursor, vscode, …
openmymemo disconnect cursor # remove its OpenMyMemo entry and revoke its access
openmymemo import chatgpt # paste ChatGPT's "Manage memories" page; it lands in "From ChatGPT"
openmymemo import auto ~/.claude/CLAUDE.md # another app's memory file: CLAUDE.md, AGENTS.md, GEMINI.md, rules, memory.md
openmymemo sort # file imported memories into topics, one suggestion at a time
openmymemo serve # open the panel at http://127.0.0.1:8787
openmymemo review # what AI changed since you last looked: keep, edit or undo
connect edits only the app's own MCP config (keeping a backup) or runs the app's own mcp add command, and tells you to restart the app; where it can't do that safely it prints the config to paste. More: doctor (checks the setup and says what to fix when an app doesn't see your memory; it prints no memories), status, approval on|off (on: every AI change waits for you), context --connector <id> (what an AI actually receives), export --format claude|chatgpt|markdown|json, search, add, connector add|list|config|rotate|remove (configs by hand), setup codex (load your memory at the start of every Codex session). Use --vault or OPENMYMEMO_HOME to put the folder elsewhere.
Plugins
Install as many as you like: they all share one memory. Every plugin uses the same ~/OpenMyMemo folder by default (created on first use), so something you tell Claude, Codex knows in its next session, and the other way round. Each plugin loads your memory into new sessions where the app supports it — starting with a one-line summary of what AI changed since you last looked — and serves the panel at http://127.0.0.1:8787 while the app is running. They need uv except where noted.
| App | Install |
| --- | --- |
| Claude Desktop | Download openmymemo-<version>.mcpb from the latest release (or build it with uv run python scripts/build_mcpb.py), then double-click it (or Settings → Extensions). Nothing to fill in: leave the memory folder empty to use ~/OpenMyMemo. Then quit Claude Desktop and open it again. Claude Desktop installs Python and the dependencies itself; no uv needed. |
| Claude Code | /plugin marketplace add MyMemoAI/openmymemo, then /plugin install openmymemo@openmymemo, then restart Claude Code. Adds /openmymemo:memory and /openmymemo:remember. |
| Codex | Three steps, see Codex below. |
| Gemini CLI | gemini extensions install https://github.com/MyMemoAI/openmymemo, then restart Gemini CLI. It uses ~/OpenMyMemo; for another folder, use openmymemo connect gemini-cli instead. |
| Cursor | Panel → Connectors → Connect, or openmymemo connect cursor. |
| VS Code | Panel → Connectors → Connect, or openmymemo connect vscode. |
After installing, quit the app completely and open it again so it loads OpenMyMemo. The first launch downloads Python and the dependencies (about 5 seconds on a fast connection; Codex gives MCP servers 10). If an app then says the OpenMyMemo server failed to start, restart it once more.
Then open the panel at http://127.0.0.1:8787 in your browser (the page pictured at the top); bookmark it. It's there whenever Claude Desktop, Claude Code, Codex or Gemini CLI is running: your memories, what AI changed (Changes), the exact text each app gets (What AI sees) and the connected apps (Connectors). Without a plugin, openmymemo serve starts it and opens the browser.
Codex
You need uv. Steps 2 and 3 are needed only once: Codex doesn't run hooks that plugins ship, so OpenMyMemo adds its own session-start hook.
-
Install the plugin. In a terminal:
codex plugin marketplace add MyMemoAI/openmymemo codex plugin add openmymemo@openmymemoThen restart Codex: quit the ChatGPT desktop app and open it again, or start
codexagain in the terminal. -
Set up the hook. Start a new Codex session and ask it to "set up OpenMyMemo". It adds a hook to
~/.codex/hooks.jsonand leaves your other hooks alone. If you installed the CLI,openmymemo setup codexdoes the same. -
Trust the hook. In the ChatGPT desktop app, open Settings → Coding → Hooks and trust "Loading your OpenMyMemo memory". Or open Codex in a terminal (
codex), type/hooks, select SessionStart and trust it there. The app and the terminal share these settings, so trusting it in either place covers both.
From your next new session on, Codex starts with your memory. The plugin also adds the memory, remember and codex-setup skills.
Connecting AI apps by hand
- Local process (recommended): Claude Desktop, Claude Code, Cursor, Codex and other stdio MCP clients.
openmymemo connect <app>writes the app's config for you (openmymemo appslists them); for anything else,openmymemo connector add <name>prints a config with absolute paths to paste in. Give each app its own--connectorso permissions and logs stay separate. - From the MCP Registry: OpenMyMemo is listed in the official MCP Registry as
io.github.MyMemoAI/openmymemo, so MCP clients that browse it can install it from there (it runs withuvx). - Local HTTP:
openmymemo connector add <name> --httpcreates a token (shown once) for use withopenmymemo serveathttp://127.0.0.1:8787/mcp. - ChatGPT and claude.ai on the web, through OpenMyMemo Cloud (optional): they can only reach MCP servers on the public internet, so they can't start OpenMyMemo on your computer the way the apps above do. With MyMemo Pro, Ultra or Lifetime, OpenMyMemo Cloud relays their calls to OpenMyMemo on your computer: sign in from the panel (Connectors → On the web → OpenMyMemo Cloud) or with
openmymemo cloud link, then add the URL it shows as a custom connector in claude.ai (Settings → Connectors) or in ChatGPT (with Developer Mode on). It is a relay, not hosting: your memory stays on your computer, the web apps reach it only while OpenMyMemo runs there, and MyMemo passes each call through without keeping your memory. It does nothing until you sign in, and you can hide it in Settings. On the OpenAI side, Codex works without it, including the Codex built into the ChatGPT desktop app.
Tools AI apps see: memory_context, memory_search, memory_get, memory_propose, memory_proposals, plus the recall prompt.
Works with
| App | Status |
| --- | --- |
| Claude Desktop (Chat, Cowork and Code) | ✅ Extension |
| Claude Code | ✅ Plugin |
| Codex (the CLI, and Codex in the ChatGPT desktop app) | ✅ Plugin |
| Gemini CLI | ✅ Extension |
| Cursor, VS Code, Zed, Cline, Kiro, LM Studio, opencode, GitHub Copilot CLI and other MCP apps | ✅ One click in the app, openmymemo connect, or a config to paste (openmymemo apps lists them all) |
| ChatGPT and claude.ai on the web | ✅ Through OpenMyMemo Cloud (optional
Truncated for display — read the full file on GitHub.
Related Skills
claude-mem
101.9kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Agent-Reach
100.1kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
Understand-Anything
87.2kGraphs that teach > graphs that impress. Turn any code into an interactive knowledge graph you can explore, search, and ask questions about. Works with Claude Code, Codex, Cursor, Copilot, Gemini CLI, and more.
headroom
76.5kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
