Exomem MCP Server

Local Markdown/Obsidian knowledge substrate for MCP agents with governed memory and hybrid search. Exposed over MCP by the exomem mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

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

• Searches the vault you already own. — Markdown stays in place; exomem does
• Adopts messy vaults safely. — adopt starts with a read-only report and
• Retrieves across text and media. — Markdown, PDFs, Office docs, images,
• Keeps sources separate from conclusions. — Raw captures, compiled notes,
• Surfaces review work. — Audit and attention queues can show unprocessed
• Measures, never judges. — The server does deterministic work: search,

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Its toolset

Everything the assistant can do here goes through one of these:

• find — Search notes, sources, entities, and evidence with type/project/tag filters
• get — Read a full page or frontmatter
• add — Capture a raw source page
• note — Create compiled notes: research note, insight, failure, pattern, experiment, or production log
• edit — Patch an existing compiled page
• replace — Supersede an old conclusion with a new one and preserve the link between them
• preserve — Store binary or text evidence append-only
• audit — Check graph and corpus health
• attention — Surface review queues such as stale notes, close-by claims, and unprocessed sources
• overview — Bounded, read-only structure report of the vault or a subtree — works outside Knowledge Base/ and before init
• adopt — Existing-vault adoption: scan-only by default; can save a manifest, copy selected legacy text files as Sources, or return a compile plan while

Configuration

You will need 3 environment variables: EXOMEM_VAULT_PATH, EXOMEM_BASE_URL, EXOMEM_REST_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Exomem.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the exomem mcp server does with a few real requests.

When to reach for it

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Exomem's toolset — find, get, add and 8 more — is a fair guide to whether it matches your workflow. It is maintained by Artexis10; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.