Skip to main content
Glama

Related Servers

Alternatives to ai-context-nas

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted service providing unified memory search and write operations across file-based memory, vector embeddings, and the Graphiti temporal knowledge graph, accessible via HTTP API or MCP stdio transport.
      3
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides self-hosted, versioned project memory with full-text and vector search, enabling search, retrieval, upsertion, and history management of project entries via MCP tools.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves plain-text notes that an Obsidian user has explicitly published for AI over streamable HTTP, with full-text and embedding-based search. MCP clients can read and search those notes and queue suggested edits that the user's own client applies only if the AI rules allow it.
      GPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to search, fetch, and manage entities, relations, notes, sources, pages, media, and status entries in a libSQL-backed personal archive knowledge graph through MCP tools. It also supports a public-only mode that exposes restricted search and fetch access.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Provides AI agents with durable, searchable project memory, session notes, skills, and bounded context packs over MCP while leaving orchestration to the client.
      15
      MIT

    TDQS

    B3.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct graph or PR purposes, such as get_node vs get_neighbors vs shortest_path. The main overlap is between list_prs and triage_prs, both listing PRs, though triage_prs is narrower and adds priority-oriented impact data. get_pr_impact is distinct by targeting a specific PR.

    Naming Consistency3/5

    All names use snake_case, but conventions are mixed: some are verb_noun (query_graph, get_node, list_prs), while others are noun phrases or specialized labels (god_nodes, graph_stats, shortest_path). The pattern is readable but not consistently action-first.

    Tool Count5/5

    Ten tools is well-scoped for a read-only knowledge-graph context and PR triage server. Each tool covers a distinct query or inspection need without excessive surface area.

    Completeness4/5

    The surface covers graph search, node details, neighbors, communities, statistics, paths, and PR impact/triage well. A minor gap is the lack of a list_communities operation, making community IDs less discoverable before calling get_community.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing