GraphRAG Llama Index MCP Server
Related Servers
Alternatives to GraphRAG Llama Index MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables semantic search and question answering over a knowledge base using hybrid retrieval and grounded answers, all running offline with no API keys.4MIT
- AlicenseBqualityDmaintenanceProvides persistent knowledge graph memory for AI agents with local semantic search using Neo4j and ONNX embeddings, enabling offline operation with zero API costs.1714 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to build and query structured semantic graphs, extracting, traversing and multi-hop reasoning over entity-relation-object triples while producing Cypher and JSON-LD graph output. It also combines BM25 lexical and dense vector retrieval with rank fusion, semantic caching and context reordering for grounded agentic memory.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to persist and retrieve notes, code entities, and typed links in a local graph database across sessions, with hybrid offline search, graph traversal, and staleness checks. It also supports export/import and CLI access for backup and transfer.MIT
- AlicenseAqualityAmaintenanceEnables local AI agents to perform hybrid search (BM25 + vector) over privately indexed local files, including notes, PDFs, DOCX, source code, and OCR'd images. All indexing and retrieval stay on the machine with read-only, whitelist-scoped access.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, read, and traverse a local knowledge base of Markdown files using full-text search and relationship graph, reducing token usage.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no ambiguity: explore_entity_graph is for graph traversal from a specific entity, get_corpus_stats is for corpus-level statistics, and search is for querying the knowledge base with three distinct modes (keyword_lookup, entity_connections, thematic_overview). The tools do not overlap in functionality.
The tool names follow a consistent snake_case pattern (explore_entity_graph, get_corpus_stats, search), but 'search' is a generic verb compared to the more descriptive 'explore' and 'get', which is a minor deviation. Overall, the naming is predictable and readable.
With only 3 tools, the server feels thin for a GraphRAG system, as it might lack operations like updating or managing the knowledge base. However, the tools cover core query and exploration functions, making it borderline appropriate for basic usage.
The tool surface covers key operations for querying and exploring a GraphRAG knowledge base, including graph traversal, corpus statistics, and multi-mode search. Minor gaps exist, such as no tools for adding or modifying data, but agents can work around this for read-only analysis.