AI & MemoryMCP Registrypypi14 toolsA · 82

Exomem MCP server

Name: Exomem
Author: Artexis10

io.github.Artexis10 · Updated today

Local Markdown/Obsidian knowledge substrate for MCP agents with governed memory and hybrid search.

At a glance

Exomem is an MCP server in the AI & Memory category. It runs locally over stdio via `uvx exomem`, and declares no required credentials. It exposes 14 tools, including recall_context, episode_memory and find. It scores A (82/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 9

One-click install

VS Code VS Code Insiders Cursor

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Exomem in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Exomem in Claude CodeAnthropic's agentic CLI

1
Add the server
bash
```
claude mcp add exomem -- uvx exomem
```
2
Verify it's connected
bash
```
claude mcp list
```
Sharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes (e.g. recall_context, episode_memory, find). It discovers them automatically.

How to install Exomem in Claude DesktopDesktop app (MCP config)

Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this server

json

{
  "mcpServers": {
    "exomem": {
      "command": "uvx",
      "args": [
        "exomem"
      ]
    }
  }
}

Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.

How to install Exomem in CursorAI-first code editor

Create / edit .cursor/mcp.json in your project

json

{
  "mcpServers": {
    "exomem": {
      "command": "uvx",
      "args": [
        "exomem"
      ]
    }
  }
}

Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.

How to install Exomem in Codex CLIOpenAI coding agent

Add to ~/.codex/config.toml

toml

[mcp_servers.exomem]
command = "uvx"
args = ["exomem"]

Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.

How to install Exomem in WindsurfCodeium's agentic IDE

Edit ~/.codeium/windsurf/mcp_config.json

json

{
  "mcpServers": {
    "exomem": {
      "command": "uvx",
      "args": [
        "exomem"
      ]
    }
  }
}

Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.

How to install Exomem in ClineVS Code autonomous agent

Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.

Add the server

json

{
  "mcpServers": {
    "exomem": {
      "command": "uvx",
      "args": [
        "exomem"
      ]
    }
  }
}

How to install Exomem in VS CodeCopilot / MCP support

Create .vscode/mcp.json

json

{
  "servers": {
    "exomem": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "exomem"
      ]
    }
  }
}

Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.

What tools does Exomem expose? (14)

Taken from the project's README — the server itself was not queried, so check its docs for the exact schemas.

recall_contextCompile durable context for a raw turn, with no query: returns a map or resolves which anchors the turn is about, with a bounded working-memory packet, or abstains.
episode_memoryRecord a bounded recap of what a conversation worked on, decided and left open, so the next session on any client sees it first; inspect an episode's revisions.
findSearch notes, sources, entities, and evidence with type/project/tag filters.
getRead a full page or frontmatter.
addCapture a raw source page.
editPatch an existing compiled page.
replaceSupersede an old conclusion with a new one and preserve the link between them.
preserveStore binary or text evidence append-only.
auditCheck graph and corpus health.
attentionSurface review queues such as stale notes, close-by claims, and unprocessed sources.
overviewBounded, read-only structure report of the vault or a subtree — works outside `Knowledge Base/` and before `init`.
adoptExisting-vault adoption: scan-only by default; can save a manifest, copy selected legacy text files as Sources, or return a compile plan while preserving originals.
record_memoryOne front door for human-owned observed state: inspect, create, query, append, or targeted update a governed Record collection.
plan_memoryOne front door for human-owned intended future state: inspect, create, query, add, update, or triage a Planning collection.

What the code can do

Source analysis currently covers npm packages only. This server ships as a Python package, which needs a different parser.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
Downloads at launch — The package is fetched from its registry each run unless you pin a version.

Last commit today — Actively maintained.
9 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

A · 82

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

Maintenance30%100%
Last commit 0 days ago.
Adoption20%30%
9 stars.
Transparency20%100%
4/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✓ discoverable tool list.
Provenance15%75%
Links to its own repository; package linkage unverified.
Packaging15%100%
Publishes a pinned version (0.149.0).

Documentation

Full README

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.

text

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

Prove it in 30 seconds

bash

uvx exomem demo

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

text

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:

bash

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

Windows — paste into PowerShell:

powershell

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

Excerpt — the full document is on GitHub.

Alternatives to Exomem

Maintain Exomem? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown

[![Exomem on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-artexis10-exomem)](https://mcp-skills-hub.vercel.app/mcps/io-github-artexis10-exomem)

Catalog data refreshed Oct 28, 2026. Something wrong? Report it.