context7-mcp
- Use it when:
- You ask about a library or framework, its setup or API, or want code that uses one; it switches on by itself when one comes up.
- It does:
- Resolves the library to a Context7 ID, preferring the closest name, official packages and the version you named, then queries its docs one concept at a time.
- You get:
- An answer built on the fetched docs, with their code examples and the library version cited.
- Unlike find-docs:
- That one, from the same repo, uses the ctx7 CLI; this one calls the Context7 MCP server's resolve-library-id and query-docs tools.
Needs the Context7 MCP server connected.
TL;DR
Upstash's Context7 skill for agents with the Context7 MCP server connected. When a question involves a library, such as configuring a Next.js proxy or writing a Prisma query, the agent first calls resolve-library-id with the library's name and what it wants to know, then picks the closest match, favoring higher benchmark scores, version-specific IDs when you mention a version, and official packages over community forks. It then calls query-docs with that ID, one concept per call: a question spanning routing, auth and caching becomes three calls on the same library unless it's about how they interact, because combined queries return shallow results for each. The answer uses the fetched documentation and its code examples rather than training data, and cites the library version when it matters.
Summarizes the skill at 078c0c7.
npx skills add https://github.com/upstash/context7 --skill context7-mcp skills.sh pageSource on GitHubAll skills from upstash/context7
- Total Downloads
- 6,700 on skills.sh, Nov 9, 2026
- Repo stars
- 64,390 upstash/context7
- First seen
- Mar 11, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 156 |
| Sep 28 | 139 |
| Oct 5 | 202 |
| Oct 12 | 231 |
| Oct 19 | 372 |
| Oct 26 | 296 |
| Nov 2 | 264 |
| Nov 9 | 238 |
| Category |
Guides for frameworks, databases and SDKs, mostly from their vendors. Everything for building software: planning, coding, debugging, design, frameworks, cloud, agents and skills. |
|---|---|
| Type |
Operates a CLI, API, app or bundled script to get something done. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Needs an MCP server connected. |
| Publisher |
A verified publisher on skills.sh, or the company or maintainer behind the product the skill operates. |
| Topics | |
| Stack |
SKILL.md
From upstash/context7 at 078c0c7. Checked daily, last changed Nov 7, 2026.
Frontmatter
name: context7-mcp
description: This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.When the user asks about libraries, frameworks, or needs code examples, use Context7 to fetch current documentation instead of relying on training data.
When to Use This Skill
Activate this skill when the user:
- Asks setup or configuration questions ("How do I configure a Next.js proxy?")
- Requests code involving libraries ("Write a Prisma query for...")
- Needs API references ("What are the Supabase auth methods?")
- Mentions specific frameworks (React, Vue, Svelte, Express, Tailwind, etc.)
How to Fetch Documentation
Step 1: Resolve the Library ID
Call resolve-library-id with:
libraryName: The library name extracted from the user's questionquery: What to look up in the library's documentation (improves relevance ranking)
Step 2: Select the Best Match
From the resolution results, choose based on:
- Exact or closest name match to what the user asked for
- Higher benchmark scores indicate better documentation quality
- If the user mentioned a version (e.g., "React 19"), prefer version-specific IDs
Step 3: Fetch the Documentation
Call query-docs with:
libraryId: The selected Context7 library ID (e.g.,/vercel/next.js)query: What to look up in the library's documentation, scoped to a single concept
If the user's question spans multiple distinct concepts (e.g. routing and auth and caching), make a separate query-docs call per concept with the same library ID, unless the question is about how the concepts interact — combined queries dilute ranking and return shallow results for each topic.
Step 4: Use the Documentation
Incorporate the fetched documentation into your response:
- Answer the user's question using current, accurate information
- Include relevant code examples from the docs
- Cite the library version when relevant
Guidelines
- Be specific: Describe what to look up in the library's documentation, but keep each query to a single concept
- One topic per query: Split multi-topic questions into separate
query-docscalls — resolve the library ID once, then query per concept, unless the question is about how the concepts interact - Version awareness: When users mention versions ("Next.js 16", "React 19"), use version-specific library IDs if available from the resolution step
- Prefer official sources: When multiple matches exist, prefer official/primary packages over community forks