Fetch up-to-date library documentation via Context7 MCP

Recipe: Fetch library docs via @upstash/context7-mcp

Server launch

npx -y @upstash/context7-mcp
# stdio transport, no API key, no env vars needed

MCP config (claudedesktopconfig.json / settings.json)

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp"]
    }
  }
}

Step 1: resolve-library-id

Turns a human-readable library name into the canonical Context7 ID.

Tool call:

{
  "name": "resolve-library-id",
  "arguments": {
    "libraryName": "Next.js",
    "query": "How to use the App Router with server components"
  }
}

Real response (executed 2026-06-10): Returns ranked results. Top hit:

• Library ID: /vercel/next.js
• Snippets: 5763
• Reputation: High
• Benchmark: 92.6
• Versions available: v16.2.2, v16.1.6, v15.1.11, v14.3.0-canary.87, v13.5.11, v12.3.7, v11.1.3, …

Also returns related libraries (next.js commerce, authkit-nextjs, learn-next.js) — useful for disambiguation.

Step 2: query-docs

Fetches relevant documentation chunks + code examples for a topic.

Tool call:

{
  "name": "get-library-docs",
  "arguments": {
    "context7CompatibleLibraryID": "/vercel/next.js",
    "topic": "How to use the App Router with server components",
    "tokens": 500
  }
}

Real response (executed 2026-06-10): Returned 5 documentation chunks with source URLs, including:

1. App Router SSR with fetch() and no-store — full TSX example of async Server Component with cache: 'no-store'
2. App Router glossary — "built on top of React Server Components, file-system based routing"
3. Server Component definition — "default component type in the App Router, rendering on the server"
4. Production checklist — Server Components "do not contribute to client-side JavaScript bundle sizes"

Each chunk includes its GitHub source URL for traceability.

Key details

• Two tools exposed: resolve-library-id, get-library-docs (aliased as query-docs in some versions)
• Token budget: the tokens param caps response size (default varies, 500–5000 is practical)
• Version pinning: pass /vercel/next.js/v16.2.2 to get version-specific docs
• No auth, no API key, no env vars — fully credential-free
• Cold start: ~3-5s on first npx invocation (package download), <1s thereafter