theseusmem-mcp
Related Servers
Alternatives to theseusmem-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes a local SQLite-backed long-term memory to AI agents as MCP tools, letting them add conversations and documents, record dated facts with provenance, search and assemble context, and edit, inspect, or forget what was stored. It runs with your own embedding and LLM keys, so memories stay readable, exportable, and portable as plain markdown.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.28 npmMIT
- AlicenseAqualityBmaintenanceProvides AI coding tools with one local SQLite memory and rules store they can read over MCP, REST or the CLI, so facts, sessions and goals persist across sessions and shared rules are written into each tool's own instruction file. Runs entirely on your machine with no account, telemetry or network calls by default.414438 npm10Apache 2.0
- AlicenseNot gradedqualityDmaintenanceLocal, cross-agent memory for AI coding agents using a single SQLite file, enabling persistent sessions and durable facts shared across multiple MCP-compatible tools.10 npmMIT
- AlicenseBqualityBmaintenanceLocal long-term memory service for AI agents via MCP, using SQLite with tools for memory CRUD, semantic search, time-based facts, and graph capabilities.2720 npm1MIT
- AlicenseBqualityCmaintenanceEnables multiple AI agents and harnesses to share one local SQLite-backed memory store over standard MCP, so decisions, preferences, and past pitfalls carry across sessions instead of being re-explained. Runs fully offline with local Chinese-capable search, zero dependencies, and no accounts, API keys, or telemetry.11MIT
TDQS
Scored across 9 tools
Most tools target distinct resources: facts, episodes, entities, timelines, reference files, and stats. However, search_facts, list_facts, and recall_entity all return facts and could be confused without careful reading; descriptions partially clarify the boundaries.
Nearly all tools use a consistent snake_case verb_noun pattern (search_facts, get_fact, remember_fact, etc.). memory_stats is the main deviation, using a noun phrase instead of a verb, but overall the naming is predictable.
Nine tools is well-scoped for a memory server, covering search, retrieval, persistence, entity recall, timelines, references, and stats. Each tool appears to earn its place without obvious redundancy.
The server covers creation and rich read paths for facts, episodes, and references, but lacks explicit update, delete, or forget operations. For a long-term memory store, the absence of deletion/forgetting and episode write operations is a notable lifecycle gap.