context7

First call context7_resolve-library-id with the official library name, then call context7_query-docs with a narrow, concrete question about the exact API, configuration, or syntax you need. Resolving the ID first ensures you query the correct library.

Use Context7 when the task involves external third-party libraries, frameworks, or SDKs and you need current or version-specific documentation. For questions about your local repository, use a code exploration tool instead, since Context7 only covers external documentation.

Yes, Context7 supports version-specific IDs in the /org/project/version format, and queries can target version-specific syntax, migration behavior, or configuration patterns. This helps avoid stale answers from older library versions.

Resolving the library ID first ensures the documentation query targets the correct package, since multiple libraries can share similar names. Skipping resolution risks querying the wrong project and receiving irrelevant or misleading documentation.

Avoid Context7 when the answer is already clear from local project code, when the task is generic programming knowledge unrelated to a specific library, or when you have no concrete documentation question. Speculative broad queries waste tokens without useful results.