exomem

<!-- mcp-name: io.github.Artexis10/exomem -->

Durable memory with sources, proof, history, and review for MCP-capable agents.

exomem turns an owned Markdown/Obsidian vault into a local knowledge substrate for Codex, Claude Code, Cursor, chatbots, CLI agents, and any client that can call MCP tools. Your files stay plain, local, portable, and editable outside the server.

agent -> MCP tools -> exomem -> your Markdown / Obsidian vault

Prove it in 30 seconds

uvx exomem demo

One command, no install, no config, no vault of your own needed:

exomem demo — bundled sample vault, keyword mode, fully local
vault: /tmp/exomem-demo-XXXXXX

1. doctor: PASS (0.8s)
2. find "retrieval": PASS (0.1s)
   - Knowledge Base/Sources/Sessions/2026-06-30-sample-session.md
   - Knowledge Base/Notes/Insights/retrieval-needs-owned-files.md
3. get retrieval insight: PASS (0.0s)
   - title: Retrieval needs owned files
   - type: insight
   - excerpt: Local-first knowledge tools should retrieve from files the user already owns.
4. audit: PASS (0.0s)

demo PASS — total 1.0s. This is your proof: agents search files you own.
Next: connect your own vault with `exomem setup`

Runs fully local and read-only against a sample vault bundled in the package. Add --keep to leave that copy on disk afterward and open it in Obsidian.

Install in one line

Mac / Linux — paste into Terminal:

curl -fsSL https://raw.githubusercontent.com/Artexis10/exomem/main/scripts/install.sh | sh

Windows — paste into PowerShell:

irm https://raw.githubusercontent.com/Artexis10/exomem/main/scripts/install.ps1 | iex

Either one installs uv, installs exomem, and walks you through exomem setup, which wires up every agent client on the machine — Claude Code and Codex both get the MCP server, all ten skills, and the capture/retrieve hooks.

Safe to run again later — it skips whatever's already done. If it can't prompt you interactively (e.g. run from another script), it prints the exact command to run next instead of guessing. Prefer to run each step yourself? See below or the full manual walkthrough in QUICKSTART.md.

Claude Code: install as a plugin

The plugin carries the skills and hooks. Its MCP entry is an optional shared HTTP URL; it deliberately does not auto-start a full stdio server in every Claude Code session:

/plugin marketplace add Artexis10/exomem
/plugin install exomem@exomem

Then choose the route. If you already run Exomem as a service for phone or hosted access, reuse that one authenticated core:

exomem setup --vault "/path/to/vault" --mcp-url https://<host>/mcp

For local-only use, run exomem setup --vault "/path/to/vault" --stdio. Stdio is intentionally explicit because each client session owns its process and can load its own embedding runtime. When updating from an older plugin, run /plugin update exomem@exomem, then /reload-plugins or restart Claude Code before rerunning setup.

claude.ai and ChatGPT

Neither platform can install skills programmatically — upload is manual. Build the archives, then upload them in the client's settings:

exomem package-skills          # writes dist/skills/*.zip (all ten)

Point the client at your server as a connector (see docs/remote-quickstart.md). Neither platform has a hook system, so capture there is skill-driven rather than automatic.

Set it up in 5 minutes

uv t