Skip to main content
Glama
jmeyer1980

neurodivergent-memory

by jmeyer1980

Related Servers

Alternatives to neurodivergent-memory

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An advanced MCP server providing RAG-enabled memory through a knowledge graph with vector search capabilities, enabling intelligent information storage, semantic retrieval, and document processing.
      14 npm
      47
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that implements a heavily typed knowledge graph memory system with AI-powered entity and relation extraction, enabling structured knowledge storage and retrieval from unstructured text using predefined or custom ontologies.
      9
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A universal MCP server providing persistent, structured memory through a knowledge graph with graph storage, semantic vector search, and multi-hop traversal for AI agents and IDEs.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Knowledge-graph memory server for MCP-compatible AI tools, providing persistent, connected memory with typed relationships and auto-consolidation.
      34 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Graph-relational memory MCP server for persistent LLM memory, featuring wikilinks, BM25 auto-linking, spreading activation, and synaptic decay across five memory layers.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that gives AI agents and teams persistent, shared memory using a knowledge graph with vector embeddings, automatic consolidation of related facts, and hybrid search.
      3
      -

    TDQS

    A3.7/5.0

    Scored across 18 tools

    Disambiguation4/5

    Tools have largely distinct purposes (CRUD, connections, search, stats, etc.), but some overlap exists between related_to and search_memories in terms of finding related memories; however, descriptions clarify the difference (ID-based vs. query-based). No major ambiguity.

    Naming Consistency5/5

    All tools use a consistent verb_noun pattern in snake_case (e.g., store_memory, list_memories, delete_memory, register_district). Deviations like prepare_memory_city_context still follow the pattern. No mixed conventions.

    Tool Count4/5

    18 tools is on the higher side, but each serves a specific purpose in a complex memory system (CRUD, search, graph traversal, statistics, import, context preparation). The count is justified and does not feel excessive.

    Completeness5/5

    The tool set covers the full lifecycle of memories: create, read (by ID, list, search, related), update, delete. Additionally supports connections, distillation, import, statistics, district registration, and context preparation. No obvious gaps for the stated domain.

    Maintenance

    ActivitySlowing
    ResponsivenessSlow