docs
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., "@docs How do I use ChromaDB with LangChain?"
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.
MCP Documentation Search Server
An MCP (Model Context Protocol) server that lets AI clients like Claude Desktop search live documentation for popular developer libraries and return clean, source-cited summaries — powered by a lightweight RAG (Retrieval-Augmented Generation) pipeline.
Ask a question like "How do I use ChromaDB with LangChain?" and the tool searches the official docs, scrapes and cleans the relevant pages, and returns grounded, sourced text — all callable directly from an MCP-compatible AI client.
How it works
User query
│
▼
Serper API (site-scoped web search)
│
▼
httpx (async fetch of result pages, run concurrently)
│
▼
trafilatura (clean HTML → readable text)
│
▼
Groq LLM (optional: context-grounded summarization)
│
▼
Source-cited responseThe server exposes a single MCP tool, get_docs(query, library), registered via FastMCP and served over stdio transport — the standard way MCP hosts (like Claude Desktop) communicate with local tool servers.
Related MCP server: MCP Server for Up-to-Date Library Documentation
Features
🔌 MCP-compliant server — discoverable and callable by any MCP client (tested with Claude Desktop)
🔍 Scoped documentation search across LangChain, LlamaIndex, OpenAI, and
uvdocs via the Serper API⚡ Concurrent async fetching — all result pages are fetched in parallel with
asyncio.gather+httpx🧹 Clean text extraction from raw HTML using
trafilatura🧠 LLM-grounded summarization via Groq, with enforced source citation
🛡️ Resilient to failures — a single broken/slow URL won't crash the whole request
🖥️ Includes a standalone MCP client (
client.py) for testing outside of Claude Desktop
Tech Stack
Category | Tools |
Language | Python 3.13+ |
Protocol | Model Context Protocol (MCP) via |
Async |
|
Search | Serper API |
Content extraction |
|
LLM | Groq ( |
Package management |
|
Project Structure
web-scraper-using-mcp/
├── main.py # MCP server — exposes the get_docs tool
├── client.py # Standalone MCP client for local testing
├── utils.py # HTML cleaning + LLM helper functions
├── pyproject.toml # Project metadata & dependencies (uv)
├── uv.lock # Locked dependency versions
├── .env.example # Template for required API keys
└── src/ # Package scaffolding (uv init)Setup
1. Clone the repo
git clone https://github.com/<your-username>/<repo-name>.git
cd <repo-name>2. Install dependencies
uv sync3. Configure environment variables
cp .env.example .envThen open .env and add your keys:
SERPER_API_KEY=your_serper_api_key_here
GROQ_API_KEY=your_groq_api_key_hereGet a free Serper API key: https://serper.dev
Get a free Groq API key: https://console.groq.com
4. Run the server
uv run main.pyYou should see FastMCP start up and log Starting MCP server 'docs' with transport 'stdio'.
Usage
Option A: Test with the included client
uv run client.pyThis spins up the server, lists available tools, calls get_docs, and prints an LLM-generated, source-cited answer.
Option B: Connect to Claude Desktop
Add the server to your claude_desktop_config.json:
{
"mcpServers": {
"web-scraper": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/project", "main.py"],
"env": {
"SERPER_API_KEY": "your_serper_api_key_here",
"GROQ_API_KEY": "your_groq_api_key_here"
}
}
}
}Restart Claude Desktop, then ask something like "Use the docs tool to look up how ChromaDB works with LangChain." Claude will discover and call the get_docs tool directly.
Demo
Server running locally:

Claude Desktop discovering and requesting to call the tool:

Supported Libraries
Library | Docs source |
| docs.langchain.com |
| docs.llamaindex.ai |
| platform.openai.com/docs |
| docs.astral.sh/uv |
Known Limitations
Retrieval is search-based (Serper), not embedding/vector-based — no vector database is used
Limited to two search results per query
Only supports the four libraries listed above
No caching — repeated identical queries re-fetch and re-scrape
Roadmap
Add a vector store (e.g. Chroma) for cached, embedding-based retrieval
Support additional libraries and configurable result counts
Add a CLI interface to
client.pyfor arbitrary queriesAdd automated tests
Author
Built by Samrudhi as a hands-on project exploring the Model Context Protocol, agentic tool-calling, and LLM-grounded retrieval.
Available Tools
1 toolget_docsA
Search the latest docs for a given query and library. Supports langchain, openai, llama-index and uv.
Inputs: query (required), library (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
Only a single tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly defined: searching docs.
With a single tool, naming consistency is trivially maintained. The name 'get_docs' follows a clear verb_noun pattern and accurately reflects its function.
A single tool for a docs server feels somewhat thin. While searching is the core need, the surface area is minimal and offers no other useful operations like listing libraries or fetching specific doc pages.
The tool covers the main search use case for the supported libraries, but lacks any auxiliary operations such as retrieving a known doc directly or discovering available libraries. Minor gaps exist but agents can likely work around them.
Maintenance
Related MCP Connectors
Versioned documentation registry and semantic search for AI tools and coding assistants.
@latest documentation and code examples to 9000+ libraries for LLMs and AI code editors in a singl…
Find, write, publish and check pages and API references in your DeveloperHub docs from an AI client
Provide your AI coding tools with token-efficient access to up-to-date technical documentation for…
Related MCP Servers
- AlicenseCqualityDmaintenanceProvides real-time access to up-to-date library documentation and code examples for any programming library. Helps AI coding assistants deliver accurate, current information instead of relying on outdated training data.110 npmMIT
- FlicenseAqualityDmaintenanceProvides Large Language Models with real-time access to the latest documentation for Python libraries like Langchain, LlamaIndex, and OpenAI, enabling accurate and up-to-date code suggestions.1-
- AlicenseAqualityDmaintenanceEnables LLM hosts to retrieve live, relevant documentation excerpts from official library docs sites via a search-and-RAG tool, avoiding reliance on training data.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables developers to ask natural-language questions and receive grounded answers sourced from official AI and Python library documentation, with automatic search, extraction, and source preservation.-