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
    B
    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

  • GroundMemory

    huss-mo
    A
    license
    Not graded
    quality
    C
    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
  • dakera-mcp by Dakera-AI

    dakera-mcpofficial

    Dakera-AI
    F
    license
    A
    quality
    B
    maintenance
    Self-hosted MCP-native agent memory server. Gives AI agents persistent, decay-weighted memory via 83 MCP tools — no cloud, full control. RocksDB+HNSW backend. Works with Claude Code, Cursor, and any MCP-compatible agent.
    14
    8
    -
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

A3.9/5.0

Scored across 16 tools

Disambiguation5/5

Each tool has a distinct purpose: crystal_index and crystal_recall handle crystallized patterns; delete_episode, recall, record, save_continuity handle episodic memory; spore_* tools handle prospective memory with clear operations; status provides health metrics. No two tools overlap in functionality.

Naming Consistency4/5

Most tools follow a verb_noun or noun_verb pattern (e.g., delete_episode, spore_add). The spore family is consistently prefixed with 'spore_'. However, three tools (recall, record, status) are single verbs without a noun, breaking the pattern slightly.

Tool Count4/5

With 16 tools, the count is slightly above the ideal 3-15 range but still reasonable for a feature-rich memory server. Each tool serves a necessary function without redundancy.

Completeness5/5

The tool surface covers the full lifecycle of memory: recording, recalling, deleting, compressing (wrap/save), crystallizing, spore management (add, resolve, update, touch, list, surface), and health monitoring. There are no obvious gaps.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources