ai-context-nas
Related Servers
Alternatives to ai-context-nas
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceSelf-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.3MIT
- AlicenseNot gradedqualityDmaintenanceSelf-hosted MCP server for private Obsidian vaults on GitHub, exposing tools to search, read, write, and analyze Markdown notes and their link graph.MIT
- FlicenseNot gradedqualityBmaintenanceProvides self-hosted, versioned project memory with full-text and vector search, enabling search, retrieval, upsertion, and history management of project entries via MCP tools.-
- AlicenseNot gradedqualityBmaintenanceServes 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
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityCmaintenanceProvides AI agents with durable, searchable project memory, session notes, skills, and bounded context packs over MCP while leaving orchestration to the client.15MIT
TDQS
Scored across 10 tools
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.
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.
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.
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.