Skip to main content
Glama
server-noonien

server-noonien

Official

Related Servers

Alternatives to server-noonien

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to maintain a shared, serverless, conflict-free knowledge graph across multiple machines by syncing append-only per-node shards. It provides drop-in compatibility with the official MCP memory tools while converging automatically without merge conflicts.
      Mozilla Public 2.0
    • 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
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store, search, and resolve shared memories with full provenance, conflict detection, and an audit trail across MCP-compatible clients.
      -
    • 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
    • A
      license
      Not graded
      quality
      A
      maintenance
      Semantic memory for AI agents — local-first MCP server with hybrid search, knowledge graph, contradiction detection, and plan-then-commit consolidation.
      403 npm
      4
      AGPL 3.0

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    Each tool pairs a distinct resource (entity, observation, relation) with an action, and the update/merge tools clearly differentiate in-place edits from merges. The main soft spot is the read trio (read_graph, open_nodes, search_nodes), which are all retrieval operations and could occasionally be confused, though descriptions distinguish whole-graph paging, exact-name lookup, and query search.

    Naming Consistency5/5

    Every tool follows a clean verb_noun pattern (create_entities, delete_observations, update_relations, merge_entities, read_graph, search_nodes). Conventions are uniform across all 14 tools with no mixing of styles.

    Tool Count5/5

    14 tools is well within the sweet spot and each earns its place by covering a distinct resource-action pair across entities, observations, and relations plus graph-level reads. Nothing feels redundant or padded.

    Completeness5/5

    Full lifecycle coverage exists for all three resource types (create, update, delete on entities/observations/relations), supplemented by merge, rename-via-update, search, paged read, and conflict inspection. No obvious dead ends for a knowledge-graph workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues