Mnema MCP Server

Local-first, formally verified memory for AI agents: consult/learn/related/list over MCP.

Remote serverstreamable-http

What is the Mnema MCP server?

If you already use Mnema, the mnema mcp server is the piece that lets your assistant work with it directly. Local-first, formally verified memory for AI agents: consult/learn/related/list over MCP.

What the server does

Your agents rent their intelligence from a lab; their memory should be yours. Mnema is a single, durable store of what your agents have learned — consult it before you act, learn a durable fact, walk the related graph, list what's recent. Data lives in ~/.mnema on your machine and nothing leaves it unless you point it somewhere.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Local — first.** An open, append-only segment format in ~/.mnema. No cloud,
  • Platform — Asset
  • Env — Default
  • MNEMA_DATA_DIR — ~/.mnema
  • MNEMA_URLhttp://127.0.0.1:7077
  • MNEMA_TOKEN — —

Credentials and setup notes

Configuration is passed through the environment: MNEMA_URL, MNEMA_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Mnema's toolset — Local, Platform, Env and 3 more — is a fair guide to whether it matches your workflow. It is maintained by ai.zimac; 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.

Worth knowing first

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Localfirst.** An open, append-only segment format in ~/.mnema. No cloud,
PlatformAsset
EnvDefault
MNEMA_DATA_DIR~/.mnema
MNEMA_URLhttp://127.0.0.1:7077
MNEMA_TOKEN

Configuration

VariableDescriptionRequired
MNEMA_URLEndpoint or connection string the server talks to.Yes
MNEMA_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Mnema to Local.
  • Use Mnema to Platform.
  • Use Mnema to Env.

Frequently asked questions

It connects Mnema to MCP-compatible AI assistants such as Claude and Cursor, exposing 6 tools (Local, Platform, Env, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mnema directly.