Library Docs fetches accurate, version-specific documentation and code examples for any library or framework — always from the live source, never from training data that may be months out of date. It covers thousands of libraries including React, Next.js, Prisma, Tailwind, Express, and more.
AI models often hallucinate outdated or incorrect API syntax because their training data doesn't reflect recent library changes. This tool bypasses that problem by fetching current documentation on demand, so you get the right method signature, the right import path, and the right configuration options for the version you're actually using.
What you can do
- resolve_library — search for any library by name and get its documentation ID plus available versions
- get_docs — fetch relevant documentation and code examples for a specific topic within a library
Who it's for
Developers who need accurate API references while coding. AI agents that write or review code and need to verify current syntax. Anyone migrating between library versions who needs to check what changed.
How to use it
- Start with resolve_library — search by library name to get the documentation ID (e.g. search "next.js" to find "/vercel/next.js")
- Use get_docs with the library ID and a natural language query to fetch relevant docs and code snippets
- Specify a version in the library ID (e.g. "/prisma/prisma/v5") to pin to version-specific docs
- Increase the tokens parameter beyond the default 5000 when you need more comprehensive coverage
Getting started
Call resolve_library with the library name first — you need the ID it returns before you can fetch docs. For most popular libraries the ID is predictable but resolve_library confirms it and shows what versions are available.
