Skip to main content
Context7 integrates with Claude Code to provide current library documentation instead of relying on training data. Beyond the basic MCP connection, Claude Code supports skills, agents, and commands that make documentation lookups more powerful.

​
Installation

​
Verifying the Connection

Run /mcp in Claude Code to see all servers and manage authentication:
Claude Code MCP List
Select a server to see details including status, authentication, and available tools:
Claude Code MCP Details
You can also run claude mcp list in your terminal: 
$ claude mcp list
Checking MCP server health...

context7: https://mcp.context7.com/mcp (HTTP) - ✓ Connected

​
Using Context7

Add “use context7” to your prompts to fetch current documentation: 
use context7 to show me how to set up middleware in Next.js 15
use context7 for Prisma query examples with relations
use context7 for the Supabase syntax for row-level security
If you know the library ID, use it directly to skip resolution: 
use context7 with /supabase/supabase for authentication docs
use context7 with /vercel/next.js for app router setup
With the Context7 plugin installed, the skill triggers automatically — no need to say “use context7”.

​
The Context7 Plugin

The full Context7 plugin for Claude Code includes more than just the MCP server:

MCP Server

The tools for fetching documentation (resolve-library-id, query-docs)

Skills

Auto-triggers documentation lookups when you ask about libraries

Agents

A docs-researcher agent for focused lookups that keep context lean

Commands

/context7:docs for manual documentation queries

​
Installing the Plugin

The plugin is available from the Context7 marketplace. Run these commands in Claude Code: 
/plugin marketplace add upstash/context7
/plugin install context7-plugin@context7-marketplace
This adds the Context7 marketplace and installs the plugin with skills, agents, and commands.

​
Skills

​
Documentation Lookup Skill

This skill triggers automatically when you ask about libraries, frameworks, or need code examples. You don’t need to type “use context7” — the skill recognizes when documentation would help.
  • Setup questions: “How do I configure Next.js middleware?”
  • Code generation: “Write a Prisma query for user relations”
  • API references: “What are the Supabase auth methods?”
  • Framework mentions: React, Vue, Svelte, Express, Tailwind, etc.
  1. Resolve: Finds the library ID using resolve-library-id with your question as context
  2. Select: Picks the best match based on name accuracy 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

​
Agents

​
docs-researcher Agent

When you’re in the middle of a long task and don’t want documentation tool calls cluttering your context, spawn the docs-researcher agent. It runs in a separate context and returns just the answer.
  • You need docs but want to keep your main context clean
  • You’re working on something complex and context is getting long
  • You want a focused answer without side effects
The agent uses the same tools (resolve-library-id and query-docs) but runs on a lighter model (Sonnet) to keep things fast.

​
When to Use Agents vs Inline Tools

ScenarioUse
Deep into a task with long contextAgent
Want to avoid context bloatAgent
Context is shortInline tools
Want docs visible in conversationInline tools

​
Commands

​
/context7:docs

Manual command for documentation lookups. Format: 
/context7:docs <library> [query]
Examples: 
/context7:docs react hooks
/context7:docs next.js authentication
/context7:docs prisma relations
When to use:
  • You know exactly which library and topic you need
  • You want a quick lookup without explaining your full context
  • You’re testing what documentation is available