context7-mcp

Fetches current library documentation and code examples via Context7 MCP queries.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/arayaroma/ether --skill context7-mcp-arayaroma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context7-mcp
Source: https://github.com/arayaroma/ether/tree/main/skills/context7-mcp
Command: npx skills add https://github.com/arayaroma/ether --skill context7-mcp-arayaroma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LLM training data goes stale, so answers about libraries and frameworks can reference outdated APIs or deprecated patterns. This Skill retrieves up-to-date documentation from Context7 at query time, so answers about React, Next.js, Prisma, Supabase, and similar tools reflect current versions. ## Core Features & Use Cases - Library Resolution: Maps a library name from the user's question to the correct Context7 library ID, preferring exact matches, higher-quality sources, and version-specific IDs. - Scoped Documentation Queries: Fetches focused documentation per concept, splitting multi-topic questions into separate queries for deeper results. - Use Case: A user asks "How do I configure Next.js 15 middleware with Supabase auth?" The Skill resolves the Next.js library ID, queries the docs for middleware configuration, and returns current code examples with version-accurate syntax. ## Quick Start Ask how to configure or use a specific library feature, such as requesting the current API for Prisma transactions or Next.js middleware setup.

Frequently Asked Questions about context7-mcp

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

FAQPage Schema
How do I get up-to-date documentation for a library like Next.js or Prisma?▼

Ask your question naming the library and topic, and the Skill resolves the library through Context7's resolve-library-id tool, then fetches current docs with query-docs. The answer includes recent code examples rather than potentially outdated training-data knowledge.

How does Context7 library resolution choose the right documentation source?▼

Resolution matches the library name from your question against Context7's index, preferring exact name matches and higher benchmark scores that indicate documentation quality. Official or primary packages are preferred over community forks when multiple matches exist.

Does Context7 support version-specific documentation like React 19 or Next.js 15?▼

Yes. When you mention a version in your question, the resolution step prefers version-specific library IDs if they are available. This ensures the fetched documentation and code examples match the release you are actually using.

Why should multi-topic questions be split into separate documentation queries?▼

Combined queries dilute ranking and return shallow results for each topic. Issuing one query-docs call per concept with the same library ID produces deeper, more relevant documentation, unless the question is specifically about how the concepts interact.

When should I not use Context7 documentation fetching?▼

It is unnecessary for general programming concepts, language syntax, or logic questions that do not depend on a specific library's current API. It also requires the Context7 MCP tools to be available in the environment.