Memoria MCP
Related Servers
Alternatives to Memoria MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent project-scoped and cross-project memory during sessions, using local semantic search to surface relevant decisions, preferences, error patterns, and guidelines across sessions. It also optionally exposes an autonomous task queue that draws on that same stored context.-
- FlicenseNot gradedqualityAmaintenanceGives AI coding agents persistent, local-first memory so they can store, semantically search, and recall decisions, preferences, error patterns, and cross-project guidelines directly during a session. It also optionally queues tasks for autonomous execution against that same memory.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to store and retrieve persistent project and cross-project memories via semantic search, so decisions, preferences, error patterns, and guidelines survive across sessions. Optionally supports autonomous task execution built on the same local-first knowledge store.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to share a persistent, self-improving memory by ingesting sources like Obsidian vaults, code, transcripts, and session captures, then serving them back through search, classification, synthesis, and token-optimized context briefings. It lets multiple agents read and write the same knowledge base, so each session builds on the last without copy-pasting context.10 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent, local-first memory across sessions and projects, with semantic search, global guidelines, and optional autonomous task execution.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent project and cross-project memory through semantic search, storing decisions, preferences, error patterns, and guidelines across sessions. Optionally exposes a task-queue server for autonomous task execution.-
TDQS
Scored across 14 tools
Most tools map to distinct actions, but a few pairs sit close together: encode_memory vs batch_encode, forget_memory vs delete_by_context, and health vs stats (both report tier/storage metrics). Descriptions do enough to separate them, so misselection risk is moderate rather than severe.
The dominant pattern is snake_case verb_noun (encode_memory, recall_memories, delete_by_context, list_agent_wings, handoff_to_agent), but several tools break it with bare verbs or nouns: feedback, consolidate, health, stats. Conventions are mixed, yet each name remains readable and self-explanatory.
14 tools is well within a healthy range and each one covers a real capability: memory lifecycle, context assembly, maintenance, observability, code lookup, and multi-agent handoff. Nothing feels padded or redundant.
The memory lifecycle is largely covered (encode/batch, recall, build_context, delete, feedback, consolidate), plus code-intelligence and agent handoff extras. Minor gaps exist: no get_memory by ID, no edit/update of an existing memory's content or context metadata, and no browsing/listing of memories by namespace.