GoodMemory
Related Servers
Alternatives to GoodMemory
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceLocal-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.401MIT
- AlicenseNot gradedqualityFmaintenanceLocal-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.2Apache 2.0
- AlicenseNot gradedqualityCmaintenancePersonal, remotely hosted memory service for Claude, Codex, and other MCP clients that preserves research, project state, and decisions in an auditable revision store with a web UI.9 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to store, search, and retrieve persistent local-first memory — project-specific decisions, preferences, error patterns, and research plus cross-project guidelines — so context survives across sessions without any external API calls. Optionally also exposes a task queue for autonomous execution and GitHub issue resolution in MCP clients such as Claude Code, OpenCode, and Goose.-
- AlicenseNot gradedqualityAmaintenancePersistent, auditable memory for AI agents. Hybrid BM25 + vector recall with 18 MCP tools, adaptive block metadata (A-MEM), intent-aware routing, contradiction detection, and governance workflows. Zero external dependencies. Drop-in memory for Claude Code and any MCP-compatible agent.58 PyPI18Apache 2.0

Loreofficial
AlicenseBqualityCmaintenanceCross-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.4610MIT
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: primary recall, progressive recall, and diagnostics are separated. However, goodmemory_search_index and goodmemory_get_context both serve recall and could be confused, though the descriptions clarify their different use cases.
All tools share the goodmemory_ prefix and use snake_case, with mostly verb_noun patterns (get_context, inspect_memory, trace_recall, get_records, read_artifacts). Two tools (timeline, stats) are noun-only, creating slight inconsistency, but the overall pattern is predictable.
At 8 tools, the count is well-scoped for a memory system. Each tool has a distinct role, and the count feels appropriate without being excessive or thin.
The tool set focuses heavily on reading and diagnostics but lacks a core writing tool (goodmemory_remember is referenced in descriptions but not exposed). No update, delete, or list-all capability is present, which is a significant gap for a memory system.