F
licenseNot graded
qualityC
maintenanceEnables retrieval-augmented question answering over LangGraph documentation, allowing MCP-compatible hosts to query a semantic vector store and receive context-aware responses with source attribution.
-
LangGraph RAG MCP
by pedarias
Related Servers
Alternatives to LangGraph RAG MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible hosts to retrieve LangGraph documentation through retrieval-augmented generation, with source attribution for responses.-
- FlicenseNot gradedqualityCmaintenanceProvides MCP-compatible hosts with retrieval-augmented access to LangGraph documentation, enabling Claude and other assistants to answer questions with relevant, source-attributed context.-
- FlicenseNot gradedqualityDmaintenanceA customized MCP server that enables integration between LLM applications and documentation sources, providing AI-assisted access to LangGraph and Model Context Protocol documentation.-
- FlicenseNot gradedqualityDmaintenanceA simple Model Context Protocol server that enables searching and retrieving relevant documentation snippets from Langchain, Llama Index, and OpenAI official documentation.-
- AlicenseNot gradedqualityDmaintenanceA modular RAG (Retrieval-Augmented Generation) service framework with pluggable architecture and full observability, enabling AI assistants to perform document Q\&A, semantic search, and knowledge base construction through the Model Context Protocol.MIT
TDQS
B3.3/5.0
Scored across 2 tools
Disambiguation5/5
langgraph_query_tool and read_page have clearly distinct purposes: one searches indexed docs and returns excerpts/URLs, the other reads a specific URL with pagination. No overlap; the intended workflow is search then read.
Naming Consistency3/5
Both use snake_case, but langgraph_query_tool includes a domain prefix and redundant _tool suffix while read_page is a simple verb_noun. The inconsistency in naming pattern makes it mixed but still readable.
Tool Count3/5
Two tools is thin for a RAG server; a typical retrieval interface might include a list-sources or metadata tool. The pair covers core search-and-read but feels minimal.
Completeness4/5
The search and read tools cover the essential retrieval lifecycle (query -> fetch full content). Minor gaps exist, such as listing all indexed documents or retrieving metadata, but agents can work around them.
Maintenance
ActivityMaintained
ResponsivenessNo issues