Skip to main content
Glama
Neboy72
by Neboy72

Related Servers

Alternatives to Nexus Memory

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory and handoff intelligence layer for MCP agents. Most memory servers retrieve text — Memory Nexus compounds operational context, learning from usage and progressively synthesizing observations into higher-order intelligence across sessions and tools.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted memory server that gives AI agents a shared, persistent second brain, enabling verbatim storage, hybrid semantic/keyword retrieval, and a synthesized wiki layer through MCP tools.
      MIT
    • 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
    • F
      license
      A
      quality
      A
      maintenance
      Shared fleet memory for AI agents — what one agent learns, the whole fleet knows. Nightly self-correction: stale facts rewritten in place, duplicates merged. Recall pushed into every prompt in supported coding agents. Self-hosted.
      8
      11
      2
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Gives AI agents persistent memory with semantic search, automatic extraction, and memory decay, accessible via MCP protocol.
      7 npm
      MIT
    • 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

    TDQS

    A3.5/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools are clearly distinct (remember/recall/forget/update, subscribe/unsubscribe/list_subscriptions, backup/restore, guardrail_check/guardrail_override, graph_traverse/find_entities/get_subgraph/get_related, cost_routing_stats/cost_routing_explain). The only potential confusion is check_update vs do_update (checking for an update vs performing the update), but their descriptions make the distinction clear.

    Naming Consistency3/5

    The naming is mostly verb_noun (check_update, remember, recall, forget, update, subscribe, unsubscribe, list_subscriptions, backup, restore, find_entities, get_subgraph, get_related), but there are inconsistencies: 'do_update' is an odd variant of 'update', and 'fact_history' and 'health' are noun-only rather than verb_noun. The mixed conventions are still readable and mostly predictable.

    Tool Count4/5

    21 tools is on the higher end but appropriate for the server's broad scope: memory CRUD, webhooks, backup/restore, guardrails, knowledge graph, cost routing, and system maintenance. Each tool serves a distinct function, though the count is slightly heavy and could feel overwhelming.

    Completeness4/5

    The memory lifecycle is well covered (remember, recall, update, forget, fact_history), and the server includes thoughtful extras like backup/restore, guardrails, and webhooks. Minor gaps exist: there's no explicit 'list all memories' tool, and the guardrail system has check/override but no way to create or manage protection rules directly.

    Maintenance

    ActivityActive
    ResponsivenessResponsive