Skip to content

Artificial Intelligence

AirOps MCP connector

The AirOps connector lets Claude, ChatGPT, Cursor and other MCP clients run your AirOps workflows, grids, agents and brand kits through one governed endpoint, with each person signed in as themselves and every run logged.

Connect on Elaichi How to connect

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect AirOps to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect AirOps once

  1. Open Connections, choose Add connection, and pick AirOps.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste an AirOps API key. One person generates a token in AirOps and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

airops
AirOps
Algolia
Botpress
Braintrust
Chatbase
Chatvolt
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

AirOps MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

AirOps MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

AirOps MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect AirOps to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect AirOps on Elaichi See pricing

Use cases

What teams do with AirOps through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Content

    Run a content workflow from a chat

    Ask for a draft, a rewrite or a brief and have the right AirOps app run with your inputs. Check the result, rate it, and rerun it if the first pass missed the mark.

  • SEO

    Generate a grid of pages and pull the CSV

    Kick off a grid run for a batch of keywords or product pages, then download the latest CSV straight into the conversation to review before anything ships.

  • Marketing

    Keep the brand kit in front of every draft

    Look up a brand kit, its prompts and its analytics before a campaign, so copy produced elsewhere still matches the voice AirOps already knows.

  • Operations

    Watch, retry and cancel long runs

    See which executions are still running, retry the ones that failed overnight, and cancel a job that was started with the wrong inputs.

  • Growth

    Talk to an AirOps agent with live context

    Chat with an agent app you have already built in AirOps, passing along the customer or campaign details from the rest of your conversation.

  • Content

    Feed research into a memory store

    Upload a file or add a document to a memory store so the next workflow run has the latest product sheet, interview notes or style guide to work from.

Try asking

  • “Which AirOps apps ran the most executions last week?”
  • “Summarize yesterday's failed executions and what each app was doing.”
  • “Run our blog brief app on these three uploaded files.”

See all 43 AirOps tools below

Compare

Elaichi vs Zapier MCP vs Composio for AirOps

All three can connect AirOps to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for AirOps, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over AirOps tools Allow or restrict single AirOps tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per AirOps call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

AirOps tools for your AI agents

43 tools are ready to call through Elaichi's MCP endpoint the moment you connect AirOps, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting AirOps gets you

6 screens from the product, each doing one job for your AirOps account.

The agent

Ask AirOps questions, get answers from live executions.

Type a question in plain language and read answers from apps and executions.

  • apps
  • executions
  • agent chats
  • files

Ask Elaichi to work across your apps.

Which AirOps apps ran the most executions last week?

Summarize yesterday's failed executions and what each app was doing.

Run our blog brief app on these three uploaded files.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One AirOps endpoint for Claude, ChatGPT and Cursor.

Connect any MCP client over OAuth, with no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

Tool catalog

43 AirOps tools cover apps, executions and files.

Run executions, hold agent chats and upload files without writing custom code.

  • List all AirOps apps
  • Get single AirOps app by ID
  • List all AirOps executions
  • AirOps executions execute
ElaichiTools
Tool Action Description
List all AirOps apps List List all apps in the airops workspace. Returns each app with id, uuid, name, description, created_at, and updated_at.
Get single AirOps app by ID Get Get a single airops app by its uuid. Returns the app object including id, name, description, created_at, and updated_at. Required: id.
List all AirOps executions List List executions for an Airops app. Returns execution records including id, status, uuid, inputs, output, runtime, credits_used, createdAt, and updatedAt. Required: airops_app_id.
AirOps executions execute Execute Execute a published Airops app synchronously and return the result. Returns the airops_app_execution object including id, status, inputs, output, and createdAt/updatedAt. Required: app_uuid, inputs. Fails if the app exceeds capacity or runs longer than 10 minutes.
AirOps executions execute async Execute Execute a published Airops app asynchronously and return the queued execution. Returns the airops_app_execution object including id, status, inputs, output, and createdAt/updatedAt. Required: app_uuid, inputs.

Toolboxes

Every team gets its own AirOps toolbox.

Curate a toolbox per team so each one reaches only the apps it needs.

  • Content
  • SEO
  • Growth Marketing
  • Data
ElaichiToolboxes
Name Source template Tools Created

Content toolbox

AirOps · blog apps and drafts

 AirOps starter 18 Mar 4, 2026

SEO toolbox

AirOps · keyword apps and briefs

 — 9 Mar 2, 2026

Growth Marketing toolbox

AirOps · campaign executions

 — 24 Feb 27, 2026

Data toolbox

AirOps · execution history and ratings

 AirOps starter 6 Feb 19, 2026

Support toolbox

AirOps · agent chats and retries

 — 31 Jan 30, 2026

Engineering toolbox

AirOps · async executions and webhooks

 — 12 Jan 22, 2026

Shared connections

Teammates run AirOps apps without seeing credentials.

The connections table shows who connected each account and how widely it is shared.

  • Content
  • SEO
  • Growth
  • Data
ElaichiConnections
Connection Scope Status Access
AI

AirOps (Content)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
AI

AirOps (SEO)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
AI

AirOps (Growth)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
AI

AirOps (Data)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
AI

AirOps (Support)

Connected by Ryan Hayes

 Personal • Active Not shared
AI

AirOps (Agency clients)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Every AirOps execution call is logged permanently.

Append-only rows record when, who, what happened, type and resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 AirOps Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 AirOps Apps Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 AirOps Apps List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A trigger drafts the digest, a person approves.

Six steps fetch AirOps executions, group them, draft a digest, then post on approval.

AirOps digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch apps

    AirOps

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. Post the digest

    AirOps

    Queued

Collections and dashboards

AirOps app health, counted and refreshed on schedule.

Four metrics, 14 days of executions created and a breakdown by team, no model.

AirOps health

Refreshed 4 minutes ago · every 15 minutes · from the apps collection

Live

Apps

1,284 ↓ 12%

Executions

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Apps created

Last 14 days

By team

Share of activity

Content 34%

SEO 27%

Growth 21%

Data 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect AirOps to Claude?

Connect AirOps in Elaichi by pasting the API key from your AirOps workspace. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks and AirOps is ready to use.

Does AirOps work with ChatGPT and Cursor as well as Claude?

Yes. Once AirOps is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect AirOps once and every client picks it up.

What can an AI agent actually do with my AirOps data?

With AirOps connected, an agent can list your apps and run one with your inputs, check on executions and retry or cancel them, chat with an agent app, generate and download grid CSVs, add documents to a memory store, upload files, and look up brand kits with their prompts and analytics. Because AirOps has many actions, short concrete asks like "run the blog brief app for this topic" work better than long instructions.

Does connecting AirOps give the AI access to my whole workspace?

No. AirOps runs through the API key of the person who connected it, so the agent sees only the apps, grids, memory stores and brand kits that key can reach. Elaichi can narrow that further with per-action restrictions, and it never widens it beyond what AirOps itself allows.

Can my team share one AirOps connection?

Yes. One person connects AirOps with their API key and shares the connection with a team in Elaichi. Nobody else on the team ever sees or handles the key, and each person still signs in to Elaichi as themselves, so the audit log names who ran which AirOps workflow.

Can I stop an agent from deleting or changing things in AirOps?

Yes. Restrictions in Elaichi apply per action, so you can allow reading brand kits and running executions while blocking deleting documents from a memory store or cancelling runs. A blocked AirOps action is never advertised to Claude, ChatGPT or Cursor, so no prompt can reach it.

What happens to an AirOps connection when someone leaves?

Offboarding a person in Elaichi ends their access to AirOps at once, in every client they used. If they shared an AirOps connection with a team, it keeps working for everyone else. Disconnecting AirOps once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

Does the AirOps MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. AirOps is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for AirOps?

Yes. Both let Claude, ChatGPT or Cursor use AirOps. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every AirOps call.

How is Elaichi different from Composio for AirOps?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to AirOps: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put AirOps in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect AirOps Talk to us
Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.