Airefs MCP server
Connect Claude, ChatGPT, Cursor, or any other MCP client to your Airefs account and ask about your AI search visibility in plain language.
Ask Claude how your mention rate moved last month, which competitors showed up in answers where your brand did not, which sources keep getting cited in your category, and which discussions are worth joining this week. The answers come from your own Airefs account rather than from the model’s general memory of the internet, and you get them without opening the dashboard or exporting anything.
The Airefs MCP server is what connects the two. The Model Context Protocol (MCP) is a shared standard for plugging AI apps into outside services, in the way USB-C is one shape of plug that fits many devices. You add one URL to your assistant, sign in once, and it can read your Airefs data from then on.
What it covers
Your assistant can read mention rate, citation rate, and average mention position over time, broken out by prompt, by competitor, and by answer source. The whole Sources layer comes with it: the domains and URLs collecting citations, and the exact AI responses behind each one. If a number is on your overview, a tool can reach it.
The opportunities to move those numbers are covered too. Article recommendations arrive with the backlog and the pipeline they feed, discussions covers the threads AI answers are already citing, and backlinks is the outreach list plus the citation evidence behind each domain.
Two things the server does not expose: Impressions, the visits AI crawlers make to your pages, and Clicks, the visitors who arrive from an AI answer. Both live in the dashboard.
Connect
The server URL is https://mcp.getairefs.com/mcp. That is the only thing you need to copy.
Add it in your client, then sign in with your Airefs account in the browser tab that opens. There is no API key to copy anywhere: the sign-in hands your client short-lived tokens, which it stores and you can revoke. After you sign in, the connection reads what your account can read: your sites’ data plus your profile basics. Nothing more.
Works the same in Claude on the web and in Claude Desktop.
- Open Settings → Connectors.
- Click +, then Add custom connector.
Name it Airefs and paste
https://mcp.getairefs.com/mcpas the remote MCP server URL.- Click Add, then Connect.
- Sign in with your Airefs account in the window that opens and approve access.
Start a chat and mention Airefs in your question. If the tools do not appear, open the tools menu in the chat box and switch the Airefs connector on.
Custom connectors work on every Claude plan, but a free account can keep only one at a time, so remove another before adding Airefs. On Team and Enterprise plans only an owner can add the connector for the organization, under Organization settings → Connectors; members then connect to it individually.
Custom MCP servers live behind ChatGPT’s developer mode, which runs in the web app only and covers Pro, Business, Enterprise, and Edu. Plus does not support custom MCP servers. Pro accounts are limited to servers with read and fetch tools, which is all Airefs has.
On Pro you add it yourself:
Open Settings → Apps → Advanced settings and turn Developer mode on.
Go back to Apps and click Create.
Name it Airefs, paste
https://mcp.getairefs.com/mcpincluding the/mcppath, and choose OAuth as the authentication method.Click Scan Tools, sign in with your Airefs account in the window that opens, then click Create.
- Start a new chat and pick Airefs from the tools menu.
On Business only admins and owners can use developer mode at all, and each one turns it on for their own account. An admin creates the app from Workspace settings → Apps → Create, then publishes it from Drafts; ordinary members have no developer mode toggle and get Airefs once it is published. On Enterprise and Edu an admin grants developer access first, under Permissions & Roles → Connected Data, after which authorized members turn developer mode on in their own settings, but only admins and owners can publish for the workspace.
Register the server once from your terminal.
claude mcp add --transport http airefs https://mcp.getairefs.com/mcpRun
/mcpinside Claude Code and choose Authenticate forairefs. A browser window opens for sign-in.Run
claude mcp listto confirm the server is connected.
To share the server with everyone working in a repository, add the scope flag between the server name and the URL:
claude mcp add --transport http airefs --scope project https://mcp.getairefs.com/mcpEach person still signs in with their own Airefs account.
Add the server to .cursor/mcp.json in your project, or to
~/.cursor/mcp.json to use it everywhere.
{
"mcpServers": {
"airefs": {
"url": "https://mcp.getairefs.com/mcp"
}
}
}Save the file, then open Cursor Settings → MCP.
Click Login next to the Airefs server and sign in with your Airefs account.
- Ask about your Airefs data in the chat pane once the server shows as connected.
Add the server to .vscode/mcp.json in your workspace.
{
"servers": {
"airefs": {
"type": "http",
"url": "https://mcp.getairefs.com/mcp"
}
}
}Save the file and click Start above the server entry.
- Sign in with your Airefs account in the browser window that opens.
Open Copilot Chat in agent mode and pick the Airefs tools from the tools picker.
Commit the file so the whole team picks up the server. Sign-in stays per person, so nobody inherits anyone else’s access.
Any client that speaks streamable HTTP and supports OAuth can use the server directly. Give it
the URL https://mcp.getairefs.com/mcp, then complete the browser sign-in when the
client asks for it. There is nothing else to configure.
For clients that only run local servers, bridge the connection with mcp-remote,
which needs Node.js installed:
{
"mcpServers": {
"airefs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.getairefs.com/mcp"]
}
}
}On its first run mcp-remote opens a browser window for sign-in and remembers the
result, so later runs start without a prompt.
What your assistant can see and do
Every tool on the Airefs MCP server is read-only, without exception. An assistant can read your Airefs data and it can never change anything in your account. It cannot add or remove prompts, dismiss an opportunity, schedule an article, edit your competitor list, or touch billing. So the worst a bad question can do is read something you would rather not have shared, because everything a tool returns goes to your assistant’s provider and is then covered by that provider’s terms.
Sign-in happens through OAuth in your browser, using the Airefs account you already have. You never handle a long-lived key. The client stores the tokens it gets back, but they are short-lived and you can revoke them from Airefs whenever you want.
What the connection can reach is what your account can reach. That starts with your profile basics: name, email address, and organization memberships. It covers your sites’ visibility analytics and prompts, and the stored AI answer texts behind them.
It also includes competitor and source lists and article and backlink recommendations. Any brand, audience, or writing context you have configured is readable too.
If you belong to an organization, that means the organization’s sites; if you have one site, that means one site. Connecting a client does not widen your own access, and it does not expose other people’s sites to you. The privacy policy says the same thing in its own words.
To cut a client off, revoke it in Airefs. Open Settings → Account, find the Airefs MCP server card, and click Disconnect next to the client under Connected clients. That deletes its tokens, so it cannot ask for new ones, and the server stops answering it within a minute.
Then tidy up on the client side so the dead entry stops showing:
Claude: Settings → Connectors, then remove the Airefs connector.
Claude Code:
claude mcp remove airefs.Cursor and VS Code: delete the
airefsentry frommcp.json.
Doing only this second step is not enough on its own. It stops that copy of that client from asking, but the access it was granted is still live until you revoke it.
Plans and limits
MCP access is included on trial, so you can connect a client before you pay for anything. Trial accounts have tighter rate limits than paid accounts, which matters mainly for long analyses that page through a lot of rows.
Some data follows your plan the same way it does in the app. Google AI Overview is available as an answer source when your site has it enabled, and how far back analytics history goes depends on your plan. When a question falls outside what your plan covers, the tool returns a clear error saying so instead of quietly answering with less.
Recipes
The server ships six ready-made prompts. In Claude they sit in the plus menu next to the message box once the Airefs connector is on. Pick one and the assistant runs a whole procedure against your data instead of a single lookup.
Both fields a prompt asks for are optional. Leave the site field empty if your account has one site, or type the domain to choose. The focus field narrows the run in your own words: “last 14 days”, “Google AI Overview only”, “just the pricing tag”. Without a focus, prompts use ChatGPT as the answer source and a recent window.
Clients that do not surface MCP prompts can still ask for the same analysis. Every prompt below ends with a plain-language version to paste into a chat.
Weekly pulse
airefs_weekly_pulse compares this week with the one before it: how your mention rate and citation rate moved, where you stand against tracked competitors right now, which domains are collecting the most citations, and which article recommendations are active. It reads as a Monday-morning digest you can paste into a team channel. When a week has no completed data it says so rather than reporting a zero.
“Use Airefs to give me a weekly pulse for acme.com: how did my mention rate and citation rate move against last week, which source domains are cited most, and which article recommendations are active?”
Competitor radar
airefs_competitor_radar checks every active tracked competitor for real movement in mention rate or citation rate between two back-to-back periods, then separates the ones that moved from the ones that held steady and puts the current leaderboard underneath. Run it monthly, or in the week after you notice a competitor shipping something. Movement comes back in percentage points, and it never claims to know the cause.
“Use Airefs to compare each tracked competitor for acme.com this month against last month, and flag anyone whose mention rate or citation rate moved by five points or more.”
Visibility-drop investigation
airefs_visibility_drop_investigation takes a decline apart: the rate change itself, the prompts that deteriorated most with the responses behind them, which competitors moved the other way, and how the cited source domains shifted. Explanations come back sorted into supported, possible, and not testable, so you can tell evidence from a hunch. This is the one to reach for on the day someone asks why the number went down.
“Use Airefs to investigate why acme.com’s mention rate fell over the last two weeks: which prompts lost mentions, which competitors gained, and what changed in the cited sources?”
Source authority review
airefs_source_authority_review maps the sources behind your answers. It groups the cited domains and pages into your own, your tracked competitors’, and everyone else’s, then shows which domains are gaining citations and which appeared for the first time. Authority here means how often and how widely something is cited; Airefs has no third-party quality score and the prompt will not invent one. Worth running before you decide where to pitch a guest post or which publications to chase.
“Use Airefs to review the source domains cited for acme.com, split them into mine, competitors’, and third-party, and show which ones are gaining citations.”
Visibility gaps
airefs_visibility_gaps lists the prompts where your brand is never or rarely mentioned across a recent stretch of executions, grouped by country and tag. Your brand context does the sorting: prompts outside what you sell land in expected misses, everything else lands in the list worth fixing, and active article recommendations get matched to the gaps they address. Run it when you are planning the next quarter of content.
“Use Airefs to list the prompts where acme.com is never or rarely mentioned, group them by tag, and tell me which active article recommendations address them.”
Action plan
airefs_action_plan is the “what do I do about it” prompt. It pulls current visibility, gap prompts, article recommendations against the content pipeline, cited discussions alongside monitored Reddit threads, and backlink opportunities into one prioritized list built around three moves: publish the recommendation-backed articles, join the discussions already being cited, and earn citations on the domains those answers already trust. Start a sprint with it and work down the list.
“Use Airefs to build an action plan for acme.com: what should I publish, which discussions should I join, and which domains should I pursue for backlinks?”
Longer questions to paste
The prompts above cover the usual jobs. When you want to steer the analysis yourself, or your client has no prompt menu at all, paste one of these and swap in your own domain.
Investigate a visibility drop
A drop deserves evidence before it gets a story, so this asks for the decomposition first.
Use Airefs for acme.com. Our mention rate is down and I have to explain it
tomorrow morning.
Compare the last 14 days with the 14 days before that on ChatGPT. Show me
the prompts that lost the most brand mentions, whether any tracked competitor
gained over the same period, and whether the domains cited for those prompts
changed.
Be clear about what the data supports and what it doesn't.Find discussions worth joining
Discussions that already appear as cited sources are the ones AI answers are reading. Asking for the citing prompt alongside each URL tells you what to actually write in the thread.
Use Airefs for acme.com. I have about an hour this week to reply in places
that AI answers actually cite.
List the discussion URLs that already show up as cited sources, and separately
the Reddit threads Airefs is monitoring. Drop anything where we're already
mentioned or that's marked done. For each one left, tell me which prompt it
was cited for so I know what angle to write from.Build a backlink outreach shortlist
Backlink opportunities are the third-party domains your answers already cite, with your own site and tracked competitors filtered out. Pulling their cited pages in the same question saves you a research pass before you write.
Use Airefs for acme.com. I'm building an outreach list for next month.
Show me the backlink opportunities ranked by how often those domains are
cited, and leave out anything already marked emailed or dismissed. For the
top ten, list the pages of theirs that get cited so I can see what they
publish about before I write the email.Prepare a competitor report
Handy the week before a marketing review. The last line matters: without it, assistants tend to narrate reasons the data cannot support.
Use Airefs for acme.com. I need a one-page competitor read for our monthly
marketing review.
For each tracked competitor: current mention rate and citation rate, the
change since the previous month, and where we sit in that ranking. Then show
which of their pages are cited in the answers we track.
Keep it factual. No theories about why anything moved.First questions to try
Three short ones, for when you have just connected a client and want to see something come back:
- “Use Airefs to summarize my current AI visibility and compare it with active competitors."
- "Which prompts rarely mention my brand, and which article recommendations should I publish?”
“Show me the cited discussions and backlink domains where my brand has the clearest opportunity.”
Troubleshooting
My assistant can't find my site
Ask it to list the Airefs sites you have access to. It will name each one exactly as Airefs stores it, which is usually the domain. Use that name, or the domain on its own, in your next question. If your site is not in the list, the Airefs account you signed in with does not have access to it. Check that you signed in with the right account, and ask an admin on your team to add you to the site if you belong to an organization.
A question about Google AI Overview data returned an error
Google AI Overview is a separate answer source, and it is enabled per site. When it is off, the tools say so rather than mixing in ChatGPT numbers. Ask the same question about ChatGPT, or see Plans & pricing to enable the answer source.
A request for a long stretch of history can fail the same way, because analytics history depth follows your plan. Ask for a shorter window and the same question works.
The connection expired and I need to sign in again
Sign-in does not last forever. When your assistant reports that it is not authorized, reconnect
from the client: in Claude, open Settings → Connectors and click
Connect on the Airefs connector; in Claude Code, run /mcp and
authenticate again; in Cursor and VS Code, use the sign-in prompt on the server entry. Nothing
needs resetting on the Airefs side.
My assistant says it's rate limited
The server limits how fast one account can call it. The error carries a suggested wait, and retrying after that wait usually works. Broad questions hit the limit sooner because they page through more data, so narrow the question: one site, one answer source, a shorter date range. Trial accounts have tighter limits than paid ones.
I can't add the connector in Claude
On the free Claude plan you can keep one custom connector at a time, so remove the one you have
before adding Airefs. On Team and Enterprise plans, an owner or primary owner has to add the
connector for the organization first; until then members will not see it as an option. Claude
connects from Anthropic’s cloud, so the server has to be reachable over the public internet,
which https://mcp.getairefs.com/mcp is.
The assistant answers without using Airefs
Most clients only reach for a tool when the question makes it obvious. Say “use Airefs” in the question, or name what you want by its Airefs term: mention rate, prompts, answer sources, competitors, discussions. Check the tools menu in your client too, since some clients leave a newly added server switched off in existing chats.
The numbers don't match the dashboard
Check the date window and the answer source first. A different window or a different source
legitimately gives a different number, and both sides can be right. Granularity is worth checking
as well: get_visibility_timeseries at weekly granularity counts a prompt as mentioned
if any execution that week mentioned you, which is not the same arithmetic as a per-batch rate.
If those all line up and the gap is still there, ask the assistant which tool it called and what parameters it used. An assistant that cannot say is guessing rather than reading.
Want to know exactly what an assistant can reach before you connect? The tools reference lists every tool on the server, what it returns, and its key parameters.
