Uninstall
How to remove AxiomSeal completely
A system you cannot cleanly remove is a system you never really chose. Below is every place we touch and how to undo each one. If anything on this page turns out to be incomplete, that is a bug — tell us.
The short way
If you connected with the one-line command, this is all it takes — nothing was ever written into your project.
claude mcp remove axiomseal # and, if you installed it for your whole account: claude mcp remove --scope user axiomseal
Or let your AI do it
This prompt works in Claude, Cursor, Gemini or any assistant with file access. It is written to be careful: it removes only our entry, leaves your other MCP servers alone, and will not touch your memory database without asking you first.
Copy into your assistant.
Please remove AxiomSeal from this machine completely, and be careful: 1. MCP config — remove ONLY the entry named "axiomseal". Leave every other MCP server untouched. Look in: .mcp.json in the project, .cursor/mcp.json, .vscode/mcp.json, ~/.claude.json, and ~/.gemini/extensions/axiomseal/. For Claude Code you can also run: claude mcp remove axiomseal 2. CLAUDE.md — delete everything between <!-- AXIOMSEAL:BEGIN --> and <!-- AXIOMSEAL:END --> including those markers, and delete the file .axiomseal/AXIOMSEAL.md if it exists. Do not touch the rest of the file. 3. Hooks — if any hook in ~/.claude/settings.json points at an AxiomSeal script, remove that hook entry and the script it references. 4. Local working files of the hooks — ~/.claude/EON-MEMORY.md, ~/.claude/eon_seals_cache.json, ~/.claude/eon_last_tools.json, ~/.claude/eon_distill_state.json, ~/.claude/eon_seal_guard.log, ~/.claude/logs/eon_client.log and the folder ~/.claude/axiomseal/. They are not my memories: those are stored on the AxiomSeal server. Ask me before removing these files, and offer to export my memories from the dashboard first. 5. Finally, list what you removed and what you left behind, and tell me plainly if anything could not be removed automatically.
Everything we touch
| Location | What we put there | How to undo |
|---|---|---|
| .mcp.json (project folder) | MCP server entry named “axiomseal”, including your API key if you used the manual route. | Remove that one entry. Leave any other server in the file alone. |
| ~/.claude.json | MCP server entry, if you connected with --scope user. | claude mcp remove --scope user axiomseal |
| .cursor/mcp.json, .vscode/mcp.json | Same entry for Cursor and VS Code. | Remove the “axiomseal” key from mcpServers. |
| ~/.claude/agents/ and ~/.claude/skills/ | Agent and skill files, depending on how you installed, for example with the older npm package (eon-memory 1.2.1–1.2.4). | Delete the ones we shipped. The uninstall script removes only files that are byte-identical to a version we shipped; files you changed stay and are listed. |
| ~/.claude/mcp-oauth-tokens/axiomseal.* | OAuth tokens stored for the AxiomSeal connection. | Delete these files. The uninstall script removes them for you. |
| ~/.gemini/extensions/axiomseal/ | A Gemini CLI extension folder. | Delete the folder. |
| CLAUDE.md | A block between the AXIOMSEAL:BEGIN and AXIOMSEAL:END markers. | Delete everything between and including the two markers. The rest of your file is yours and stays untouched. |
| Hooks in ~/.claude/settings.json | Only if you opted into them during setup. | Remove the hook entry and the script file it points at. |
| ~/.claude/eon_config.json | The access settings of the hooks, including your API key. | Delete the file. |
| Working files of the hooks in ~/.claude/ | EON-MEMORY.md (titles of the last 50 automatically saved memories), eon_seals_cache.json (a copy of your active seals), eon_last_tools.json, eon_distill_state.json, eon_seal_guard.log, logs/eon_client.log and the folder axiomseal/ (manifest and session state, including file names). Your memories themselves are not in these files; they are stored on our server. | Delete these files and the folder. The uninstall script removes them for you. |
| Your own project files | Your own files in your projects (for example CLAUDE.md outside the AxiomSeal block). | This is your data, not ours. Export it first if you want it; nothing deletes it automatically. |
If your API key was ever committed
Deleting the file does not remove the key from your git history. If a config containing your key was committed at any point, treat that key as exposed: revoke it in Settings and create a new one. This is the reason the one-line command is the recommended route — it stores nothing inside your project.
Your data
Removing the connection does not delete your account or the memories stored on our side. To have those deleted as well, ask in Settings. You can export everything first — see the privacy policy for what we keep and for how long.