Use Ahrefs 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.

Ahrefs MCP OAuth authorization Use an MCP-compatible client and connect it to https://api.ahrefs.com/mcp/mcp. Ahrefs documents an interactive consent flow where the client redirects you to log in to Ahrefs, choose a workspace, and click Allow. For ChatGPT's MCP connector, Ahrefs explicitly says to choose Authentication: OAuth and leave OAuth Client ID and Client Secret blank, indicating the client self-onboards for the remote server. After approval, the connection appears in your Ahrefs account with a dedicated API key tagged with MCP scope.

Ahrefs API key In Account settings / API keys, create an API key for Ahrefs API v3. Only workspace owners and admins can create and manage keys. Send it as Authorization: Bearer YOUR_API_KEY. The docs note keys expire after 1 year and can be limited per key in the same page.

Ahrefs MCP key In your Ahrefs account, manually generate an MCP key and use it in your AI agent's configuration. Ahrefs says MCP connections can also appear with a dedicated API key tagged with MCP scope, and workspace admins can manage limits in the API keys report.