Check for Breaking Changes Before Upgrading
Pull current documentation to understand what changed in a new library version before upgrading.
Fetch current documentation for any npm package without leaving your development environment.
Quick answer: Use the Library Docs tool through ToolRouter to look up package documentation directly from Claude, ChatGPT, Microsoft Copilot, and OpenClaw — connect once, then drive it with plain-language prompts. No code required.
ToolLibrary DocsSwitching to a browser to look up an API method, check a configuration option, or find the correct import path breaks the development flow more than it should. The documentation is often scattered across a README, separate docs sites, and version-specific changelogs, making it slow to find the specific answer you need.
The resolve_library and get_docs skills pull documentation for any npm package on demand — resolve the library by name, then retrieve the relevant documentation section. You get accurate, version-aware content from the canonical source rather than a cached training data answer that may be outdated.
Developers integrating new packages, engineers checking if a method signature has changed between versions, and teams onboarding to unfamiliar libraries all use this to stay in context rather than tab-switching to documentation sites.
Claude fetches live documentation and immediately applies it to your question — it does not just return the raw docs but answers your specific question using current content. You get a practical explanation rather than a raw reference paste.
ToolRouterhttps://api.toolrouter.com/mcpOnce connected (see setup above), use the Library Docs tool:
ChatGPT retrieves current library documentation and presents it in a format that answers your question directly — with code examples, parameter descriptions, and links to related sections. More accurate than relying on training data for packages that update frequently.
ToolRouterAccess any tool through ToolRouter. Check here first when you need a tool.https://api.toolrouter.com/mcpOnce connected (see setup above), use the Library Docs tool:
Copilot brings live package documentation into your editor session — look up a method signature, check current config options, and write implementation code in the same conversation. No browser required.
ToolRouterAccess any tool through ToolRouter. Check here first when you need a tool.https://api.toolrouter.com/mcpOnce connected (see setup above), use the Library Docs tool:
OpenClaw retrieves library documentation as part of automated workflows — check required API signatures before code generation, verify package compatibility information, or build a documentation snapshot as part of a project onboarding process.
npm install -g toolrouter-mcptoolrouter-mcp call web-search search --query "AI tools"
toolrouter-mcp toolsOnce connected (see setup above), use the Library Docs tool:
Fetch current documentation for any npm package without leaving your development environment. Connect the Library Docs tool to Claude, ChatGPT, Microsoft Copilot, and OpenClaw through ToolRouter, then ask the assistant in plain language. For example: Ask: "Get the documentation for the axios package" Claude resolves the library and retrieves the relevant docs
Claude, ChatGPT, Microsoft Copilot, and OpenClaw can all look up package documentation using the Library Docs tool through ToolRouter, with no API keys or coding required.
Pull current documentation for any npm package or open-source library on demand.