Skip to main content
Glama
wazionapps

NEXO Brain

by wazionapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to NEXO Brain

No user-submitted related servers found.

    Related Servers

    • emms-mcp

      supermaxlol
      F
      license
      Not graded
      quality
      F
      maintenance
      Cognitive memory system for AI agents with 129 MCP tools. Persistent 6-tier hierarchical memory (working→short-term→long-term→semantic), Ebbinghaus forgetting curves, dream consolidation, hybrid retrieval (BM25+RRF), goal tracking, emotional recall, knowledge graphs, and a 26-job consciousness daemon. Works with Claude Code, Cursor, and any MCP client.
      -

    • Logica Mind

      Rovemark
      A
      license
      Not graded
      quality
      D
      maintenance
      Long-term memory for AI agents over MCP — episodic + semantic memory, a temporal knowledge graph, and a dialectic user model, exposed as 32 tools (recall, remember, context, graph, dreaming, peers). Zero dependencies, runs fully offline; leads the LoCoMo benchmark at ~35x fewer LLM calls.
      2
      Apache 2.0

    • mind-mem

      star-ga
      A
      license
      Not graded
      quality
      A
      maintenance
      Persistent, auditable memory for AI agents. Hybrid BM25 + vector recall with 18 MCP tools, adaptive block metadata (A-MEM), intent-aware routing, contradiction detection, and governance workflows. Zero external dependencies. Drop-in memory for Claude Code and any MCP-compatible agent.
      17
      Apache 2.0
    • MnemoQ by Mnemoq

      MnemoQofficial

      Mnemoq
      A
      license
      A
      quality
      B
      maintenance
      A local-first memory engine for AI agents with MCP-native, graph-linked, spaced repetition. It enables agents to log, retrieve, and manage learnings via CLI or MCP server.
      8
      AGPL 3.0
    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

    C2.9/5.0

    Scored across 170 tools

    Disambiguation4/5

    Every tool has a distinct resource+verb (get/update/delete/list by entity), but with 170 overlapping entities there is inevitably semantic overlap (e.g. multiple 'explain' or 'surface' tools); still, each appears to target a unique function.

    Naming Consistency5/5

    Uniform nexo_ prefix with snake_case verbs and nouns is extremely consistent across all 170 tools; pattern is predictable.

    Tool Count1/5

    170 tools is an extreme surface area. Even intentional 'mission control' servers rarely need this many; it overwhelms context and decision-making.

    Completeness4/5

    For the apparent domain (multi-session memory, checkpoints, events, sessions, products, external APIs), lifecycle coverage is thorough — create/update/close/query pairs exist across the board. Some areas (e.g., plugin removal edge cases) may still have gaps, hence not 5.

    Maintenance

    ActivityStale
    ResponsivenessResponsive

    Resources