Context7 Usage

To fetch up-to-date library documentation, use the Context7 workflow by first resolving the library name to a Context7-compatible ID, then retrieving the docs using the get-library-docs tool with an optional topic parameter.

The correct workflow to resolve a library ID requires calling the resolve-library-id tool with a library name like "/facebook/react" to obtain a Context7-compatible ID, which is then passed to get-library-docs to ensure accurate results.

Yes, you can retrieve documentation for specific modules by using the optional topic parameter in the get-library-docs tool, such as setting topic="routing" for Next.js to focus on specific API references.

Context7 supports codebase verification and migrations for TypeScript and NixOS by providing current API references and structured usage examples, applying in scenarios such as feature work and onboarding.

Limitations when fetching library docs include adhering to token limits and trust-score considerations to ensure relevant and safe results, and enforcing a strict workflow that requires resolving a library ID before any documentation retrieval.

Context7 requires resolving a library name before getting library docs to ensure the system queries the correct Context7-compatible ID, which enforces a strict workflow that guarantees accurate and up-to-date API references.