Ahrefs MCP Kit
Bearer-token caller for the Ahrefs MCP, with measured tool costs
Calls the official Ahrefs remote MCP with a bearer token instead of an OAuth round trip, so scheduled jobs keep running unattended. Ships what the pricing page does not tell you: the real unit cost of each of the 41 tools, measured across 1,102 calls. Needs only bash, curl and python3.
What it solves
Ahrefs documents its cost model in one line: rows times fields, minimum fifty units per billable request. That is accurate and almost useless for planning, because it tells you nothing about which of the forty-odd tools is going to eat your month. In our own use, three of them accounted for 78 percent of the spend.
How it works
Two parts. A bearer-token caller for the official Ahrefs remote MCP server, and the part that is genuinely hard to find anywhere else: what each tool actually costs, measured across 1,102 real calls rather than estimated from the pricing page. The measurement is the point. Everything else in the repository exists to make it reproducible.
When to use it
Read the cost table before you write the first script against the Ahrefs API, not after the first invoice. If you are planning a recurring job, it tells you which tool to build it on and which one to avoid at that frequency.
When not to use it
The numbers are our measurement on our account with our query shapes. Rows times fields means your cost depends on what you ask for, so treat the table as a ranking and an order of magnitude, not as a price list. It also needs an Ahrefs key with MCP scope, which is to say it needs a subscription.
Stars
★ 0
Clones (14d)
⊟ 6
Language
Shell
Updated
2026-08-12