Skip to content

Context7 Platform -- Up-to-date docs for AI agents

fix: claude code plugin name and details image (#1417)

Fahreddin Özcan3553cb202303
diff --git a/docs/clients/claude-code.mdx b/docs/clients/claude-code.mdx
index e2a9671d..c76dc5e0 100644
--- a/docs/clients/claude-code.mdx
+++ b/docs/clients/claude-code.mdx
@@ -154,10 +154,6 @@ This skill triggers automatically when you ask about libraries, frameworks, or n
3. **Fetch**: Calls `query-docs` with the library ID and your specific question
4. **Return**: Provides code examples and explanations from current documentation
</Accordion>
-<Accordion title="Limits">
-- Maximum 3 documentation calls per question
-- Uses version-specific IDs when you mention versions
-</Accordion>
</AccordionGroup>
### Agents
diff --git a/docs/docs.json b/docs/docs.json
index b8863836..bb7f8a15 100644
--- a/docs/docs.json
+++ b/docs/docs.json
@@ -39,7 +39,7 @@
},
{
"group": "Clients",
- "pages": ["clients/cursor", "clients/claude-code"]
+ "pages": ["clients/claude-code","clients/cursor"]
},
{
"group": "SDKs",
diff --git a/docs/images/clients/claude-code/mcp-details.png b/docs/images/clients/claude-code/mcp-details.png
index 26017fd3..f4e5b21b 100644
Binary files a/docs/images/clients/claude-code/mcp-details.png and b/docs/images/clients/claude-code/mcp-details.png differ
diff --git a/plugins/claude/context7/.claude-plugin/plugin.json b/plugins/claude/context7/.claude-plugin/plugin.json
index a53438cb..ed65ab9f 100644
--- a/plugins/claude/context7/.claude-plugin/plugin.json
+++ b/plugins/claude/context7/.claude-plugin/plugin.json
@@ -1,5 +1,5 @@
{
- "name": "context7",
+ "name": "context7-plugin",
"description": "Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.",
"author": {
"name": "Upstash"
diff --git a/plugins/claude/context7/README.md b/plugins/claude/context7/README.md
index a54ea164..48a88e90 100644
--- a/plugins/claude/context7/README.md
+++ b/plugins/claude/context7/README.md
@@ -13,10 +13,11 @@ This plugin provides:
## Installation
-Copy this plugin folder to your Claude Code plugins directory, or run:
+Add the marketplace and install the plugin:
```bash
-claude plugins install context7
+claude plugin marketplace add upstash/context7
+claude plugin install context7-plugin@context7-marketplace
```
## Available Tools
diff --git a/plugins/claude/context7/agents/docs-researcher.md b/plugins/claude/context7/agents/docs-researcher.md
index 2682c02e..ec7e8aa0 100644
--- a/plugins/claude/context7/agents/docs-researcher.md
+++ b/plugins/claude/context7/agents/docs-researcher.md
@@ -1,42 +1,40 @@
---
+name: docs-researcher
description: Lightweight agent for fetching library documentation without cluttering your main conversation context.
-tools:
- - resolve-library-id
- - query-docs
model: sonnet
---
-# Documentation Researcher
+You are a documentation researcher specializing in fetching up-to-date library and framework documentation from Context7.
-This agent handles library and framework documentation lookups in a separate context, keeping your main conversation lean.
+## Your Task
-## When to Use
+When given a question about a library or framework, fetch the relevant documentation and return a concise, actionable answer with code examples.
-Spawn this agent when:
+## Process
-- You need documentation for a library but don't want tool call results in your main context
-- You're asking "how do I..." or "what's the API for..." questions
-- You want focused answers with code examples
-- You're working on a long task and want to avoid context bloat
+1. **Identify the library**: Extract the library/framework name from the user's question.
-## How It Works
+2. **Resolve the library ID**: Call `resolve-library-id` with:
+ - `libraryName`: The library name (e.g., "react", "next.js", "prisma")
+ - `query`: The user's full question for relevance ranking
-1. Takes your question about a library or framework
-2. Resolves the library name to a Context7 ID using `resolve-library-id`
-3. Picks the best match based on name accuracy and benchmark scores
-4. Fetches relevant documentation with `query-docs`
-5. Returns a concise answer with code examples
+3. **Select the best match**: From the results, pick the library with:
+ - Exact or closest name match
+ - Highest benchmark score
+ - Appropriate version if the user specified one (e.g., "React 19" → look for v19.x)
-## Examples
+4. **Fetch documentation**: Call `query-docs` with:
+ - `libraryId`: The selected Context7 library ID (e.g., `/vercel/next.js`)
+ - `query`: The user's specific question for targeted results
-```
-spawn docs-researcher to look up React hooks documentation
-spawn docs-researcher: how do I set up Prisma with PostgreSQL?
-spawn docs-researcher to find Tailwind CSS grid utilities
-```
+5. **Return a focused answer**: Summarize the relevant documentation with:
+ - Direct answer to the question
+ - Code examples from the docs
+ - Links or references if available
-## Limits
+## Guidelines
-- Maximum 3 `query-docs` calls per question
-- Uses version-specific IDs when you mention a version (e.g., "Next.js 15")
-- Passes your full question to the query for better relevance ranking
+- Pass the user's full question as the query parameter for better relevance
+- When the user mentions a version (e.g., "Next.js 15"), use version-specific library IDs if available
+- If `resolve-library-id` returns multiple matches, prefer official/primary packages over community forks
+- Keep responses concise - the goal is to answer the question, not dump entire documentation
diff --git a/plugins/claude/context7/commands/docs.md b/plugins/claude/context7/commands/docs.md
index a4cefa3a..8a2df781 100644
--- a/plugins/claude/context7/commands/docs.md
+++ b/plugins/claude/context7/commands/docs.md
@@ -1,5 +1,6 @@
---
description: Look up documentation for any library
+argument-hint: <library> [query]
---
# /context7:docs
diff --git a/plugins/claude/context7/skills/documentation-lookup/SKILL.md b/plugins/claude/context7/skills/documentation-lookup/SKILL.md
index e40db8d0..8b7f3996 100644
--- a/plugins/claude/context7/skills/documentation-lookup/SKILL.md
+++ b/plugins/claude/context7/skills/documentation-lookup/SKILL.md
@@ -1,61 +1,53 @@
---
-description: Automatically fetches library documentation when you ask about frameworks, APIs, or code patterns.
-triggers:
- - library questions
- - framework setup
- - API references
- - code examples
+name: documentation-lookup
+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.
---
-# Documentation Lookup
+When the user asks about libraries, frameworks, or needs code examples, use Context7 to fetch current documentation instead of relying on training data.
-This skill activates when you ask questions about libraries, frameworks, or need code examples. It fetches current documentation from source repositories instead of relying on training data.
+## When to Use This Skill
-## When It Triggers
+Activate this skill when the user:
-The skill runs automatically when you:
+- Asks setup or configuration questions ("How do I configure Next.js middleware?")
+- 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.)
-- Ask setup questions ("How do I configure Next.js middleware?")
-- Request code generation involving libraries ("Write a Prisma query for...")
-- Need API references ("What are the Supabase auth methods?")
-- Mention specific frameworks (React, Vue, Svelte, Express, Tailwind, etc.)
+## How to Fetch Documentation
-## Process
+### Step 1: Resolve the Library ID
-1. **Resolve**: Finds the library ID using `resolve-library-id` with your question as context
-2. **Select**: Picks the best match based on exact name matching and quality scores
-3. **Fetch**: Calls `query-docs` with the library ID and your specific question
-4. **Return**: Provides code examples and explanations from current documentation
+Call `resolve-library-id` with:
-## Guidelines
+- `libraryName`: The library name extracted from the user's question
+- `query`: The user's full question (improves relevance ranking)
+
+### Step 2: Select the Best Match
-- Uses your full question as the query parameter for better relevance
-- Limited to 3 documentation calls per question to avoid overwhelming context
-- Picks version-specific IDs when you mention versions ("Next.js 15", "React 19")
-- Checks available versions from the resolution step before querying
+From the resolution results, choose based on:
-## Supported Libraries
+- 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
-Works with any library indexed by Context7, including:
+### Step 3: Fetch the Documentation
-- Frontend: React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Solid, Astro
-- Backend: Express, Fastify, Hono, NestJS, Django, FastAPI, Rails
-- Databases: Prisma, Drizzle, Supabase, Firebase, MongoDB
-- Styling: Tailwind CSS, Styled Components, Emotion
-- And thousands more...
+Call `query-docs` with:
-## Example Interactions
+- `libraryId`: The selected Context7 library ID (e.g., `/vercel/next.js`)
+- `query`: The user's specific question
-**You**: "How do I set up authentication with Supabase?"
+### Step 4: Use the Documentation
-**Skill activates**:
-1. Resolves "supabase" → `/supabase/supabase`
-2. Queries with "authentication setup"
-3. Returns current auth documentation with code examples
+Incorporate the fetched documentation into your response:
-**You**: "Show me React 19 use() hook examples"
+- Answer the user's question using current, accurate information
+- Include relevant code examples from the docs
+- Cite the library version when relevant
+
+## Guidelines
-**Skill activates**:
-1. Resolves "react" with version context → `/facebook/react/v19.0.0`
-2. Queries with "use hook examples"
-3. Returns React 19-specific documentation
+- **Be specific**: Pass the user's full question as the query for better results
+- **Version awareness**: When users mention versions ("Next.js 15", "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