home / skills / upstash / context7 / context7-mcp

This skill fetches up-to-date library documentation and generates code examples for frameworks like React, Next.js, Prisma, and Supabase.

npx playbooks add skill upstash/context7 --skill context7-mcp

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
2.1 KB
---
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 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.)

## How to Fetch Documentation

### Step 1: Resolve the Library ID

Call `resolve-library-id` with:

- `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

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`: The user's specific question

### 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**: 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

Overview

This skill connects user questions about libraries, frameworks, and APIs to up-to-date Context7 documentation and returns accurate examples and setup guidance. It is designed for TypeScript-first workflows and focuses on current docs rather than relying on training data. Use it when users ask for configuration, API references, or code samples tied to specific packages or versions.

How this skill works

The skill resolves a library identifier from the user's full question, ranks candidate docs by relevance and quality, and selects the best match (preferring exact names and official packages). It then queries the selected Context7 library with the user's full query and extracts code examples, API signatures, and version details. The final response synthesizes that documentation into concise, actionable guidance and includes cited version information when relevant.

When to use it

  • User asks how to configure or set up a framework (e.g., Next.js middleware setup).
  • User requests code that uses a particular library (e.g., Prisma query, Supabase auth).
  • User needs API reference or method lists for a package (e.g., React hooks API).
  • User mentions a specific framework or version (React, Vue, Next.js 15, etc.).
  • User asks for up-to-date examples or docs that may have changed since training data.

Best practices

  • Always pass the user's full question as the query to improve relevance ranking.
  • Prefer exact name or version-specific library IDs when the user specifies a version.
  • Favor official or primary package documentation over forks or community mirrors.
  • Include relevant code examples from the fetched docs and cite the documented version.
  • If multiple high-quality matches exist, explain choices and present the most applicable snippet first.

Example use cases

  • Generate a Next.js middleware example and include configuration for edge/runtime.
  • Write a Prisma query for filtering and pagination using the version the user specified.
  • Show Supabase authentication methods and a minimal sign-in example with current APIs.
  • Explain how to migrate a React component to a new Hooks API version with code snippets.
  • Provide Tailwind configuration examples for a specific PostCSS or framework setup.

FAQ

What information should I include in my question?

Include the library name, any specific version, and the exact task or error you need help with to improve matching and results.

What if multiple documentation versions match my query?

The skill prefers a version-specific match if you mention one; otherwise it ranks by exact name and benchmark score and will state which version it used.