context7

Resolve Context7 library IDs and fetch up-to-date documentation via API.

7|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/manojbajaj95/mcp-skill --skill context7-manojbajaj95
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context7
Source: https://github.com/manojbajaj95/mcp-skill/tree/main/skills/context7
Command: npx skills add https://github.com/manojbajaj95/mcp-skill --skill context7-manojbajaj95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires fastmcp.

What problem does it solve?

Context7 development often requires discovering library IDs and accessing up-to-date documentation for libraries. This skill automates those tasks by exposing two tools: resolve-library-id and query-docs.

Core Features & Use Cases

  • Resolve-library-id: find Context7-compatible library IDs (format: /org/project) from a library name.
  • Query-docs: retrieve documentation and code examples for a specific library using up-to-date Context7 data.
  • Use Case: quickly locate a library by name, obtain its ID, and fetch relevant usage docs to integrate into your codebase.

Quick Start

Call resolve_library_id with a library name to obtain a Context7 library ID, then use query_docs to fetch matching libraries and their documentation.

Frequently Asked Questions about context7

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

FAQPage Schema
How do I fetch up-to-date documentation for an MCP library programmatically?

To fetch up-to-date documentation for an MCP library, use the query-docs tool with a resolved Context7 library ID to retrieve structured descriptions and code examples for integration.

What's the best way to resolve a Context7 library ID from a library name?

Resolving a Context7 library ID from a name requires calling the resolve-library-id tool, which returns the matching library identifier in the /org/project format for documentation queries.

Do I need external authentication to retrieve Context7 docs and code examples?

No external authentication is needed to retrieve Context7 docs and code examples; the tool relies on the provided Context7 API to return structured results without requiring external API keys.

Does the Context7 documentation tool support async tool-calling workflows?

Yes, the Context7 documentation tool supports async tool-calling workflows through its fastmcp dependency, enabling developers to programmatically discover libraries and fetch docs asynchronously.

Can I use Context7 to discover Python library versions and retrieve integration code?

Yes, you can use Context7 to discover Python library versions and retrieve integration code by resolving the library ID first, then querying the docs for up-to-date examples and descriptions.

What are the limitations of using Context7 for resolving library IDs?

A key limitation of using Context7 for resolving library IDs is its two-step dependency: you must successfully resolve the ID via resolve-library-id before you can fetch any documentation using query-docs.