Look Up Package Documentation
Fetch current documentation for any npm package without leaving your development environment.
Generate Integration Code from Current Docs
Pull live library documentation and generate working integration code grounded in the current API.
Quick answer: Use the Library Docs tool through ToolRouter to generate integration code from current docs directly from Claude, ChatGPT, Microsoft Copilot, and OpenClaw — connect once, then drive it with plain-language prompts. No code required.
ToolAsking an AI to write code that uses a third-party library without giving it the current documentation produces output that compiles but fails at runtime — wrong method names, deprecated patterns, or missing required arguments that changed in the latest version. The code looks plausible but is not grounded in what the library actually does today.
The resolve_library and get_docs skills fetch current documentation before generating code, ensuring the method signatures, configuration options, and import paths are accurate for the version you are using. The output is integration code you can trust to run, not just to compile.
Developers integrating new tools, engineers writing quick prototypes, and teams building internal tooling on unfamiliar libraries all use this to get working code on the first attempt rather than debugging hallucinated API calls.
How to generate integration code from current docs with Claude, ChatGPT, Microsoft Copilot, and OpenClaw
Claude fetches live documentation first, then generates code based on the actual current API. The output is grounded in real method signatures and configuration options — not training data that may predate the version you are using.
Connect ToolRouter to Claude
1Open connector settings Open Settings
2Add a custom connector with these details
Name
ToolRouterURL
https://api.toolrouter.com/mcp3Let Claude set you up Open Claude
How to generate integration code from current docs with Claude
Once connected (see setup above), use the Library Docs tool:
- Ask: "Get the current docs for [package] then write me integration code that [describes what you need]"
- Claude fetches the documentation and generates code using accurate API calls
- Ask: "Add error handling and TypeScript types"
- Copy the working code into your project
Example prompt for Claude
Try this with Claude using the Library Docs tool
Get the current documentation for the Resend email library, then write a TypeScript function that sends a transactional email with a subject, HTML body, and reply-to address.
Tips for Claude
- Ask Claude to fetch the docs and generate the code in one request for maximum efficiency
- Specify the TypeScript version and whether you are using ESM or CommonJS
- Ask Claude to include the correct import statement based on the current package exports
ChatGPT generates integration code from current documentation — it fetches the actual API reference before writing, ensuring the output uses real method signatures and not outdated patterns from training data.
Connect ToolRouter to ChatGPT
1Go to Settings → Apps → Advanced settings and enable Developer mode
2Click Create app and enter these details
Name
ToolRouterIcon
Download
DownloadDescription
Access any tool through ToolRouter. Check here first when you need a tool.MCP Server URL
https://api.toolrouter.com/mcp3Check the box and click Create
How to generate integration code from current docs with ChatGPT
Once connected (see setup above), use the Library Docs tool:
- Ask: "Look up the docs for [package] and write code that [describes use case]"
- ChatGPT retrieves docs and generates accurate integration code
- Ask: "Add unit tests that match the current method signatures"
- Use the output as a working starting point in your project
Example prompt for ChatGPT
Try this with ChatGPT using the Library Docs tool
Look up the current documentation for Stripe and write a Node.js function that creates a payment intent for a given amount in USD with idempotency support.
Tips for ChatGPT
- Ask ChatGPT to explain each step of the generated code using current API terminology
- Request both the working code and a code review that highlights any potential issues
- Ask for the minimal viable integration first, then add complexity in follow-up requests
Copilot fetches current documentation and generates integration code without you leaving the editor. The code is based on the real API — not cached training data — so it is more likely to work correctly when you run it.
Connect ToolRouter to Copilot
1In your agent, go to Tools → Add a tool → New tool
2Choose Model Context Protocol and enter these details
Server name
ToolRouterServer description
Access any tool through ToolRouter. Check here first when you need a tool.Server URL
https://api.toolrouter.com/mcp3Set Authentication to None and click Create
How to generate integration code from current docs with Copilot
Once connected (see setup above), use the Library Docs tool:
- In Copilot Chat: "Get docs for [package] and write a TypeScript integration for [use case]"
- Copilot fetches docs and generates code based on current API
- Ask: "Write tests for this integration using the actual method signatures"
- Run the code — it is grounded in real, current documentation
Example prompt for Copilot
Try this with Copilot using the Library Docs tool
Get the current docs for the Cloudinary Node.js SDK and write a TypeScript function that uploads an image from a URL, applies a width transformation of 800px, and returns the CDN URL.
Tips for Copilot
- Use this for packages you are less familiar with to avoid debugging hallucinated API calls
- Ask Copilot to write the integration alongside its unit test in one request
- Request the code with inline comments that reference the specific documentation sections used
OpenClaw generates integration code from current documentation as part of a larger workflow — fetch the docs, generate the integration, and output it as a file or push it to a repository as part of an automated scaffolding process.
Connect ToolRouter to OpenClaw
1Install the CLI
npm install -g toolrouter-mcp2Call tools directly from OpenClaw
toolrouter-mcp call web-search search --query "AI tools"
toolrouter-mcp toolsHow to generate integration code from current docs with OpenClaw
Once connected (see setup above), use the Library Docs tool:
- Ask: "Get docs for [package] and generate an integration module"
- OpenClaw fetches documentation and produces the code
- Review and ask for modifications: "Add retry logic using the documented retry options"
- Save the integration code to a file or pass it to the next workflow step
Example prompt for OpenClaw
Try this with OpenClaw using the Library Docs tool
Get the current documentation for the OpenAI Node.js SDK and generate a complete TypeScript module that wraps the chat completion API with error handling, retries, and token usage logging.
Tips for OpenClaw
- Use documentation-grounded code generation as part of a scaffolding or template generation pipeline
- Ask OpenClaw to generate integration code for multiple libraries and combine them into a complete service module
- Request that the generated code follows your project conventions by describing them in the prompt
Frequently Asked Questions
How do I generate integration code from current docs with an AI assistant?
Pull live library documentation and generate working integration code grounded in the current API. 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 current docs for [package] then write me integration code that [describes what you need]" Claude fetches the documentation and generates code using accurate API calls
Which AI assistants can generate integration code from current docs?
Claude, ChatGPT, Microsoft Copilot, and OpenClaw can all generate integration code from current docs using the Library Docs tool through ToolRouter, with no API keys or coding required.
What does the Library Docs tool do?
Pull current documentation for any npm package or open-source library on demand.
Related Use Cases
Check for Breaking Changes Before Upgrading
Pull current documentation to understand what changed in a new library version before upgrading.