Included as an SEO and web-intelligence surface whose API and hosted MCP expose backlinks, organic and paid search, keyword research, SERPs, Rank Tracker, Site Audit, Brand Radar, Web Analytics, GSC Insights, and social-media reporting, with selected project and list management reserved to the public API.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Sites, domains and URLs; backlinks and referring domains; organic and paid keywords and pages; keyword ideas and metrics; SERP results; Rank Tracker and Site Audit projects; Brand Radar prompts, responses, mentions, citations, and reports; Web Analytics dimensions; GSC data; social channels, posts, activity, and metrics; workspace limits and API keys.
Query Site Explorer, Keywords Explorer, SERP Overview, Rank Tracker, Site Audit, Batch Analysis, Brand Radar, Web Analytics, GSC Insights, and Social Media endpoints that are marked for API or MCP use; inspect subscription limits and workspace project metadata.
Through the public API, create, update, or delete supported Rank Tracker projects, keywords, tags, competitors, Keyword Explorer lists, Brand Radar prompts or reports, and social posts where the endpoint permits it. Do not assume those mutations exist in hosted MCP: the reference marks project creation, access updates, and deletion as API-only while marking project reads API+MCP.
Hosted MCP uses an authorization consent flow that creates a dedicated workspace API key tagged with MCP scope; users may also supply a manually created MCP key, and Enterprise customers may use API keys. Public API calls use a bearer API key created by a workspace owner or admin; keys expire after one year and are invalidated if their creator leaves the workspace.
Show the workspace, endpoint availability label, requested fields, filters, row limit, estimated or actual API-unit cost, and key-level monthly ceiling. Route API-only mutations through a separately approved integration and never use the external MCP URL as an ad hoc JSON-RPC or scripting endpoint.
Hosted MCP requires a paid Lite plan or higher, inherits the plan's maximum rows per request and monthly API-unit allowance, and charges third-party calls against that allowance. The external MCP endpoint is not a general-purpose programmatic API and may not be used through custom scripts, bridges, or standalone HTTP clients. The public API defaults to 60 requests per minute and can also return dynamic 429 throttling.
Agent access
Support: Official MCP server
Read scope: Use endpoint-backed MCP actions for backlink and organic-search analysis, keyword and SERP research, project and audit inspection, Brand Radar and AI-visibility analysis, Web Analytics, GSC Insights, Batch Analysis, and social reporting when the reference labels the endpoint API+MCP.
Write scope: No hosted-MCP mutation is claimed in this packet. Ahrefs documents public API writes for management and social objects, but representative project create, update, and delete endpoints are explicitly labeled API-only; use the endpoint's API+MCP or API-only badge as the action boundary.
Authentication: Remote-client authorization presents Ahrefs consent and creates an MCP-scoped key in the chosen workspace; a manually generated MCP key is also supported, and Enterprise can use its API keys. The recommended streamable-HTTP endpoint is `https://api.ahrefs.com/mcp/mcp`; legacy SSE remains available but is deprecated in many clients.
Approval boundary: Keep MCP analysis and public-API mutation as separate modes. Before an API-only change, show workspace, target project or list, endpoint, payload, cost classification, and whether the operation creates, updates, publishes, or deletes; never translate an MCP read result directly into a management call without confirmation.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Ahrefs ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Official Ahrefs developer docs and hosted endpoint confirmed; supports OAuth/workspace selection or MCP keys depending client.
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
