context7

Resolve library names to Context7 IDs and fetch official documentation.

13|2|Updated Aug 9, 2025
One-click install
npx skills add https://github.com/petbrains/mvp-builder --skill context7-petbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context7
Source: https://github.com/petbrains/mvp-builder/tree/main/.claude/skills/context7
Command: npx skills add https://github.com/petbrains/mvp-builder --skill context7-petbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides up-to-date library documentation by resolving library IDs and fetching official docs using Context7 MCP tools, including trust scoring and topic-focused retrieval.

Core Features & Use Cases

  • Resolves library names to Context7 IDs
  • Fetches library documentation with targeted topics
  • Applies trust scores and snippet counts to select best matches
  • Supports multi-step workflows for API references

Quick Start

THINK: Resolve a library name (e.g., "react") → RESOLVE: /mcp__context7__resolve-library-id libraryName="react" → SELECT: /reactjs/react.dev → FETCH: /mcp__context7__get-library-docs with topic="getting started" tokens=12000

Frequently Asked Questions about context7

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find up-to-date documentation for npm and PyPI packages?

Context7 resolves library names to official documentation by matching package identifiers across npm and PyPI ecosystems, then fetches targeted API references and guides with trust scoring to surface the most relevant results.

Can I retrieve specific API reference sections from library documentation?

Yes. Context7 fetches library docs with topic-focused queries—specify topics like 'getting started' or 'API reference'—and returns multiple results ranked by trust score and snippet relevance for precise section retrieval.

What's the workflow for locating documentation across multiple package ecosystems?

Context7 follows a THINK → RESOLVE → FETCH → APPLY workflow: resolve the library name to a Context7 ID, select the correct package source, fetch docs with your topic and token budget (3K–20K), then apply results to your implementation.

How does Context7 handle library name resolution for npm and PyPI packages?

Context7 maps library names to ecosystem-specific IDs, disambiguating between similarly named packages across npm and PyPI by applying trust scores and ecosystem context to surface the correct official documentation source.

Can I control documentation retrieval depth and result count?

Yes. Context7 supports token scaling (3K–20K) to adjust retrieval depth and snippet-count parameters to filter results, letting you balance comprehensiveness against token usage for your documentation queries.

Does Context7 work with private or unofficial package repositories?

Context7 resolves and fetches documentation for libraries in official npm and PyPI ecosystems using MCP tools with trust scoring. Private repositories and unofficial sources fall outside the supported Context7-enabled ecosystems.