Skip to main content
Glama

Related Servers

Alternatives to Mirsad

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Gives MCP-compatible AI assistants one shared, append-only memory stored as a graph, so facts persist across tools and sessions with their full reasoning chain. Enables finding disagreements between tools, resolving them by recording a winner, and seeing which downstream decisions become stale.
      9
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables self-hosted, provenance-aware shared memory with scoped access, attributed observations, correction history, disagreement tracking, and durable idempotent writes for humans and AI agents via REST and MCP.
      1
      Apache 2.0

    TDQS

    B3.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (remember_fact vs current_fact vs timeline vs record_decision), and the descriptions clarify the temporal/provenance differences. The main soft spot is the read side: recall, why, timeline, and current_fact all retrieve stored knowledge and could be confused by an agent deciding which to call, though 'why' and 'recall' are reasonably differentiated by their descriptions.

    Naming Consistency3/5

    All names are snake_case or single lowercase words, so the surface is readable, but the convention is mixed: some are verb_noun (remember_fact, record_decision, add_alias, resolve_conflict), some are bare nouns (version_info, current_fact, timeline, memory_stats), and some are bare verbs (why, recall). There is no single predictable pattern an agent can rely on.

    Tool Count5/5

    Twelve tools is well within a healthy range and each one maps to a distinct part of the memory/decision lifecycle: writes, reads, conflict handling, aliasing, and diagnostics. Nothing feels like padding, and no obvious operation is duplicated by another tool.

    Completeness4/5

    The surface covers a full lifecycle for facts (write, current, history), decisions (record, outcome, why), and conflicts (list, resolve), plus aliases and stats. Minor gaps remain: there is no way to list or inspect entities, no explicit forget/delete or entity-merge operation, and no bulk/query-by-subject listing, though the design intentionally closes rather than deletes facts.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues