AirOps

Read AI-search visibility analytics and manage Brand Kits, Grids and Knowledge Bases.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the AirOps connector does

The AirOps MCP server connects an AirOps workspace — AI-search visibility analytics, Brand Kits, Grids and Knowledge Bases — to Claude, ChatGPT and any MCP-compatible agent. AirOps documents 78 tools that read those analytics, edit brand configuration, ingest documents and trigger workflow runs. Sign-in is OAuth under a single undifferentiated scope.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

AirOps tools (78)

  • list_workspaces
  • list_brand_kits
  • get_brand_kit
  • list_brand_kit_competitors
  • list_personas
  • list_topics
  • list_aeo_prompts
  • get_prompt_answers
  • query_analytics
  • list_pages
  • get_page_details
  • get_page_prompts

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Anthropic's listing understates the surface by 66 tools. The directory's 12 names are all reads. AirOps documents 43 writes and 4 deletes that the listing omits entirely, so a reader judging risk from the directory alone would conclude this connector cannot change anything. It can.
  • One OAuth scope covers everything. The RFC 9728 resource descriptor declares scopes_supported as api and nothing else. No boundary falls between reading a mention rate and deleting a Knowledge Base — granting one grants both.
  • run_grid_rows has no enumerable blast radius. It executes customer-authored workflows whose step types include arbitrary JavaScript and Python, outbound API calls and SQL queries. No tool listing can describe what your workspace's workflows do; audit the Grid before approving the tool.
  • Nothing can read a balance. Calls spend tasks or Answer Credits and no tool among the 78 observes usage, quota or billing. Set a hard task limit in AirOps before granting broad approval.
  • create_aeo_prompt commits recurring cost, not a one-off. Each tracked prompt bills platforms × regions × (1 + named personas) × 30 Answers monthly until it is untracked, with Claude answers debiting four units each.
  • AirOps' own two tool lists disagree. Its FAQ names create_report and get_legacy_brand_kit, neither of which appears on its tools reference. We could not determine which page is current.
  • The documentation URL in Anthropic's directory is dead. The directory nominates https://docs.airops.com/mcp, which returned 404 on 2026-08-23. The working page is https://docs.airops.com/developers/mcp-server, which the server's own RFC 9728 descriptor names as its resource_documentation — the descriptor is correct where the directory is not.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or server-declared hint is published here.
  • Interactive Apps do not work in Claude Code. analytics_chart and suggest_brand_kit_edits need Claude web or desktop. The second matters for safety: its accept-or-reject review UI is the reason it is a suggestion tool rather than a write tool.
  • AirOps' provider list omits Claude where its billing table includes it. The tools reference lists five filterable providers, none of them Claude, while the billing page documents Claude answers at a 4× multiplier. We could not resolve whether Claude is filterable via these tools.
  • Idempotency is undocumented. AirOps publishes no idempotency key for run_grid_rows, create_aeo_prompt or write_grid. A timed-out call that is retried may duplicate work that bills, so treat a timeout as unresolved rather than retrying blind.

Frequently asked questions

How many tools does the AirOps MCP server actually have?

Seventy-eight by AirOps' own tools reference, not the 12 Anthropic's directory lists. The directory's 12 are all reads. AirOps documents 66 more, including every write tool, all four deletes and the workflow trigger. A third list in the AirOps FAQ names two further tools, so even 78 is a floor.

Can the AirOps connector delete anything?

Yes, four tools delete, and none of them appears in Anthropic's listing. AirOps documents knowledge_base_delete, which it says removes a Knowledge Base, all its documents and the underlying vectors; knowledge_base_delete_document; delete_topic; and delete_aeo_tag. AirOps marks the two Knowledge Base deletions as actions that cannot be undone.

What does run_grid_rows actually do?

It executes your own AirOps Workflows, so its reach is whatever your team built. AirOps documents that the tool runs all workflow columns for each row you name, up to 50 rows per call. Workflow step types include Run Code for JavaScript and Python, Call API for outbound POST requests, and Run SQL Query.

Does using the AirOps connector cost money?

Yes, and no tool can check the balance first. AirOps meters Workflows and Insights Answers against a monthly task or Answer Credit balance. Creating one tracked prompt bills platforms times regions times personas times 30 days every month. No tool among the 78 reads a balance, quota or usage figure.

What OAuth permissions does the AirOps MCP server request?

One scope named api, which separates nothing. The server's RFC 9728 descriptor declared scopes_supported as api alone on 2026-08-23, and its authorization server advertises openid, email and that same api. So consent cannot grant reading visibility analytics without also granting deleting a Knowledge Base or publishing a Brand Kit.

Can an AI agent approve its own changes in AirOps?

No, and that is a real boundary. AirOps Workflows include a Human Review step that pauses for a person to validate output, and no tool among the 78 approves one. The nearest tool, suggest_brand_kit_edits, deliberately withholds changes for a person to accept or reject in an interactive review UI.

What do I need before connecting AirOps to Claude?

An AirOps plan with AEO enabled and at least one Brand Kit configured, plus a paid Claude plan. AirOps documents that Claude Pro, Team or Enterprise is required and that the free plan does not support connectors. Interactive charts work only on Claude web and desktop, not Claude Code.

Why do AirOps tools not show up after connecting?

Usually a stale connection rather than a failed one. AirOps advises restarting Claude, confirming Settings then Connectors shows AirOps as Connected, and disconnecting then reconnecting to clear cached authentication. AirOps also notes that corporate networks and VPNs can block MCP connections or OAuth redirects entirely.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put AirOps to work.

Connect AirOps once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.