Docs

Step 1: Resolve a Library

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.

Always pass a query argument — it is required and directly affects result ranking. Use the user’s intent to form the query, which helps disambiguate when multiple libraries share a similar name. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.

Result fields

Each result includes:

• Library ID — Context7-compatible identifier (format: /org/project)
• Name — Library or package name
• Description — Short summary
• Code Snippets — Number of available code examples
• Source Reputation — Authority indicator (High, Medium, Low, or Unknown)
• Benchmark Score — Quality indicator (100 is the highest score)
• Versions — List of versions if available. Use one of those versions if the user provides a version in their query. The format is /org/project/version.

Selection process

1. Analyze the query to understand what library/package the user is looking for
2. Select the most relevant match based on:
   • Name similarity to the query (exact matches prioritized)
   • Description relevance to the query’s intent
   • Documentation coverage (prioritize libraries with higher Code Snippet counts)
   • Source reputation (consider libraries with High or Medium reputation more authoritative)
   • Benchmark score (higher is better, 100 is the maximum)
3. If multiple good matches exist, acknowledge this but proceed with the most relevant one
4. If no good matches exist, clearly state this and suggest query refinements
5. For ambiguous queries, request clarification before proceeding with a best-guess match

IMPORTANT: Do not call ctx7 library more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.

Version-specific IDs

If the user mentions a specific version, use a version-specific library ID:

The available versions are listed in the ctx7 library output. Use the closest match to what the user specified.

Step 2: Query Documentation

Retrieves up-to-date documentation and code examples for the resolved library.

You must call ctx7 library first to obtain the exact Context7-compatible library ID required to use this command, UNLESS the user explicitly provides a library ID in the format /org/project or /org/project/version.

IMPORTANT: Do not call ctx7 docs more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.

Writing good queries

The query directly affects the quality of results. Be specific and include relevant details, but keep each query to one topic — if the question spans multiple distinct concepts, run a separate ctx7 docs command per concept instead of combining them, unless the question is about how the concepts interact. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.

Describe what to look up in the library’s documentation in the query when possible — vague one-word queries return generic results, and multi-topic queries dilute ranking and return shallow results for each topic.

The output contains two types of content: code snippets (titled, with language-tagged blocks) and info snippets (prose explanations with breadcrumb context).

Authentication

Works without authentication. For higher rate limits: