Skip to main content
Glama
ahmetakyurt

zipmem-mcp

by ahmetakyurt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to zipmem-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-light-memory

      PeterPirog
      A
      license
      Not graded
      quality
      A
      maintenance
      Local-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.
      MIT

    • whitemagic

      lbailey94
      A
      license
      B
      quality
      A
      maintenance
      Provides local-first durable memory and session continuity for AI coding agents over MCP, enabling context across restarts without cloud services or telemetry.
      2
      1
      MIT

    • marketnow-memory

      alicelabs-llc
      A
      license
      A
      quality
      C
      maintenance
      Provides 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.
      8
      MIT

    • Cortex

      ryanfrigo
      A
      license
      Not graded
      quality
      D
      maintenance
      Local-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.
      3 npm
      MIT

    • M3 Memory

      skynetcmd
      A
      license
      B
      quality
      C
      maintenance
      Local-first persistent memory layer for MCP agents with hybrid search, file ingestion, and GDPR compliance.
      20
      1,662 PyPI
      25
      Apache 2.0

    • mcp-chest-memory

      siosig
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent, local-first memory for coding agents over MCP, enabling automatic recall and recording of past work, failures, and decisions to reduce repetition and token usage.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources