Context7

Name: Context7 MCP Server
Availability: InStock
Author: Context7

Developer Tools2 toolsNo Auth Required

Up-to-date library documentation for coding agents. Two read-only tools — resolve a library ID, then query its docs. The directory says sign-in required; the published endpoint answered anonymously on 2026-08-18.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Context7 via MCP

https://mcp.context7.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Context7 Tools & Capabilities (2)

resolve-library-idRead-only

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Each result includes: - Library ID: Context7-compatible identifier (format: /org/project) - Name: Library or package name - Description: Short summary - Code Snippets: Number of available code examples - Source Reputation: Authority indicator (High, Medium, Low, or Unknown) - Benchmark Score: Quality indicator (100 is the highest score) - Versions: List of versions if available. Use one of those versions if the user provides a version in their query. The format of the version is /org/project/version. For best results, select libraries based on name match, source reputation, snippet coverage, benchmark score, and relevance to your use case. Selection Process: 1. Analyze the query to understand what library/package the user is looking for 2. Return the most relevant match based on: - Name similarity to the query (exact matches prioritized) - Description relevance to the query's intent - Documentation coverage (prioritize libraries with higher Code Snippet counts) - Source reputation (consider libraries with High or Medium reputation more authoritative) - Benchmark Score: Quality indicator (100 is the highest score) Response Format: - Return the selected library ID in a clearly marked section - Provide a brief explanation for why this library was chosen - If multiple good matches exist, acknowledge this but proceed with the most relevant one - If no good matches exist, clearly state this and suggest query refinements For ambiguous queries, request clarification before proceeding with a best-guess match. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.

query-docsRead-only

Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Do not call this tool more than 3 times per question.

Read from the server on 2026-08-18, including each tool's own safety annotations.

Limits

It retrieves documentation; it reads none of your code. Neither tool accepts a file, a repository path or a credential. Context7's data privacy page states that it does not store source files and that your prompts, code and conversation history are never transmitted — only the query the client formulates, the library name or ID, and client metadata.
Context7 disclaims the accuracy of what it returns. Its repository disclaimer states that projects are community-contributed, that it cannot guarantee accuracy, completeness or security, and that projects are maintained by their owners. It asks users to report suspicious content through a Report button on the project page. Carried here unsoftened, because an agent writing code from these snippets inherits the caveat.
The free plan caps at 1,000 API calls a month. Context7's pricing page states free users are blocked on reaching that limit, with 20 bonus calls granted daily while blocked until the month resets. Pro is $10 per seat per month with 5,000 included calls per seat and $10 per additional 1,000. Private repository parsing is billed separately at $5 per 1M tokens.
Anonymous callers get the lowest rate limit and no private sources. Context7's API guide describes the anonymous tier as low limits with no custom configuration. Private repositories require a Pro or Enterprise plan; they are not reachable without a key at all.
Prompts and resources are declared but empty. initialize declares prompts and resources with listChanged: true; prompts/list, resources/list and resources/templates/list all returned empty arrays on 2026-08-18. An undeclared capability returns error -32601, and none of these did. A prompt picker for this server will be blank.
The published endpoint's WWW-Authenticate header is misleading to strict clients. It appears on a successful HTTP 200. A client treating it as a gate will demand a sign-in the endpoint does not require.
Documentation freshness is a threshold, not a guarantee. Context7's refresh runs in the background on request, at one day for top-100 libraries and up to 45 days for everything outside the top 5,000; website-sourced libraries use a slightly higher threshold still. A niche library's documentation can be over a month old and the tools give no signal of its age.
Private libraries are never refreshed automatically. Context7 states this explicitly; updating one requires a manual refresh from its library page.
Your queries are stored and passed to third-party LLMs. Context7's data privacy page says client-formulated queries are sent to OpenAI, Google Gemini and Anthropic for reranking, and are anonymously stored for benchmarking. Disabling that storage is an Enterprise-plan control, and Context7 warns it may degrade retrieval quality.
Anthropic's directory records this connector as requiring authentication, which contradicts what its own published endpoint does. Documented above with both observations; we do not know which will change.
We did not call either tool. Our check was a read-only initialize, tools/list, prompts/list, resources/list and resources/templates/list handshake, plus a GET /ping. Every behavioural claim above comes from the server's own schemas and descriptions, or from Context7's published documentation.

Frequently asked questions

Does the Context7 MCP server require an API key?

No, not at the endpoint Anthropic publishes. Our anonymous handshake against https://mcp.context7.com/mcp on 2026-08-18 returned both tool definitions with no credential attached, and Context7's own client documentation says the standard endpoint works without a key at the anonymous rate limit. A key raises those limits and unlocks private repositories, but it is not needed to connect.

Why does Anthropic's directory say Context7 needs authentication?

Because Context7 runs two endpoints and the posture differs between them. The directory records auth_required for the connector, yet the URL it publishes answered our anonymous handshake with HTTP 200 on 2026-08-18. A second endpoint, the same host with /mcp/oauth, returned HTTP 401 and JSON-RPC error -32001 to the identical anonymous request. Both facts are real.

Why must you call resolve-library-id before query-docs?

Because query-docs takes a Context7 library ID that nothing else on the surface produces. Its required libraryId parameter expects the form /org/project, such as /vercel/next.js, and resolve-library-id is the tool that turns a package name into one. Context7 documents one exception: if you already know the ID, you can pass it straight to query-docs and skip resolution entirely.

What does Context7 send to its servers when my agent uses it?

Only the fields in the two tool schemas plus client metadata. Context7's data privacy page lists the query, the library name or ID, your API key if you supplied one, your MCP client name and version, the transport type, and an AES-256-CBC encrypted client IP used for rate limiting. It states your full prompts, source code and conversation history are never transmitted.

Is the documentation Context7 returns guaranteed to be accurate?

No, and Context7 says so directly. Its repository disclaimer states that projects are community-contributed, that it cannot guarantee the accuracy, completeness or security of all library documentation, and that projects are maintained by their owners rather than by Context7. It asks users to report suspicious content and says you use the service at your own discretion and risk.

How many free requests does the Context7 free plan include?

One thousand API calls a month. Context7's pricing page states that free users are blocked on reaching that monthly limit, and that twenty bonus calls are granted each day while blocked until the month resets. Pro is ten dollars per seat per month with five thousand included calls per seat, then ten dollars per additional thousand.

Are the Context7 MCP tools safe to auto-approve?

Both carry the full four-annotation set read live on 2026-08-18: readOnlyHint true, destructiveHint false, idempotentHint true and openWorldHint true. Neither writes anything and neither accepts a credential in its schema. The residual risks are context poisoning from retrieved third-party text and quota spend, not damage to anything you own.