Context7
Developer tools Listed by MCPBayUp-to-date, version-specific library docs and code examples pulled into the assistant's context
By: Upstash
The connection URL lives in your cabinet. Use "Add" above, then open "My MCPs" — the address for your AI client appears there.
About
Context7 gives a coding assistant current documentation for thousands of open-source libraries and frameworks, so it writes code against the API that actually exists today instead of what it remembers from training.
Two tools:
- resolve-library-id — turns a plain library name (for example "next.js" or "supabase") into a Context7 library ID.
- query-docs — fetches relevant documentation sections and code snippets for that library, optionally narrowed to a topic and a token budget.
Typical use: ask the assistant to build something with a fast-moving framework and add "use context7" to the prompt; the assistant looks up the library and grounds its answer in the current docs.
Who it is for: developers working in Claude, Cursor, VS Code and other MCP clients who keep running into outdated or hallucinated APIs.
Notes: works without an account; an API key from context7.com raises rate limits. Maintained by Upstash.
Tools (2)
Query DocumentationRetrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Do not call this tool more than 3 times per question. If you know the programming language the user is working in, pass it as `language` so the results match their setup.
Resolve Context7 Library IDResolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. 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 of the version is /org/project/version. For best results, select libraries based on name match, source reputation, snippet coverage, benchmark score, and relevance to your use case. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return 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: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.