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 "{}"