About DocReader MCP Tool
DocReader MCP Tool helps LLMs search web-based documentation, extract page content, and synthesize findings. It is for AI assistants handling documentation questions, with a single tool that can perform the full search-to-summary workflow.
Key features
- 01Search documentation pages
- 02Extract content from URLs
- 03Summarize collected information
- 04Run search, extraction, and summary together
Use cases
- 01Find answers across a documentation site
- 02Gather and summarize pages for a technical question
MCP support
It exposes documentation search, content extraction, summarization, and an end-to-end reading workflow as tools for MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEDocReader MCP Tool
DocReader is a powerful tool for reading and searching documents, built on the Model Context Protocol (MCP). It enables LLMs to search, extract, and synthesize information from web-based documents, assisting AI assistants in answering questions accordingly.
Features
- Search for relevant pages across documentation websites
- Extract content from specific pages
- Aggregate and summarize discovered information
- Complete the document Q&A workflow in a single step
Installation
Requirements
- Python 3.7 or higher
- fastmcp
- beautifulsoup4
- requests
- openai
- python-dotenv
Installation Steps
-
Clone or download this repository.
-
Install the required dependencies:
pip install fastmcp beautifulsoup4 requests openai python-dotenv
- Create a
.envfile and add your API key, preferably a NetMind API key:
API_KEY=your_api_key_here
Usage
Run Directly
cd path/to/DocReaderMCP
python DocReader.py
Run with fastmcp CLI
cd path/to/DocReaderMCP
fastmcp run DocReader.py
Using with Cursor
Method 1: Temporary Addition
- In the Cursor interface, click the extensions/plugins icon in the left sidebar.
- Locate the MCP section or select "Add Tool".
- Choose "Add Local MCP Tool".
- Enter a tool name, such as "DocReader".
- Select the execution method (either point to the script path or connect via URL).
Method 2: Persistent Installation
cd path/to/DocReaderMCP
fastmcp install DocReader.py --name "DocReader" --with beautifulsoup4 requests openai python-dotenv
Toolset
DocReader MCP provides the following tool functions:
- search_docs: Search documentation pages to find those most relevant to your query.
- extract_content: Extract content from a specified URL.
- summarize_findings: Summarize the information collected.
- read_doc: Complete the entire workflow—search, extraction, and summarization—in one step.
Recommended Workflow
- Start by using
search_docsto find relevant pages on the documentation site. - Use
extract_contentto retrieve content from the most relevant pages. - Summarize your findings with
summarize_findings. - Alternatively, use
read_docto perform all these steps at once.
Example
See test_doc_reader.py for more examples of how to use each tool function.
A brief example:
from DocReader import search_docs, extract_content, summarize_findings, read_doc
doc_url = "https://flax.readthedocs.io/en/latest/index.html"
query = "How do I train a model with flax? Please help me write the training code and the inference code after training."
# 1. Search for relevant pages
results = search_docs(doc_url, query, depth=2, max_results=3)
# 2. Extract content
if results:
page_content = extract_content(results[0]['url'], query)
# 3. Summarize findings
summary = summarize_findings(query)
print(summary['summary'])
# 4. One-step workflow
final_answer = read_doc(doc_url, query)
print(final_answer)
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.