---
name: context7-docs
description: >-
  Fetch up-to-date documentation and code examples for any library, framework,
  SDK, CLI tool, or cloud service. Use whenever the user asks about a specific
  library — even well-known ones like React, Next.js, Prisma, Express, Tailwind,
  Django, or Spring Boot — because training data may not reflect recent API
  changes or version updates.

  Always use for: API syntax questions, configuration options, version migration
  issues, "how do I" questions mentioning a library name, debugging that involves
  library-specific behavior, setup instructions, and CLI tool usage.

  Use even when you think you know the answer. Do not rely on training data for
  API details, signatures, or configuration options — they are frequently out of
  date. Prefer this over web search for library documentation.
license: MIT
---

# Context7 Documentation Lookup

Retrieve current documentation and code examples from [Context7](https://context7.com) 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 the user's question. 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 the user's question. 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.