Home / MCP / DocsFetcher MCP Server
Fetches package documentation across languages for LLMs without API keys.
Configuration
View docs{
"mcpServers": {
"docsfetcher": {
"command": "npx",
"args": [
"-y",
"@smithery/cli@latest",
"run",
"@cdugo/mcp-get-docs",
"--config",
"'{}'"
]
}
}
}DocsFetcher MCP Server fetches package documentation from multiple language ecosystems and presents structured data for large language models, enabling rich library insights without requiring API keys. It supports multiple languages, extracts README and API docs, and offers prompts to analyze documentation for concise summaries and explanations.
You use this MCP server by configuring it in your MCP client and invoking its endpoints or tools to fetch and analyze documentation. You can fetch docs for a single package, across multiple languages, or for a URL, then summarize or explain dependencies as needed.
Key usage patterns you can perform include: fetching package docs by name, fetching docs from a URL, fetching multilingual docs for comparison, and using prompts to summarize or explain dependency errors. Use the provided tools from the server to trigger these actions and receive structured data optimized for LLM consumption.
Prerequisites: Node.js 18 or later.
1. Install the MCP server tooling and dependencies using an MCP client configuration shown for your environment. The following configuration runs the server via npx and hooks it into your MCP client.
{
"mcpServers": {
"docsfetcher": {
"command": "npx",
"args": [
"-y",
"@smithery/cli@latest",
"run",
"@cdugo/mcp-get-docs",
"--config",
"'{}'"
]
}
}
}2. If you use Cursor IDE, add a new MCP server with the following configuration to enable access to the same functionality.
{
"Name": "docsFetcher",
"Command": "npx -y @smithery/cli@latest run @cdugo/mcp-get-docs --config \"{}\""
}Prerequisites include having Node.js 18 or later installed on your development machine. The MCP server is designed to work with Claude Desktop and Cursor IDE without requiring an API key.
Starting the server locally involves cloning the project, installing dependencies, and running the start script. You can customize the port if needed.
Fetch docs from a specific URL and return structured documentation data.
Fetch docs for a named package with an optional language specification to gather README, API docs, and code examples.
Smart tool that fetches documentation for a library by name or URL and cross-references multiple sources.
Fetch docs for a package across multiple language ecosystems for comparison and multilingual coverage.
Create a comprehensive summary of a library's documentation, highlighting key concepts, usage, and caveats.
Generate explanations for dependency-related errors to aid debugging and resolution.