context7-mcp

name	context7-mcp
description	Use for library, framework, SDK, API, or CLI questions that need current documentation or version-specific behavior.

When the task depends on external library, framework, SDK, API, or CLI behavior, use Context7 to fetch current documentation instead of relying on memory alone.

This skill is for direct documentation lookup. It does not by itself require a planning or research subagent.

When to Use

• Setup or configuration questions
• API syntax or usage questions
• Version-specific behavior
• Code generation involving external libraries/frameworks
• CLI flag or command reference questions

How to Fetch Documentation

Step 1: Resolve the Library ID

Call resolve-library-id with:

• libraryName: the library or tool name
• query: the user's full question

Step 2: Choose the Best Match

Prefer:

• exact name match,
• official source,
• stronger reputation,
• better benchmark/snippet coverage,
• version-specific ID when the user names a version.

Step 3: Query the Docs

Call query-docs with:

• libraryId: the selected Context7 ID
• query: the user's full question

Step 4: Answer with the Docs

• use the fetched guidance,
• include relevant examples,
• mention version assumptions when relevant,
• keep the answer tied to the user's task.

Escalation

If direct docs lookup still leaves important uncertainty for a risky integration, do one focused follow-up query if needed, then either implement with stated assumptions or escalate to api-researcher with an explicit reason.

For routine library questions, direct Context7 use is enough.