Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Mnema

by Zimac-AIversion 0.2.0i★ –iRuns on your computer
Registry nameai.zimac/mnema

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory
  • You need to fill in: MNEMA_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: MNEMA_DATA_DIR, MNEMA_URL, MNEMA_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Download the maker’s .mcpb file

The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.

Run this in your terminal

Fill in the empty values before running it.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • MNEMA_DATA_DIR env
    Where the store lives (default ~/.mnema).
  • MNEMA_URL env
    Target store URL. Loopback (default http://127.0.0.1:7077) auto-starts a local daemon; a remote URL makes the server a pure authenticated bridge.
  • MNEMA_TOKEN secret env
    Bearer credential when MNEMA_URL points at a token-protected remote store.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain zimac.ai (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7270 servers in this category
  • Published to the registry more recently than 21% of the other 7270 servers in this category
  • Basic checks equal to or better than 100% of the other 7270 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Mnema safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MNEMA_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Mnema

Local-first, formally verified memory for AI agents — one shared store, every client, over [MCP](https://modelcontextprotocol.io).

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.

  • Verified engine. The embedded engram database is formally specified and machine-checked (property catalog discharged by 250+ tests, an exhaustive CRDT conformance model checker, Kani proofs, and a TLA⁺ model). Every released binary passed that gate on its exact commit.
  • Local-first. An open, append-only segment format in ~/.mnema. No cloud, no account.
  • One store, every client. Claude Code, Claude Desktop, Cursor, your scripts, and your CI all talk to the same memory. Recall is lexical + graph spreading-activation (plus optional semantic embeddings), with an honest confidence band on every answer.

This repository hosts the public release bundles (.mcpb) and prebuilt

binaries. The product, docs, and downloads live at [mnema.zimac.ai](https://mnema.zimac.ai).

Install

From the MCP Registry (recommended)

Mnema is published to the official MCP Registry as `ai.zimac/mnema`. Any registry-aware client can install it by name; it pulls the platform .mcpb bundle from this repo's releases and verifies its fileSha256.

.mcpb bundle (manual)

Grab the bundle for your platform from the latest release and open it with an MCP-bundle-aware client (e.g. Claude Desktop → Extensions):

PlatformAsset
macOS (universal)mnema- -macos-universal.mcpb
Linux (x86_64)mnema- -linux-x86_64.mcpb

A .mcpb is a ZIP of a manifest.json, the mnema binary, and this README. Each is dry-run verified (the bundled binary completes an MCP initialize handshake) before release.

Headless binary (curl | sh)

For agents, scripts, and CI — installs the standalone mnema binary:

curl -fsSL https://mnema.zimac.ai/install.sh | sh

(macOS universal + Linux x86_64 prebuilt; anything else builds from source. The macOS GUI app is a separate download at mnema.zimac.ai.)

Give your agents memory

claude mcp add mnema -- mnema mcp

That's the whole setup: mnema mcp auto-starts the shared local store if it isn't running, and the session gets four tools — consult (search before you act), learn (record a durable fact), related (graph neighbours), list (browse). Any MCP client works; the generic config is:

{ "mcpServers": { "mnema": { "command": "mnema", "args": ["mcp"] } } }
Point it at a shared / team store

The same binary bridges to a remote Mnema (a token-protected mnema serve or a hosted learnings pod) instead of the local one:

MNEMA_URL=https://memory.example.com MNEMA_TOKEN=<secret> mnema mcp

With a non-loopback URL nothing is auto-started — it's a pure authenticated bridge.

Configuration

EnvDefaultWhat
MNEMA_DATA_DIR~/.mnemaWhere the store lives
MNEMA_URLhttp://127.0.0.1:7077Store the CLI/MCP bridge targets
MNEMA_TOKEN—Bearer credential for a remote store

Links

  • Product & downloads: https://mnema.zimac.ai
  • Registry entry: ai.zimac/mnema on https://registry.modelcontextprotocol.io
  • Releases (`.mcpb` + binaries): https://github.com/Zimac-AI/mnema/releases

Mnema is a Zimac project.

Ask PopNx