context7

Fetch current library documentation from MCP sources.

8|3|Updated Jun 1, 2025
One-click install
npx skills add https://github.com/jonhill90/vibes --skill context7-jonhill90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context7
Source: https://github.com/jonhill90/vibes/tree/main/.github/skills/context7-sh
Command: npx skills add https://github.com/jonhill90/vibes --skill context7-jonhill90

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, curl, and includes scripts (resource) components.

What problem does it solve?

Fetch current documentation for libraries and frameworks to ensure references are up to date and reliable, instead of relying on training data that may be stale.

Core Features & Use Cases

  • MCP-based tooling to resolve library IDs and query docs for libraries and frameworks (Python, Bash, PowerShell variants).
  • Fallback scripts in scripts/ to search and fetch docs when MCP tools are unavailable.
  • Optional API key setup for higher rate limits and seamless access to live docs.

Quick Start

Use the MCP tools or the provided scripts to fetch documentation for a library and integrate it into your coding workflow.

Frequently Asked Questions about context7

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

FAQPage Schema
How do I fetch current library documentation to replace outdated training data?

Fetch current library documentation by using MCP-based tooling or provided fallback scripts to resolve library IDs and query live docs, successfully replacing outdated training data with up-to-date API references.

Why does my AI assistant provide outdated API references for libraries?

AI assistants provide outdated API references because they rely on stale training data. Fetching live library docs via MCP sources replaces this static knowledge with current, reliable framework documentation on demand.

Do I need an API key to fetch library docs with MCP sources?

An API key is not required to fetch library docs, but configuring an optional API key provides higher rate limits and seamless access to live documentation when querying MCP sources.

Can I use fallback scripts to query docs when MCP tools are unavailable?

You can use fallback scripts located in the scripts directory to search and fetch library documentation when MCP tools are unavailable, ensuring continuous access to current API references.

What's the best way to get up-to-date code examples for Python and Bash frameworks?

The best way to get up-to-date code examples is to fetch current documentation via MCP tooling, which resolves library IDs and queries live docs for Python, Bash, and PowerShell variants.

What are the limitations if I don't configure an API key for fetching documentation?

Without configuring an API key, you face lower rate limits when fetching library documentation, which may restrict the frequency of querying live docs compared to seamless access with higher limits.