Mnemosyne OS
Related Servers
Alternatives to Mnemosyne OS
- AlicenseNot gradedqualityAmaintenanceDescription: Persistent local memory for Claude, Cursor and Codex. 13 MCP tools, SQLite + FTS5 + Knowledge Graph. No cloud, no API keys. One command: npx @studiomeyer/local-memory-mcp.69 npm13MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first, file-based memory layer for AI agents — one shared Markdown vault across Claude, Codex, Gemini, Cursor and any MCP client. Provides read/write memory tools with an audit trail, per-agent trust levels, and Git sync; no cloud and no lock-in.2MIT
- AlicenseNot gradedqualityAmaintenanceLocal-first, source-grounded memory for AI agents, with citations, bitemporal history, review-gated corrections, and MCP tools for search and recall.3Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides a local-first, source-cited memory layer for AI agents, with MCP tools to search, read, explain sources, and propose/apply memory updates.23 npm6Apache 2.0
- AlicenseNot gradedqualityAmaintenanceLocal memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.3MIT
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides AI agents with persistent, local cross-session shared memory by combining vector semantic retrieval with knowledge graph relationships, and supports short/long-term memory management and local backups.-
- AlicenseBqualityAmaintenanceEnables local AI coding agents and web agents to store, retrieve, and search memories using hybrid semantic, lexical, and knowledge-graph ranking with cognitive decay modeling in a local on-device database.15MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to automatically capture durable knowledge and retrieve only relevant, token-bounded context from a secure local-first long-term memory, with support for progressive disclosure, snapshots, health diagnostics, and background tasks.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.179MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents with long-term memory and retrieval-augmented generation (RAG) capabilities, allowing them to recall past conversations, search local files, and learn user preferences.MIT

Loreofficial
AlicenseBqualityAmaintenanceCross-agent memory server: hybrid (vector + full-text + knowledge-graph) recall, per-user private/shared visibility, write-side secret/PII redaction, and as-of-date bi-temporal fact queries. Auto-injection hooks for Claude Code / Cursor / Codex; self-hostable on PostgreSQL or SQLite.468MIT
TDQS
Scored across 25 tools
Most tools map to a distinct domain and action, and the long descriptions carefully separate mnemosyne_ask from mnemosyne_query and pheme_watch from pheme_radar. The main risk is mnemosyne_todo_list vs mnemosyne_todo_lists, whose singular/plural names point at two different operations (reading tasks vs managing list shapes), so one pair could still trip up an agent.
All tools share the mnemosyne_ prefix, but the action-placement pattern is mixed: query/ask/ingest are bare verbs, get_position/update_position are verb_noun, while todo_add/agenda_update are noun_verb. This is readable but not predictable, and mnemosyne_todo_list versus mnemosyne_todo_lists is an especially confusing near pair.
25 tools is at the heavy end and spans many subsystems—memory, resonances, pheme, todo, agenda, cockpit, and agent monitoring—so the count feels more like an OS surface than a focused MCP. Each tool is individually justified, but the overall set is borderline for agent selection and would benefit from consolidation or namespacing.
The todo and agenda domains have full add/read/update/remove coverage, and agent-collision checks fill real gaps. However, the core memory domain only offers ingest plus query/ask, with no explicit update or delete/forget path, which is a notable lifecycle gap even if permanence is intentional.