Resolve a specific library
resolve-library-id maps a package name and task to the library identifier needed by the retrieval tool.
Documentation ↗MCP server / developer tools / source-linked
Context7 MCP
Context7 fits a narrow question: which documented API should this code use? Library identification and version-aware retrieval make it more targeted than a broad web search. Use it while implementing a dependency, then verify the resulting code against your installed package.
Before you choose.
Identify the implementation and the job it supports.
Which implementation is this?
Upstash's maintained documentation service; MCP and CLI + Skills are separate supported integration modes.
Implementation source ↗
Upstash's maintained documentation service; MCP and CLI + Skills are separate supported integration modes.
Implementation source ↗
Context7 fits a narrow question: which documented API should this code use? Library identification and version-aware retrieval make it more targeted than a broad web search. Use it while implementing a dependency, then verify the resulting code against your installed package.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Remote HTTP or local stdio
- Authentication
- API key; remote OAuth endpoint available
Register https://mcp.context7.com/mcp with a bearer API key, or use /mcp/oauth for browser authorization. The interactive installer lets you choose MCP versus CLI + Skills; confirm the chosen mode in your client.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
npx ctx7 setupWhat it actually exposes.
Concrete capabilities with maintainer sources.
Retrieve task-focused documentation
query-docs takes a library ID and question; it returns relevant documentation rather than executing the package.
Documentation ↗Target the intended version
State the version in the prompt, or supply a known library ID to avoid an ambiguous matching step.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Community signals.
Concrete reports from public community discussions, kept separate from product documentation.
I spent 3 weeks building my dream MCP setup and honestly, most of it was useless
The author describes Context7 as a daily time saver because it retrieves current library documentation inside the agent workflow.
“Having up-to-date docs for any library right in Claude is incredible; it saves me probably 30 minutes daily.”Open community source ↗
What's your must-have MCP server that you use daily?
A commenter values Context7 for routing prompts to current dependency documentation rather than stale examples, while another reports occasional hallucinations.
“It finds relevant documentation and adds it to context instead of relying on old Stack Overflow examples.”Open community source ↗
Community evidence is anecdotal and may reflect one setup, version or account. It is included for discovery and risk-sensing, not as a representative rating or independent benchmark. Verify the current official documentation before acting on a report.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Proposed workflow: review a dependency migration
Suggested evaluation, not an observed test result.
- Record the version currently installed and the target version.
- Resolve the library, then request the relevant migration and API documentation.
- Ask the coding agent to explain each proposed change with its documentation reference before running your own checks.
What to inspect: A traceable migration plan and version-specific examples. This workflow was not executed for this directory.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
OAuth is available over remote HTTP only. A local stdio connection uses API-key authentication.
Boundary reference ↗Editorial inference: retrieved examples are evidence for an implementation, not proof that it builds with your lockfile and runtime.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A traceable migration plan and version-specific examples. This workflow was not executed for this directory.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| MCP Documentation Server | Editorial choice: the question concerns MCP protocol documentation itself. | A narrower protocol corpus rather than general library lookup. Documentation ↗ |
| GitHub MCP Server | Editorial choice: inspect a project's actual repository, issues or pull requests. | Repository context still needs interpretation against the installed version. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Is Context7 itself a coding agent?
No. It supplies documentation to the agent that performs the coding.
Documentation ↗
Must I run a local server?
No. Use its remote endpoint; local stdio is an alternative for clients that need it.
Documentation ↗
Source trail.
Maintainer documentation used in this record.