Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Up-to-date library docs for coding agents.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
Context7 is a documentation retrieval server for coding agents, operated by Upstash. Two read-only tools resolve a library name to a Context7 ID, then query that library's current documentation and code examples. It covers indexed open-source libraries rather than your own code, and the published endpoint answered our anonymous handshake without a credential.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
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.
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.
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.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.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.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.
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.
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.
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.
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.
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.
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.
overview.md). This is the exact documentation value in Anthropic's directory entry, and it resolves without redirect. Source for the product framing and the use context7 prompt convention. · retrieved 2026-08-18Authorization: Bearer header form, the /mcp versus /mcp/oauth endpoint choice, and the statement that the standard endpoint works without an API key at the anonymous rate limit. · retrieved 2026-08-18/mcp/oauth, the stdio exclusion, and the warning that most clients need explicit authentication after setup. · retrieved 2026-08-18llms.txt, npm and uploaded sources; the two version-pin syntaxes; the anonymous-versus-keyed rate-limit tiers; and the 429 response headers including Retry-After. · retrieved 2026-08-18use context7, the library-ID shortcut, and version matching. · retrieved 2026-08-18/ping health check, the 401 guidance naming Authorization: Bearer and the ctx7sk key prefix, and the recommendation to prefer the remote endpoint over local npx. · retrieved 2026-08-18docs-researcher agent, /context7:docs command — the context7-marketplace install route, and the note that the plugin works anonymously when no key is exported. · retrieved 2026-08-18Accept: text/markdown, and the target of a 307 from https://context7.com/docs/plans-pricing.md). The sole source for every price and quota on this page: the free tier's 1,000 monthly API calls and 20 daily bonus calls while blocked, Pro at $10 per seat with 5,000 included calls, $10 per additional 1,000, and private-repo parsing at $5 per 1M tokens. · retrieved 2026-08-18upstash/context7 repository (README retrieved 2026-08-18, HTTP 200; repository metadata via the GitHub API confirms an MIT licence and an active push the same day). Source for the two tool names with their required parameters, and for the accuracy disclaimer quoted in Limits. Note the README's own scope statement: the repository hosts the MCP server's source only, while the API backend, parsing engine and crawling engine are private. · retrieved 2026-08-18https://context7.com/llms.txt, https://context7.com/docs/llms.txt and https://context7.com/.well-known/integrations.json (all retrieved 2026-08-18, HTTP 200). The docs index drove every fetch above. integrations.json declares the MCP surface's auth status as required with a CONTEXT7_API_KEY header, which is the machine-readable half of the header disagreement noted on this page. · retrieved 2026-08-18https://mcp.context7.com/mcp — anonymous initialize returned HTTP 200, protocol 2025-06-18, server Context7 4.0.1, capabilities prompts, resources and tools each with listChanged: true, plus an instructions block; tools/list returned two tools with full descriptions, input schemas and four-hint annotations; prompts/list, resources/list and resources/templates/list each returned an empty array (2026-08-18). The 200 response carried WWW-Authenticate: Bearer resource_metadata=.... GET https://mcp.context7.com/ping returned {"status":"ok","message":"pong"}. Tool schemas committed at docs/marketing/data/tool-schemas/context7.tools.json. · retrieved 2025-06-18initialize against https://mcp.context7.com/mcp/oauth returned HTTP 401 with JSON-RPC error -32001 "Authentication required" (2026-08-18). https://mcp.context7.com/.well-known/oauth-protected-resource returned HTTP 200 naming authorization server https://context7.com and scopes profile and email; https://context7.com/.well-known/oauth-authorization-server returned HTTP 200 with the RFC 8414 metadata. Under this catalogue's rule an RFC 9728 descriptor is the server's own statement, so the OAuth path is verified — and so, separately, is the published endpoint's anonymous success. · retrieved 2026-08-18privacy_policy value in Anthropic's directory entry, and the Context7 Addendum at . Both returned HTTP 200 as PDFs on 2026-08-18 and were confirmed reachable but not parsed; we make no claim about their contents. · retrieved 2026-08-18prompt_names: [] and both tool names, read from our committed directory snapshot dated 2026-08-16. It records the connector as added 2026-02-06. · retrieved 2026-08-16Connect Context7 once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.