fetch-library-docsLABSCO SUMMARY
Real documentation pulled into the conversation, so answers about a library rest on its docs rather than memory.
The library tool takes either a name or a URL, so an agent does not have to know which it has, and the multilingual tool fetches the same package across ecosystems at once — useful when a name exists in several languages and you want to compare.
What it is
A server that fetches documentation for packages and libraries so an assistant can answer questions grounded in the real docs — by package name or URL, across many language ecosystems, returning README, API docs, and examples.
What you get
- fetch-package-docs fetches docs for a package, with an optional language; fetch-url-docs fetches from a specific documentation URL
- fetch-library-docs is the smart entry point that takes either a package name or a URL
- fetch-multilingual-docs fetches a package's docs across several language ecosystems at once
- Covers JavaScript, Python, Java, .NET, Ruby, PHP, Rust, Go, and Swift; ships prompts for summarising docs and explaining dependency errors
Requirements
Runs through npx; Node is the prerequisite. No API key.
Setup effort
One command — npx -y @smithery/cli@latest run @cdugo/mcp-get-docs --config "{}"
USE CASES
Answering a how-do-I question about a library
fetch-library-docs pulls the README and API docs by name or URL so the answer cites the real documentation.
Getting docs for a specific package and language
fetch-package-docs fetches a named package's docs, narrowed to a language when the name is ambiguous.
Comparing a package across ecosystems
fetch-multilingual-docs returns docs for the same package name in several languages together.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
fetch-multilingual-docsfetch-package-docsfetch-url-docsBEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected. Summarize-library-docs and explain-dependency-error are prompts, not tools. All four only read public documentation and need no key; fetch-library-docs accepts a package name or a URL.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
npx -y @smithery/cli@latest run @cdugo/mcp-get-docs --config "{}"MCP Clients
Claude Desktop
{
"mcpServers": {
"docsFetcher": {
"command": "npx",
"args": [
"-y",
"@smithery/cli@latest",
"run",
"@cdugo/mcp-get-docs",
"--config",
"{}"
]
}
}
}Cursor
Add to .cursor/mcp.json (or Cursor Settings → MCP → Add New MCP Server with the same name and command).
{
"mcpServers": {
"docsFetcher": {
"command": "npx",
"args": [
"-y",
"@smithery/cli@latest",
"run",
"@cdugo/mcp-get-docs",
"--config",
"{}"
]
}
}
}Any MCP client — local build
Clone the repository and build it
git clone https://github.com/cdugo/package-documentation-mcp
cd package-documentation-mcp
npm install
npm run buildPoint your client at the build
This is what npm start runs (node build/index.js). It is a stdio server, so the client launches it; <YOUR_PATH_TO_PACKAGE_DOCUMENTATION_MCP> is the full path of your clone.
{
"mcpServers": {
"docsFetcher": {
"command": "node",
"args": [
"<YOUR_PATH_TO_PACKAGE_DOCUMENTATION_MCP>/build/index.js"
]
}
}
}