Skip to main content
Glama
Sign In
Nexus Memory

Nexus Memory

by Neboy72
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Nexus Memory

No user-submitted related servers found.

    Related Servers

    • Memory Nexus

      Memory Nexusofficial

      MemoryNexus
      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

    • 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

    • Mnemon

      coopers98
      A
      license
      Not graded
      quality
      A
      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

    • knowledge-base-server

      Ebba57
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to share a persistent, self-improving memory by ingesting, classifying, synthesizing, and retrieving knowledge from sources like Obsidian vaults, code, and transcripts through MCP and REST APIs. Provides token-optimized, tiered retrieval with full-text and semantic search so every agent session builds on accumulated context.
      5 npm
      MIT

    • knowledge-base-server

      hugonowak0237
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to share persistent memory by capturing, classifying, synthesizing, and retrieving knowledge from sources like Obsidian, code, and transcripts via MCP and REST APIs. Provides token-optimized search, three-tier memory, and self-learning capture of sessions and fixes so multiple agents can build on prior context.
      5 npm
      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

    B3.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    Core memory operations (remember/recall/update/forget) are clearly distinct, and the guardrail, cost-routing, and webhook clusters are well separated. The knowledge-graph tools (find_entities, get_related, graph_traverse, get_subgraph) overlap somewhat since all query related facts, though hop-depth and output shape differentiate them.

    Naming Consistency2/5

    Three conventions coexist: bare verbs (remember, recall, forget, restore, backup, health), verb_noun (find_entities, get_related, graph_traverse, list_subscriptions), and noun_verb (guardrail_check, cost_routing_stats, fact_history). All are snake_case so it stays readable, but the mixed verb styles reduce predictability.

    Tool Count4/5

    19 tools spans several distinct subsystems—memory CRUD, knowledge graph, guardrails, cost routing, and webhooks—so each earns its place. It runs slightly heavy and could consolidate the KG and cost-routing pairs, but it's reasonable for the breadth of scope.

    Completeness4/5

    Strong lifecycle coverage: full memory CRUD (remember/recall/update/forget), backup+restore, fact history/supersession, and complete webhook subscribe/unsubscribe/list. Minor gaps like batch operations or listing all memories remain, but core workflows are well covered.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources