Context7 Pro

Your expert agent for leveraging Context7 tools to provide accurate, up-to-date library and framework documentation in your development workflow.

When to Use This Agent

Choose Context7 Pro when:

• You need accurate, current documentation for any library or framework
• Working with APIs where the docs may have changed since training data cutoff
• Integrating unfamiliar libraries where hallucinated API signatures would be costly
• Looking up specific function signatures, configuration options, or usage patterns
• Comparing API approaches across different library versions

Consider alternatives when:

• You need general architecture advice — use a cloud architect agent
• You need to write documentation — use a documentation engineer agent
• You need code generation without specific library lookups — use a general coding agent

Quick Start

Copy
# .claude/agents/context7-pro.yml
name: Context7 Pro
model: claude-sonnet
tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep
  - mcp_context7_resolve_library_id
  - mcp_context7_get_library_docs
description: Documentation expert using Context7 tools for accurate, up-to-date library and framework reference

Example invocation:

claude "Look up the current API for React Server Components — I need the exact syntax for use client and use server directives and how they interact with Suspense boundaries"

Core Concepts

Context7 Workflow

Step	Action	Purpose
1. Resolve	resolve_library_id("react")	Find the canonical library identifier
2. Fetch	get_library_docs(id, topic)	Get current documentation for a topic
3. Apply	Use fetched docs to answer accurately	Ground responses in real documentation

Why Context7 Matters

Without Context7:
  Q: "How do I use the new Suspense API?"
  A: [May contain outdated or hallucinated API signatures]

With Context7:
  1. Resolve: react → "react-official"
  2. Fetch: get_library_docs("react-official", "Suspense")
  3. Answer: [Accurate, current API with real signatures]

Supported Documentation Sources

Category	Examples
Frontend	React, Vue, Svelte, Angular, Next.js, Nuxt
Backend	Express, FastAPI, Django, Spring Boot, Rails
Database	Prisma, Drizzle, Mongoose, SQLAlchemy, TypeORM
Cloud	AWS SDK, Azure SDK, GCP client libraries
Testing	Jest, Vitest, Playwright, Cypress, pytest
Build Tools	Vite, Webpack, esbuild, Turbopack

Configuration

Parameter	Description	Default
auto_resolve	Automatically resolve library IDs on first mention	true
cache_duration	How long to cache resolved library IDs	session
doc_depth	Documentation detail level (overview, detailed, exhaustive)	detailed
include_examples	Include code examples from docs	true
version_specific	Target specific library version	latest

Best Practices

1. Always resolve the library ID before fetching docs. Library names can be ambiguous — "react" could mean React core, React Native, or React Router. The resolve step confirms which library you're targeting and prevents documentation mismatches.

2. Be specific with your topic queries. Instead of fetching all React docs, request "React useEffect cleanup" or "React Server Components streaming." Specific queries return focused, actionable documentation rather than overwhelming overviews.

3. Verify API signatures against fetched documentation. When Context7 returns function signatures, parameter types, or configuration options, use those exact signatures in your code. Don't interpolate or guess — the fetched documentation is your source of truth.

4. Check version-specific documentation when targeting older releases. Libraries frequently change APIs between major versions. If your project pins React 17, fetch docs for React 17 specifically rather than the latest version.

5. Combine Context7 lookups with local codebase patterns. After fetching the canonical API docs, check how the library is already used in the project. This ensures your new code follows both the official API and the project's existing conventions.

Common Issues

Library resolution returns multiple matches. Popular names like "router" or "orm" match many packages. Provide more context — "react-router v6" or "prisma orm" — to get the correct library ID. If multiple matches remain, verify against the project's package.json.

Fetched documentation seems outdated. Context7's documentation sources update on different schedules. If the docs seem stale, cross-reference with the library's official website or GitHub releases page. Report outdated sources to improve future accuracy.

Agent answers without using Context7 tools. If the agent skips Context7 and answers from training data, the response may contain outdated APIs. Explicitly instruct the agent to use Context7 tools for every library-specific question, or configure it as a hard requirement in the agent's system prompt.