Skip to main content
Glama
phillipclapham

anneal-memory

by phillipclapham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to anneal-memory

  • Amber by ambermem

    Amberofficial

    ambermem
    A
    license
    A
    quality
    B
    maintenance
    Gives your AI persistent memory across conversations. Stores facts automatically, finds them by meaning using hybrid search with query expansion, and organizes everything into topics without manual tagging.
    18
    1
    MIT

Related Servers

  • mnemosis-mcp

    liyexiaoyi
    A
    license
    C
    quality
    A
    maintenance
    Provides AI agents with a human-inspired memory layer via MCP, enabling episodic and semantic memory recall, forgetting curves, consolidation, and contradiction detection. It integrates with MCP clients to offer local-first, dependency-free memory management.
    98
    1
    MIT

  • mnemo

    krat214
    A
    license
    Not graded
    quality
    D
    maintenance
    Persistent memory MCP server for AI agents, featuring a visual interface to browse, search, edit, and delete memory. It provides tools for capturing episodes, recalling, consolidating, crystallizing traits, and forgetting, with local SQLite storage and optional authenticated web UI.
    MIT

  • MemVault

    dreamor
    A
    license
    A
    quality
    A
    maintenance
    A self-hosted MCP memory server that gives every MCP-compatible agent a shared, persistent memory layer, so preferences, project conventions, and past decisions carry across sessions and across different agents and vendors. It combines hybrid keyword-plus-vector retrieval with automatic context injection, zero-config sync, and selective injection of memories by agent and priority.
    20
    2
    MIT

  • GroundMemory

    huss-mo
    A
    license
    Not graded
    quality
    A
    maintenance
    An MCP-native, local-first memory server that gives AI agents persistent, structured memory across sessions and tools, enabling them to maintain identity and context without reconfiguration.
    3
    MIT
Deploy Server
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.7/5.0

Scored across 17 tools

Disambiguation4/5

Tools are mostly distinct and the descriptions work hard to delineate the tricky pairs (recall vs crystal_recall, crystal_index vs crystal_recall, spore_list vs spore_surface, spore_touch vs spore_update). The residual ambiguity is between the two memory layers (episodic recall/record vs crystallized recall) and the wrap lifecycle tools (prepare_wrap/save_continuity/wrap_cancel), where an agent could still mispick without careful reading.

Naming Consistency3/5

Everything is snake_case, which is good, but verb/noun ordering is mixed: verb_noun (prepare_wrap, save_continuity, delete_episode, record, recall) alongside noun_verb (wrap_cancel, spore_add, spore_get, crystal_index). The domain-prefix convention (spore_*, crystal_*) is coherent internally, but the core memory tools have no prefix, so the scheme is readable rather than predictable.

Tool Count4/5

17 tools is on the heavy side but justified by a genuinely dual-layer domain (episodic memory + wrap lifecycle + crystallized tier + a full spore subsystem). Each tool earns its place; no obvious redundancy beyond the spore surface/list overlap.

Completeness4/5

Broad lifecycle coverage: episode record/recall/delete, wrap prepare/save/cancel, crystal index/recall, and full spore CRUD plus descend/ascend/surface resolution. Gaps are mostly deliberate (no update_episode, corrections handled via new records; no direct tool to author or manage crystallized/durable patterns outside the continuity file).

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources