mcpField
C
context7-docs

context7-docs

github.com/upstashDevelopment63.9k45 installsUpdated today
Repository

About context7-docs

A skill for retrieving current library documentation and code examples through Context7 tools. It guides library lookup and focused documentation queries for questions about libraries, frameworks, SDKs, CLIs, and cloud services.

Key features

  1. 01Resolve library names to Context7 IDs
  2. 02Query documentation by concept
  3. 03Choose matches using source and quality details
  4. 04Limit queries and protect sensitive information

Use cases

  1. 01Look up current framework configuration guidance
  2. 02Find SDK or CLI usage examples
  3. 03Check cloud service documentation

MCP support

Uses the Context7 extension's `resolve-library-id` and `query-docs` tools to retrieve documentation and examples. It describes a tool workflow, but does not specify MCP server management.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/upstash/context7 --skill context7-docs

After installing, type/context7-docsin Claude Code to confirm it loaded.

Details

From the project README

Context7 Documentation Lookup

Retrieve current documentation and code examples from Context7 using the resolve-library-id and query-docs tools that ship with this extension.

When to use

Reach for these tools whenever a question involves a specific library, framework, SDK, CLI tool, or cloud service. Examples:

  • "How do I configure caching in Next.js 16?"
  • "What's the syntax for Prisma's findMany with relations?"
  • "Show me a working Tailwind v4 install for a Vite app."
  • "How do I rate-limit with @upstash/ratelimit?"

Workflow

  1. Resolve the library ID. Call resolve-library-id with the library name and what to look up in the library's documentation. The tool returns matching libraries with their Context7 IDs (/org/project format), descriptions, snippet counts, and quality scores. Pick the best match — prioritize official sources, name match, and high benchmark scores.
  2. Query the docs. Call query-docs with the chosen library ID and what to look up in the library's documentation, scoped to a single concept — if the question spans multiple distinct concepts, make a separate call per concept with the same library ID, unless the question is about how the concepts interact. The tool returns documentation snippets and code examples.
  3. Answer. Cite the library ID you used and quote code examples verbatim when relevant.

If the user supplies a library ID in /org/project or /org/project/version format directly, skip step 1 and call query-docs immediately.

Constraints

  • Do not call either tool more than 3 times per question.
  • Do not pass API keys, passwords, credentials, personal data, or proprietary code as the query argument — it is sent to the Context7 API.
  • Authentication uses the CONTEXT7_API_KEY environment variable. Get a key at https://context7.com/dashboard if requests fail with an auth error.

Comments

Markdown supported