← marketplace
engineerstoolOfficialsha:af43aecf1e3cc32cmanual
context7
Use when you need up-to-date, version-specific library docs and real code examples pulled into the prompt — add 'use context7' so the agent stops guessing outdated APIs.
Install confidence
curl --create-dirs -fsSL https://skillmake.xyz/i/context7 -o ~/.claude/skills/context7/SKILL.md
Pinned content
sha:af43aecf1e3cc32c
Generated with
manual
Source
github.com
The file served at /api/marketplace/context7-af43aecf/raw matches this hash. Inspect before install, then copy the command.
3,093 chars · ~773 tokens
--- name: context7 description: "Use when you need up-to-date, version-specific library docs and real code examples pulled into the prompt — add 'use context7' so the agent stops guessing outdated APIs." source: https://github.com/upstash/context7 generated: 2026-07-23T01:35:07.886Z category: tool audience: engineers --- ## When to use - Writing code against a fast-moving library where your model's training data is stale - You keep getting hallucinated methods, wrong import paths, or APIs that no longer exist - You want docs and examples for a specific version of a framework, not a generic average - Wiring an MCP server into Claude Code, Cursor, or another agent to fetch live documentation on demand ## Key concepts ### 'use context7' prompt trigger Appending the phrase 'use context7' to a prompt tells the MCP-enabled agent to fetch current, version-specific documentation and code snippets for the libraries mentioned, injecting them into context before answering. ### resolve-library-id then get-library-docs Context7 exposes two MCP tools: resolve-library-id maps a package name to a Context7-compatible library ID, and get-library-docs pulls that library's docs (optionally scoped to a topic and token budget). ### Version-specific documentation Rather than serving one blended snapshot, Context7 indexes docs per library version so the examples it returns match the exact release you are building against. ### Remote vs local MCP server You can point an agent at the hosted endpoint https://mcp.context7.com/mcp or run the server locally via npx @upstash/context7-mcp — both expose the same tools; the remote endpoint needs no install. ## API reference ``` claude mcp add --transport http context7 https://mcp.context7.com/mcp ``` Register the hosted Context7 MCP server in Claude Code (no local install needed). ``` claude mcp add --transport http context7 https://mcp.context7.com/mcp ``` ``` npx -y @upstash/context7-mcp ``` Run the Context7 MCP server locally over stdio. ``` npx -y @upstash/context7-mcp ``` ``` resolve-library-id(libraryName) ``` Resolve a human package name (e.g. 'next.js') to a Context7-compatible library ID. ``` resolve-library-id({ libraryName: "next.js" }) ``` ``` get-library-docs(context7CompatibleLibraryID, topic?, tokens?) ``` Fetch up-to-date docs for a resolved library, optionally scoped to a topic and token budget. ``` get-library-docs({ context7CompatibleLibraryID: "/vercel/next.js", topic: "app router", tokens: 5000 }) ``` ## Gotchas - You must add 'use context7' (or otherwise invoke the tools) — the server does not fire automatically on every prompt - The library must be indexed by Context7; obscure or private packages may not resolve to an ID - Higher token budgets pull more docs but eat into your context window — scope with a topic when you can - It surfaces documentation, not your private codebase — pair it with repo-aware tooling for internal APIs --- Generated by SkillMake from https://github.com/upstash/context7 on 2026-07-23T01:35:07.886Z. Verify against source before relying on details.
File: ~/.claude/skills/context7/SKILL.md