Mnemex MCP Server

Most knowledge and memory work still happens through a UI a human drives. Mnemex MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server providing human-like memory dynamics for AI assistants. Memories naturally fade over time unless reinforced through use, mimicking the [Ebbinghaus forgetting.

The short version

• ❌ "Delete after 7 days" (doesn't care if you used it 100 times)
• ❌ "Keep last 100 items" (throws away important stuff just because it's old)
• ✅ Combines recency (when?), frequency (how often?), and importance (how critical?)
• ✅ Memories fade naturally like human memory
• ✅ Frequently used memories stick around longer
• ✅ You can mark critical things to "never forget"

The tools it exposes

The server publishes 14 tools. What each one is for:

• save_memory — Save new memory with tags, entities (auto-enrichment in v0.6.0+)
• search_memory — Search with filters and scoring (includes review candidates)
• search_unified — Unified search across STM + LTM
• touch_memory — Reinforce memory (boost strength)
• observe_memory_usage — Record memory usage for natural spaced repetition
• analyze_message — ✨ NEW v0.6.0 - Detect memory-worthy content, suggest entities/strength
• analyze_for_recall — ✨ NEW v0.6.0 - Detect recall intent, suggest search queries
• promote_memory — Move to long-term storage
• cluster_memories — Find similar memories
• consolidate_memories — Merge similar memories (algorithmic)
• read_graph — Get entire knowledge graph
• open_memories — Retrieve specific memories

What it needs from you

Configuration is passed through the environment: PYTHONPATH, CORTEXGRAPH_STORAGE_PATH, LTM_VAULT_PATH. 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.

Getting it running

The server ships on PyPI as mnemex, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

How it compares

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mnemex's toolset — save_memory, search_memory, search_unified and 11 more — is a fair guide to whether it matches your workflow. It is maintained by simplemindedbot; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mnemex.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.