mneme Record MCP Server

Every session starts from zero. You re-explain the same architecture, the same constraints, the same decision you already settled yesterday, and the tools that promise to fix it mostly store your conversation history in opaque SQLite blobs and call an LLM every time you finish a session. The record of your own work ends up somewhere you cannot read, cannot grep, and cannot take with you. Its README documents 9 tools, including mneme_search, mneme_recall, mneme_write.

People connecting productivity tools to Claude, Cursor, VS Code, or another MCP client. The project is written in Python.

VERIFIED ACTIVE

LAST COMMIT 2026-08-14 · ★ 2 · #57 OF 139 MAINTAINED PRODUCTIVITY · VERIFIED 2026-08-25

Apache-2.0 · Python servers · how we verify → /methodology

01 · Install mneme Record

Claude Code

claude mcp add onourimpram-mneme -- npx -y mneme-mcp-server

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "onourimpram-mneme": {
      "command": "npx",
      "args": [
        "-y",
        "mneme-mcp-server"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license Apache-2.0 - declared in the repository

npm package mneme-mcp-server - unscoped; check the name against the project README before installing

registry namespace io.github.OnourImpram is GitHub-verified and matches the repo owner

03 · What mneme Record can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

An agent gets 9 documented tools, including mneme_search, mneme_recall, mneme_write, mneme_summarize, mneme_timeline.

The 9 tools it gives your agent

Extracted from the project's README - what mneme Record lets an agent do.

mneme_search
- FTS5 BM25 retrieval over the vault with Turkish casefold normalization, plus date, memory-type, and scope filters. Returns ranked hits and EvidenceCards carryin
mneme_recall
- Retrieves indexed documents by session identifier, date range, and scope. Returns paths, titles, modification times, memory types, and optionally the full markd
mneme_write
- Atomically appends or replaces a markdown section in a vault file. Enforces vault path containment and redacts private spans before storage.
mneme_summarize
- Groups FTS5 matches for a topic by vault directory within optional date and scope filters. Graphiti enrichment appears only when that optional local graph integ
mneme_timeline
- Returns scope-restricted references for a subject in chronological order. Graphiti facts and bi-temporal filtering appear only when the optional local graph int
mneme_prime
- Builds a token-budgeted preflight context bundle from recent sessions and topic-relevant matches. A caller session identifier enables per-session injection dedu
mneme_propose
- Queues a redacted memory-edit proposal for the policy drain. The server does not apply the edit directly; durable categories always require human approval.
mneme_checkpoint_list
- Lists recent Context Continuity Engine checkpoints from the active scope, newest first. Missing checkpoint state returns an empty list.
mneme_working_set_load
- Loads salience-ranked working-set items from a Context Continuity Engine checkpoint. Unknown and out-of-scope anchors return the same neutral not-found result.

Latest releases

v3.6.3 · 2026-07-27

Patch seventeen advisories the lockfile was pinning open · Bound the audit lock retry, and stop it spinning without a sleep · 3.6.3

v3.6.2 · 2026-07-26

This release publishes two things that were finished but never shipped, because the 3.6.1 tag was cut before they landed. · The display name · The MCP Registry returns four distinct things for the word "mneme": · this…

v3.6.1 · 2026-07-25

publish the MCP server under the current GitHub namespace (3.6.1)

04 · Who maintains mneme Record

mneme Record is maintained by onourimpram. It's the only MCP server we track from this author; the repo dates to May 2026.

05 · Facts

category
productivity - ranked #57 of 139 actively-maintained productivity servers as of 2026-08-25.
release cadence
10+ releases in the last 90 days (latest 2026-07-27)
registry
io.github.OnourImpram/mneme (active, first published 2026-07-25 · 3 versions)
packages
npm:mneme-mcp-server

06 · mneme Record FAQ

Is mneme Record still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-14 and it shipped 10+ releases in the last 90 days. We re-verify nightly.

What can mneme Record do?

An agent gets 9 documented tools, including mneme_search, mneme_recall, mneme_write, mneme_summarize, mneme_timeline.

How do I install mneme Record?

Run `npx -y mneme-mcp-server`. You can also paste the ready-made client config above.

Does mneme Record run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to mneme Record