Context7 MCP Server

MCP detected

Details

Endpoint: https://mcp.context7.com/mcp
Transport: streamable-http
Docs: https://context7.com/docs/resources/all-clients

Authentication

Context7 API key api_key discovered Get key ↗

CONTEXT7_API_KEY: <credential>

Create an account in the Context7 dashboard, open Create API Key in the API Keys card, name the key, and copy it immediately; keys are only shown once. The key format is ctx7sk-.... See Manage API Keys and the API Guide.

OAuth 2.0 oauth2 discovered

OAuth · resolves from well-known metadata

OAuth 2.0 — self-onboarding

Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.

Context7 API key api_key declared Get key ↗

CONTEXT7_API_KEY: <credential>

Create a free account at context7.com/dashboard and generate an API key. Search and docs endpoints also work anonymously at low rate limits, but a key is required for higher rate limits, some endpoints (e.g. adding libraries), and private repositories. On the REST API send it as Authorization: Bearer <key>; on the MCP server send it as a CONTEXT7_API_KEY header; for the CLI run ctx7 login or ctx7 setup --api-key <key>. See the API guide.

Context7 OAuth oauth2 declared

OAuth · resolves from well-known metadata

MCP clients can authenticate interactively via OAuth 2.0 instead of an API key. Discovery is standard: the MCP endpoint publishes RFC 9728 metadata at https://mcp.context7.com/.well-known/oauth-protected-resource, pointing at the authorization server https://context7.com (RFC 8414 metadata at /.well-known/oauth-authorization-server). See Set Up OAuth.