by cdugo
Get up-to-date library info with Package Documentation Fetcher – a great tool for those with an MLIS degree or a master'
Fetches documentation and package information from multiple language registries (npm, PyPI, Maven, etc.) without requiring API keys. Extracts READMEs, API docs, and code examples for LLM analysis.
Package Documentation Fetcher is a community-built MCP server published by cdugo that provides AI assistants with tools and capabilities via the Model Context Protocol. Get up-to-date library info with Package Documentation Fetcher – a great tool for those with an MLIS degree or a master' It is categorized under search web, developer tools.
You can install Package Documentation Fetcher in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Package Documentation Fetcher is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
Package Documentation Fetcher is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Package Documentation Fetcher reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated Package Documentation Fetcher against two servers with overlapping tools; this profile had the clearer scope statement.
Package Documentation Fetcher has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Package Documentation Fetcher is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Package Documentation Fetcher is the kind of server we cite when onboarding engineers to host + tool permissions.
According to our notes, Package Documentation Fetcher benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Strong directory entry: Package Documentation Fetcher surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Package Documentation Fetcher is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Package Documentation Fetcher has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 26
An MCP server that fetches package documentation from multiple language ecosystems for LLMs like Claude without requiring API keys.
<a href="https://glama.ai/mcp/servers/8yfwtryuc5"> <img width="380" height="200" src="https://glama.ai/mcp/servers/8yfwtryuc5/badge" alt="DocsFetcher Server MCP server" /> </a>{
"mcpServers": {
"docsFetcher": {
"command": "npx",
"args": [
"-y",
"@smithery/cli@latest",
"run",
"@cdugo/mcp-get-docs",
"--config",
"'{}'"
]
}
}
}
Name: docsFetcher
Command: npx -y @smithery/cli@latest run @cdugo/mcp-get-docs --config "{}"
git clone https://github.com/cdugo/package-documentation-mcp
cd package-documentation-mcp
npm install
npm run build
Once installed, you can run the server locally with:
# From the project root directory
npm start
For development with auto-restart on file changes:
npm run dev
The server will start on the default port (usually 3000). You should see output like:
🚀 DocsFetcher MCP Server running!
📋 Ready to fetch documentation
To specify a custom port:
PORT=8080 npm start
MIT
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.