Claude AirOps connectorWhat Claude can do in your AirOps account.
The Claude AirOps connector exposes 12 tools. 11 read your Brand Kits, tracked prompts and page metrics, 0 write, 1 is described nowhere. Below: what Claude pulls from AirOps, what it needs on the AirOps side, and where the publisher and Anthropic disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your content and SEO team
Instead of opening AirOps dashboards to see whether answer engines mention your brand, you ask Claude. AEO, short for answer engine optimization, is what AirOps tracks: how your brand shows up in AI search answers. Claude picks the right tool, pulls the figures and explains them in the conversation.
Know where you stand in AI answers. query_analytics answers custom questions over your AEO analytics with the metrics, dimensions and filters you pick, and on web and desktop AirOps can draw them as charts inside the chat.
Find the pages worth reworking. list_pages puts AI search, Search Console and GA4 figures side by side, then get_page_prompts shows which tracked questions cite a given page.
Brief writers with the real brand rules. get_brand_kit and list_personas bring back tone, identity and audiences before anyone drafts, so a freelancer starts from the same rules as the in-house team.
What it will not do, by default: the directory sheet only exposes reading. AirOps's own docs describe brand updates and other write tools, but none of them are on the sheet. Nothing runs by itself either: no alert fires when a citation drops. For scheduled monitoring, an automation tool does that job; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will meet while plugging AirOps in.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory lists them by name.
- Authorization
- The sign-in screen of the service itself, where you hand Claude the access it will use. Given once per person, revocable anytime.
- Approval
- The confirmation Claude waits for before it finishes an action that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as AirOps.
Connect AirOps to Claude in three steps
- 01
Find AirOps in Claude
In Claude's settings, open Customize, then Connectors, and look for AirOps in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector first so each member can sign in.
- 02
Start the connection
Click Connect on the AirOps row, then sign in with your AirOps account in the window AirOps opens itself. If the link breaks later, use Disconnect and connect again.
- 03
Read the authorization screen
Go through AirOps's access screen before approving. It belongs to the service, not to Claude, and it sets what the access covers. You can withdraw that access later from the AirOps side as well.
The 12 Claude AirOps connector tools, sorted by what they do
AirOps gives Claude 12 tools: 11 that read your account, 0 that change something in it, and 1 no official source describes.
Two groups here: what Claude reads, and what no official source describes. Names stay exactly as Claude shows them.
- 11 read
- 1 not documented
What Claude reads (11)
11 toolsEleven tools that look at your AirOps data without touching it.
list_workspaces
Lists the AirOps workspaces you can access, with each one's ID, name, slug and subscription tier.
list_brand_kits
Returns every Brand Kit you can reach, each flagged to show whether brand management and AI search tracking are switched on for it.
get_brand_kit
Opens a single Brand Kit and brings back its brand identity, its style guide and the entities attached to it.
list_personas
Lists the personas configured on a Brand Kit, the reader profiles your content is meant to address.
list_topics
Returns the topics set up for a Brand Kit, the themes AirOps tracks for that brand.
list_aeo_prompts
Lists the AI prompts tracked for a Brand Kit, meaning the questions AirOps asks answer engines to see whether your brand comes up.
get_prompt_answers
Fetches what the AI engines replied to one tracked prompt, so you can read the actual answers rather than a score.
query_analytics
Runs a flexible query over AirOps analytics with metrics, dimensions and filters of your choosing, in the spirit of a BI tool.
list_pages
Lists your pages with their AI search, Google Search Console and GA4 metrics side by side.
get_page_details
Returns the detailed metrics of one specific page, beyond the summary the page list gives.
get_page_prompts
Shows which tracked AI prompts cite a given page of your site.
Not documented (1)
1 toolThe directory publishes this name and nothing more. No official text says what it does, and this page will not guess from a name.
list_brand_kit_competitors
The directory lists this name and nothing more. AirOps's tools reference does not describe it, and no Claude page mentions it either, so this page will not say what it returns or does.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account for you. The request shows up in the conversation, when it matters.
With AirOps, the sheet exposes eleven reading tools and one undocumented name, so no tool here is described as changing your account. On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time, and they can cap what a connector may do for the whole organization, keeping reads open and closing writes. That setting binds everyone. Claude also works with your AirOps access, nothing more: a Brand Kit you cannot open stays closed to it.
Which plans this is available on
None of the 819 sheets in the official directory shows availability per plan. Connector by connector, the answer is published nowhere: a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can sign in. AirOps's FAQ states something narrower, set against this rule in the limits section. For the current state, the AirOps sheet in the official directory is the only place that shows it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when your mention rate falls or a competitor gains citations.
Only the publisher documents this connector: no Claude help article covers it, so the details here come from AirOps's own docs. The tool list is an observed floor, not a ceiling: by default the sheet exposes only reading, and an administrator can open actions that appear on no public sheet. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee their behavior. For another marketing-side connector, see the Claude activecampaign connector.
Which Claude plans can use the AirOps connector?
- Claude Help Center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner must enable each one first.
- AirOps documentation FAQ ↗undatedThe publisher lists Pro, Team or Enterprise and states that the free plan does not support connectors.
What this page followsThe two do not say the same thing: Anthropic's rule covers every connector, while AirOps names plans and rules one out, on an undated page. It is the publisher speaking, not Anthropic, so neither settles it for your account: check the AirOps sheet in the directory from your own account.
Need help connecting AirOps to Claude?
A person reads every message.
