Key takeaways
- Promptwatch's MCP is built for AI visibility work: citations, prompts, fan-outs, content gaps and content generation. It has no backlink or keyword database.
- Semrush and Ahrefs MCPs are API-unit-metered gateways into huge traditional SEO datasets (keywords, backlinks, traffic). They are the better choice for classic research.
- Ahrefs puts its AI search data behind the Brand Radar add-on, so AI-focused MCP prompts cost extra on top of a base plan. Semrush's coverage of its AI Visibility Toolkit through MCP is something to verify before you buy.
- Unit burn is the biggest practical risk with Semrush and Ahrefs. A looping agent can eat a month of allowance in an afternoon.
- Most serious teams will end up running two of these side by side: one for AI visibility, one for classic SEO data.
What an SEO MCP server actually does
The Model Context Protocol lets an AI client such as Claude, ChatGPT or Cursor call a tool directly and get structured data back. No CSV exports, no pasting screenshots into a prompt. You ask a question, the agent picks a tool, the tool returns rows, and the model reasons over them.
By mid-2026 every major SEO vendor ships an official MCP, and a Nightwatch roundup of SEO MCP servers counts dozens of options overall. That makes the question less "should I connect one?" and more "which dataset do I actually want my agent reasoning over?"
That is where these three diverge. Two of them sit on top of decade-old link and keyword indexes. One sits on top of AI answer tracking. They solve different problems, and I think comparing them as direct substitutes is the wrong framing. Still, people ask, so here is how they line up.
The three servers at a glance
| Promptwatch MCP | Semrush MCP | Ahrefs MCP | |
|---|---|---|---|
| Core data | AI visibility, citations, prompts, fan-outs, content gaps, crawler analytics | Keywords, domains, traffic, competitors, trends | Backlinks, keywords, organic traffic, site data |
| AI search data | Native, the whole point | Marketing page mentions AI search data; exact endpoint coverage unconfirmed | Requires Brand Radar add-on |
| Write or generate tools | Yes (monitors, prompts, content creation) | Mostly read and research, plus project tools | Read-only research |
| Metering | Tied to your plan and API key | API units | API units |
| Auth | API key or OAuth | OAuth default, API key option | OAuth or key |
| Clients | ChatGPT, Claude, Cursor and others | Claude, Claude Code, Copilot, ChatGPT, Cursor, VS Code, Perplexity, Lovable, Notion and more | Claude, ChatGPT, Copilot, Lovable, n8n and others |
| Best for | GEO and AI SEO execution | Broad keyword and competitor research | Backlink and search-first research |
Promptwatch MCP
Promptwatch is an AI search visibility and GEO platform, and its MCP exposes that data to your assistant. It is an official plugin in the ChatGPT store and an official connector in the Claude directory, so setup is mostly a click-through rather than a config-file exercise. The MCP documentation lists use cases like querying brand visibility across ChatGPT, Claude, Gemini, Perplexity and AI Overviews, analyzing citation sources, tracking AI-referred traffic, comparing competitors and finding content gaps.
What the tools cover
The tools reference groups things sensibly. Going by the docs (my copy of the page was truncated after the content tools, so there may be more):
- Projects and models, including
setupProject, which creates a project, enriches it from your site and generates up to three monitors with prompts. - Monitors and prompts: create, update, delete, activate, tag, bulk create.
- Visibility and sentiment time series, plus heatmaps across brands, models, topics and countries.
- Citation analysis:
getCitations,getSelfCitationFrequency,getCitationDomainsOverTime,getCitationRankAnalysis,getCitationTopPages,getCitationDomainsByLlm. - Page tracker, which watches up to 100 URLs and lists the prompts and responses citing each one.
- Response and competitor data via
getResponseandgetTopCompetitors. - Content:
getContentGapRecommendations,listQueryFanoutsandcreateContent, which generates or refreshes content.
The difference from the other two is the last bullet. An agent connected to Promptwatch can go from "which prompts are we missing?" to "draft the article" inside one conversation. Semrush and Ahrefs hand you research. Promptwatch also hands you the next step.
Why fan-outs matter in an MCP
Query fan-outs are the sub-searches an AI model runs behind a single prompt. Promptwatch Data's ChatGPT query fanout report shows the averages are lower than the folklore suggests: about 2.15 fan-outs per response in early December 2025, about 1.84 by early March 2026, then 1.0 when the data resumed in April. Average query length also fell, from roughly 117 characters to about 53 from April. The "3 to 8 searches per prompt" figure you see quoted is a ceiling, not an average.
Why do I care in an MCP context? Because an agent that can pull the actual sub-queries can build an outline around them rather than guessing. ChatGPT also started using the site: operator at scale in August 2026, per Promptwatch Data, which changes what those sub-queries look like. This is the kind of thing a live data connection catches and a static keyword export does not.
Crawler data you will not find elsewhere
Promptwatch also tracks IP-verified AI crawler traffic. In Promptwatch Data's crawler report (June 8 to September 6, 2026), OpenAI accounted for 79.8% of verified AI crawler requests in the week of Aug 31 to Sep 6, down from 94.8% in the week of Jun 8 to 14. Only requests from the operator's published IP ranges count, so spoofed user agents are excluded. I found nothing equivalent in the Semrush or Ahrefs MCP docs.
Limits
It does not replace a backlink index or a 28-billion-keyword database. If you ask it for link prospects, you are using the wrong server. Also, because some tools create, update or delete, you should gate those in your client. The tools carry readOnlyHint, destructiveHint and idempotentHint annotations, so most clients can prompt for approval. I could not confirm which plan tiers include MCP from the docs, so check promptwatch.com/pricing before committing.
Semrush MCP
Semrush runs a remote server at https://mcp.semrush.com/v2/mcp, and the official docs have setup guides for an unusually long list of clients: Claude, Claude Code, Microsoft Copilot, ChatGPT, Cursor, VS Code, Perplexity, Lovable, Notion and a few others. If your team is split across assistants, that breadth matters.
What it is good at
The example prompts in the docs are traffic and competitor lookups, such as pulling domain lists for an industry or asking who is winning traffic among streaming services in Germany. Per Nightwatch's rundown, it draws on Semrush's 28.3 billion keyword database across 142 regions, with a triple-API setup covering core SEO, Trends and Projects. Bulk domain analysis, low-competition keyword discovery and keyword clustering all work from a prompt.
There is also a Semrush One review video floating around, sponsored by Semrush, that demos the MCP inside a code editor pulling market data into finished content. Treat it as a demo, not a benchmark.
The AI visibility question
Semrush's marketing page says the MCP brings in AI search data. What I could not confirm is which AI Visibility Toolkit endpoints are exposed. Before you assume parity with a dedicated GEO tool, ask Semrush support, or run a test prompt about ChatGPT citations on a trial. Do not buy on the assumption.
Access and cost
There is no separate MCP fee. The server spends your account's API units. According to a third-party reading of Semrush's pages dated October 22, 2026:
- Semrush One Starter, Semrush One Pro+, SEO Classic Pro and SEO Classic Guru are named in the docs as including 50,000 API units.
- SEO Classic Business and Semrush One Advanced can use MCP only with a separately bought API units package (2M, 5M, 10M or 20M units), and the package prices are not published.
- Monthly prices on the pricing page (billed annually): SEO $139 ($117.33), Starter $199 ($165.17), Pro+ $299 ($248.17). Advanced showed as custom.
- The docs and the pricing page disagree on whether the $139 SEO plan includes MCP. Confirm with support first.
- Typical costs: keyword overview is 10 units per line, related keywords 40 units per line. Unused units expire at renewal.
Older articles quote Pro $139.95, Guru $249.95 and Business $499.95, plus a $99 AI Visibility Toolkit. Those are legacy names and numbers. Use the current page.
Ahrefs MCP
Ahrefs' getting-started article (dated September 22, 2026) makes the rules refreshingly clear. MCP is available on Lite and above, with no extra fee for the MCP itself.
| Plan | Monthly API units | Max rows per request |
|---|---|---|
| Lite | 200,000 | 100 |
| Standard | 800,000 | 250 |
| Advanced | 2,000,000 | 500 |
| Enterprise | Custom | Unlimited |
Every call costs at least 50 units, and cost rises with complexity. Units are shared across the MCP, Ahrefs Connect and direct API v3, so a script that already hits the API is competing with your agent. Extra units are only sold via Enterprise; otherwise you upgrade. You can watch usage at app.ahrefs.com/account/limits-and-usage. A 401 error usually means an expired key or inactive plan.
The Brand Radar catch
AI-visibility prompts, such as AI Overviews sentiment over time, need the Brand Radar: AI Overviews & AI Mode Platform add-on. So the MCP is cheap to try, but the AI data is not included. Pricing for Brand Radar varies by source: some quote $398/month for selected platforms and $699 for all platforms, and a snippet from Ahrefs' pricing page shows "from $199/mo". These conflict, and I did not verify the current page, so check it yourself.
Where it shines
Backlink data. Nobody else in this comparison has it at that depth, and an agent that can pull link profiles, referring domains and keyword rankings in one conversation saves a lot of tab-switching. The 100-row cap on Lite is a real annoyance for bulk work, though.
Cost and pitfalls compared
| Issue | Promptwatch | Semrush | Ahrefs |
|---|---|---|---|
| Metering | Plan-based; confirm MCP tier | API units, expire at renewal | API units, shared with API |
| AI data included? | Yes, native | Unconfirmed via MCP | Only with Brand Radar add-on |
| Row or size caps | Per-tool | Unit cost per line | 100 rows on Lite |
| Plan confusion | Low | High (Advanced needs units package) | Low |
| Risky tools | Write and delete tools, gate in client | Heavy bulk tools slow in loops | Credit burn in loops |
The general advice applies to all three: start with strict limits, watch a few agent runs, then loosen. Also prune your tool list. If one client connects to four MCPs each exposing 50-plus tools, the agent's tool selection gets worse.
Which should you pick?
You do GEO or AI search work day to day
Promptwatch. It is the only one of the three where the whole server is about AI visibility, and it can write and refresh content from the gaps it finds. The weekly loop of "find gaps, draft, publish, check citations" is easier when one connection covers it.
You do traditional keyword and competitor research
Semrush, especially if you need one MCP that works in Claude and ChatGPT and a wide range of other clients. Budget for API units and read the plan fine print.
You live in backlinks
Ahrefs. Add Brand Radar only if you need AI data from the same vendor and accept the price.
You want both worlds
Run two. A common stack is Promptwatch for AI visibility plus Ahrefs or Semrush for link and keyword data, and add the free Google Search Console MCP, which grounds every prompt in your own site's data. Google rankings still drive a big share of AI citations, so skipping Search Console is a mistake. Other AI visibility tools exist too, and the GEO software directory at bestgeosoftware.com is a decent place to compare them.
Nightwatch, which publishes its own MCP covering rank tracking and AI visibility, is worth a look if you want a single mid-priced connection, though it is a different product from the three here.
A practical first-week test
- Connect one server at a time and run the same three prompts: a competitor gap, a citation question and a content brief.
- Note how many units or credits each run consumes.
- Check whether the answer used real data or filled in from the model's memory. If a tool returns nothing for AI visibility, you have your answer about coverage.
- Turn on approval prompts for anything that writes or deletes.
- After a week, drop whichever server your agent barely calls.
Bottom line
These servers are not interchangeable. Semrush and Ahrefs give your agent a big library of traditional SEO facts, metered by units. Promptwatch gives it a live view of how AI engines talk about you, plus the tools to act on it. If AI search is the channel you are trying to grow in 2026, start with Promptwatch and add a classic SEO MCP only for the data it lacks. Verify pricing on each vendor's own page before buying, because Semrush and Ahrefs both changed plan details within the last few weeks.