Context7
Up-to-date docs for AI agents
Docs checkedRemote Streamable HTTP · Metadata observed 2026-10-24
Connect Context7
Choose manual setup
Add https://mcp.context7.com/mcp as a remote MCP server in your client.
Publisher instructions ↗Add a Context7 API key
Get a key from the Context7 dashboard for higher rate limits. For manual setup, configure Authorization with Bearer followed by your API key.
Publisher instructions ↗Use the client setup instructions
Save the connection and initialize it in your client. Alternatively, the publisher’s ctx7 setup helper signs in through OAuth, creates a key and installs the selected integration.
Publisher instructions ↗
Connection address
https://mcp.context7.com/mcpUse this address when adding the remote connection to your MCP client.
Credentials and access
API key recommended; manual setup uses an Authorization bearer header.
Setup notes from publisher documentation
- The publisher confirms https://mcp.context7.com/mcp for manual setup.
- An API key is recommended for higher rate limits. Manual configuration uses Authorization: Bearer YOUR_API_KEY; do not interpret the key recommendation as proof every request requires authentication.
- The ctx7 setup helper signs in through OAuth and generates an API key. That helper flow is distinct from the manual remote-header configuration.
Registry configuration snapshot (1 inputs)
Configure these in your MCP client. This page does not collect credentials. Requiredness and secret flags below come from the Registry snapshot; publisher notes above can clarify alternative setup paths.
No required inputs are declared in this connection’s metadata. Other setup requirements may still apply.
Other declared inputs (1)
Authorization Requiredness not asserted · SecretAPI key for authentication. Accepts "Bearer <key>" or the raw key.
Registry definition:/remotes/0/headers/0Sources & review
Documentation checked 2026-10-23. Remote URL and manual authentication instructions checked. Anonymous access and tool execution were not tested.
Registry inputs are a dated snapshot. Publisher checks are separate, scoped observations. The downloadable bundle preserves the original draft plus the documentation review; it is not a ready-to-run client configuration.
Inspect the source binding
io.github.upstash/context7
Connection: /remotes/0
SHA-256: 7e24a291db28ffead8d29cd6fc4abbc46ff179df833eef45709d533ae3ed77f6