Use Context7 through Slack with Giga.

Structured tool access via the Model Context Protocol.

OAuth 2.0

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 OAuth 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.

Context7 API key Create an account in the Context7 dashboard, then open the API Keys card and click Create API Key. Copy the key immediately; the docs say keys are shown only once and look like ctx7sk-.... Use it as Authorization: Bearer <key> for the REST API, as the CONTEXT7_API_KEY header for the hosted MCP server, or authenticate the CLI with ctx7 login / npx ctx7 setup --api-key <key>. See Manage API Keys and the API Guide.

Context7 API key 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.