zipmem-mcp
Related Servers
Alternatives to zipmem-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.MIT
- AlicenseAqualityAmaintenanceLocal-first persistent memory for coding agents and MCP clients. It keeps important project context across sessions and reduces wasted tokens by retrieving only relevant memories instead of replaying unnecessary history.8MIT
- AlicenseBqualityAmaintenanceProvides local-first durable memory and session continuity for AI coding agents over MCP, enabling context across restarts without cloud services or telemetry.1MIT
- AlicenseAqualityCmaintenanceProvides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.8MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.1 npmMIT
- AlicenseBqualityBmaintenanceLocal-first persistent memory layer for MCP agents with hybrid search, file ingestion, and GDPR compliance.201,429 PyPI26Apache 2.0
TDQS
Scored across 3 tools
Each tool has a distinct purpose: zipmem_load_memory initializes context, zipmem_checkpoint stages incremental progress, and zipmem_save_and_compact finalizes and compresses. No overlap or ambiguity.
All tools share the 'zipmem_' prefix and use lowercase with underscores, but 'zipmem_checkpoint' deviates slightly from the verb_noun pattern used by the other two (load_memory, save_and_compact). Still, the naming is clear and predictable.
With only three tools, the set is minimal but perfectly scoped for the server's purpose: loading, checkpointing, and saving memory. Each tool is essential and justified.
The tools cover the complete lifecycle of memory management: initial load, periodic checkpoints, and final save/compact. No gaps are present for the intended domain.