RAG Documentation MCP Server
Mentioned as a planned feature for local embeddings generation as an alternative to OpenAI embeddings
Uses OpenAI embeddings for vector search capabilities, requiring an API key for generating embeddings of documentation content
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RAG Documentation MCP Server search for how to configure environment variables in the documentation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RAG Documentation MCP Server
An MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context.
Features
Vector-based documentation search and retrieval
Support for multiple documentation sources
Semantic search capabilities
Automated documentation processing
Real-time context augmentation for LLMs
Related MCP server: RAG Documentation MCP Server
Tools
search_documentation
Search through stored documentation using natural language queries. Returns matching excerpts with context, ranked by relevance.
Inputs:
query(string): The text to search for in the documentation. Can be a natural language query, specific terms, or code snippets.limit(number, optional): Maximum number of results to return (1-20, default: 5). Higher limits provide more comprehensive results but may take longer to process.
list_sources
List all documentation sources currently stored in the system. Returns a comprehensive list of all indexed documentation including source URLs, titles, and last update times. Use this to understand what documentation is available for searching or to verify if specific sources have been indexed.
extract_urls
Extract and analyze all URLs from a given web page. This tool crawls the specified webpage, identifies all hyperlinks, and optionally adds them to the processing queue.
Inputs:
url(string): The complete URL of the webpage to analyze (must include protocol, e.g., https://). The page must be publicly accessible.add_to_queue(boolean, optional): If true, automatically add extracted URLs to the processing queue for later indexing. Use with caution on large sites to avoid excessive queuing.
remove_documentation
Remove specific documentation sources from the system by their URLs. The removal is permanent and will affect future search results.
Inputs:
urls(string[]): Array of URLs to remove from the database. Each URL must exactly match the URL used when the documentation was added.
list_queue
List all URLs currently waiting in the documentation processing queue. Shows pending documentation sources that will be processed when run_queue is called. Use this to monitor queue status, verify URLs were added correctly, or check processing backlog.
run_queue
Process and index all URLs currently in the documentation queue. Each URL is processed sequentially, with proper error handling and retry logic. Progress updates are provided as processing occurs. Long-running operations will process until the queue is empty or an unrecoverable error occurs.
clear_queue
Remove all pending URLs from the documentation processing queue. Use this to reset the queue when you want to start fresh, remove unwanted URLs, or cancel pending processing. This operation is immediate and permanent - URLs will need to be re-added if you want to process them later.
Usage
The RAG Documentation tool is designed for:
Enhancing AI responses with relevant documentation
Building documentation-aware AI assistants
Creating context-aware tooling for developers
Implementing semantic documentation search
Augmenting existing knowledge bases
Configuration
Usage with Claude Desktop
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"rag-docs": {
"command": "npx",
"args": [
"-y",
"@hannesrudolph/mcp-ragdocs"
],
"env": {
"OPENAI_API_KEY": "",
"QDRANT_URL": "",
"QDRANT_API_KEY": ""
}
}
}
}You'll need to provide values for the following environment variables:
OPENAI_API_KEY: Your OpenAI API key for embeddings generationQDRANT_URL: URL of your Qdrant vector database instanceQDRANT_API_KEY: API key for authenticating with Qdrant
TODO
Make embeddings configurable to allow choosing between OpenAI embeddings or local Ollama for vector generation
License
This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Acknowledgments
This project is a fork of qpd-v/mcp-ragdocs, originally developed by qpd-v. The original project provided the foundation for this implementation.
Available Tools
7 toolsclear_queueA
Remove all pending URLs from the documentation processing queue. Use this to reset the queue when you want to start fresh, remove unwanted URLs, or cancel pending processing. This operation is immediate and permanent - URLs will need to be re-added if you want to process them later. Returns the number of URLs that were cleared from the queue.
Inputs: no named parameters.
extract_urlsA
Extract and analyze all URLs from a given web page. This tool crawls the specified webpage, identifies all hyperlinks, and optionally adds them to the processing queue. Useful for discovering related documentation pages, API references, or building a documentation graph. Handles various URL formats and validates links before extraction.
Inputs: url (required), add_to_queue.
list_queueA
List all URLs currently waiting in the documentation processing queue. Shows pending documentation sources that will be processed when run_queue is called. Use this to monitor queue status, verify URLs were added correctly, or check processing backlog. Returns URLs in the order they will be processed.
Inputs: no named parameters.
list_sourcesA
List all documentation sources currently stored in the system. Returns a comprehensive list of all indexed documentation including source URLs, titles, and last update times. Use this to understand what documentation is available for searching or to verify if specific sources have been indexed.
Inputs: no named parameters.
remove_documentationA
Remove specific documentation sources from the system by their URLs. Use this tool to clean up outdated documentation, remove incorrect sources, or manage the documentation collection. The removal is permanent and will affect future search results. Supports removing multiple URLs in a single operation.
Inputs: urls (required).
run_queueA
Process and index all URLs currently in the documentation queue. Each URL is processed sequentially, with proper error handling and retry logic. Progress updates are provided as processing occurs. Use this after adding new URLs to ensure all documentation is indexed and searchable. Long-running operations will process until the queue is empty or an unrecoverable error occurs.
Inputs: no named parameters.
search_documentationA
Search through stored documentation using natural language queries. Use this tool to find relevant information across all stored documentation sources. Returns matching excerpts with context, ranked by relevance. Useful for finding specific information, code examples, or related documentation.
Inputs: query (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose with no overlap: clear_queue manages queue state, extract_urls discovers links, list_queue and list_sources provide status views, remove_documentation deletes sources, run_queue processes the queue, and search_documentation queries content. The descriptions reinforce these boundaries, making misselection unlikely.
All tool names follow a consistent verb_noun pattern using snake_case, such as clear_queue, extract_urls, list_queue, list_sources, remove_documentation, run_queue, and search_documentation. This uniformity makes the set predictable and easy for agents to navigate.
With 7 tools, the server is well-scoped for its RAG documentation purpose, covering queue management, source discovery, processing, and search. Each tool earns its place without bloat, aligning with typical server sizes of 3-15 tools for focused functionality.
The tool set covers core RAG documentation workflows including queue management, source extraction, indexing, and search, with no dead ends. A minor gap exists in lacking tools for updating or modifying existing documentation sources, but agents can work around this by re-adding URLs.
Maintenance
Related MCP Connectors
Ingest, manage, and retrieve documents for RAG-powered AI applications
Versioned documentation registry and semantic search for AI tools and coding assistants.
Search and read Vector Panda docs: API operations, pricing, storage tiers, measured benchmarks.
Tailor Platform for AI assistants: search, list and read the platform documentation.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn MCP server implementation that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to augment their responses with relevant documentation context20 npm263MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to enhance their responses with relevant documentation through a semantic vector search, offering tools for managing and processing documentation efficiently.65MIT
- AlicenseNot gradedqualityDmaintenanceProvides advanced document search and processing capabilities through vector stores, including PDF processing, semantic search, web search integration, and file operations. Enables users to create searchable document collections and retrieve relevant information using natural language queries.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and retrieve information from Teleport documentation using a vector database. It provides a tool for semantic vector search over pre-populated embeddings of Teleport pages and examples to assist with technical queries.1MIT