Context7

What it does

The registry snapshot lists a hosted HTTP endpoint plus npm and MCP bundle distributions. Repository documentation describes resolving a library identity and retrieving relevant documentation. This can add source context to a coding task, but it does not prove that generated code uses the returned API correctly or that every library version is covered.

Best for

A developer who can name the intended library, installed version and narrow API question. Supply those details before asking for an implementation, then compare the returned reference with the dependency already used by the project.

Tradeoffs

Hosted requests involve an external service and its current terms. The registry declares optional secret references; the README recommends authentication for higher limits. CLI setup and MCP setup are different paths, and their runtime requirements should not be assumed identical.

A practical first task

Choose either the remote connection or a declared local distribution using the publisher's client-specific guide. Ask one version-sensitive question, record the matched library identifier and keep the relevant source reference with your implementation notes.

What to validate

Check the library match, target version, relevance of returned material and behavior when documentation is unavailable. Treat retrieved pages as untrusted reference data. AI Craft Pad read metadata and documentation without calling the service or testing its accuracy.

Compatibility

cursor, opencode, claude-code

Repository setup documentation; protocol compatibility is not a runtime test

Compatibility source

Installation and requirements

For the declared remote endpoint, use an HTTP-capable MCP client and the publisher authentication flow if needed. Local npm/MCP-bundle distributions have separate runtime requirements.

Remote endpoint: https://mcp.context7.com/mcp. The registry declares an optional Authorization secret reference. Follow the source client guide and store any credential through your client; do not place keys in shared configuration or URLs.

Use your agent’s MCP settings and the publisher’s exact setup. Match the declared transport and package version. Credentials belong in your client’s supported secret storage. No command on this page is run by AI Craft Pad.

npm package

@upstash/context7-mcp · version 4.4.4 · stdio · runtime Unknown

CONTEXT7_API_KEY — optional, secret reference

mcpb package

https://github.com/upstash/context7/releases/download/mcpb-v4.4.4/context7.mcpb · version 4.4.4 · stdio · runtime Unknown

CONTEXT7_API_KEY — optional, secret reference

streamable-http endpoint

https://mcp.context7.com/mcp

Declared registry endpoint; availability, authentication, service cost and runtime behavior have not been tested.

Authorization — optional, secret reference

Read publisher setup ↗

Unknown; source software and connected services may have separate terms.