context7-mcp

Retrieve official library documentation and API references via Context7 MCP.

1|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/lollipopkit/cc-skills --skill context7-mcp-lollipopkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context7-mcp
Source: https://github.com/lollipopkit/cc-skills/tree/main/context7-mcp
Command: npx skills add https://github.com/lollipopkit/cc-skills --skill context7-mcp-lollipopkit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When users ask for library of API docs, this Skill resolves the library's official docs via Context7 MCP instead of guessing, ensuring accurate references.

Core Features & Use Cases

  • Resolve & Fetch: Call resolve-library-id, then fetch docs with get-library-docs (mode code for API/reference; info for conceptual).
  • Cite & Avoid Guesswork: Cite snippets from retrieved docs and keep to latest version unless specified.
  • Ambiguity Handling: If multiple matches, pick closest and mention ambiguity briefly before proceeding.

Quick Start

Ask for a library's API docs, e.g., "What is the useEffect hook in React according to Context7 MCP?" and Context7 MCP will fetch and present the answer with citations.

Frequently Asked Questions about context7-mcp

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

FAQPage Schema
How do I fetch official API documentation for a package?

Fetching official API documentation resolves the package name to its library ID, then retrieves docs in code mode for API references and signatures or info mode for conceptual guides, ensuring accurate references with citations from the latest version.

Can I look up specific API methods and usage examples for libraries?

Yes, you can retrieve specific API methods, usage examples, and function signatures by requesting docs for a particular package, which fetches official references and code examples directly rather than relying on guesses or invented APIs.

What happens if a library name is ambiguous or matches multiple packages?

When multiple matches exist, the Skill picks the closest match and briefly mentions the ambiguity before proceeding, ensuring you still get accurate documentation for the intended library.

How do I get documentation for framework-specific topics like hooks or routing?

Documentation retrieval handles framework-specific topics like hooks or routing by resolving the package context and fetching relevant official docs in the appropriate mode, delivering accurate guidance on those specific features.

Does this work with the latest version of a library?

The Skill prioritizes the latest documentation pages by default unless you specify a different version, keeping your references current with the most recent API and feature documentation.