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.
-
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.
43 tools
How to connect
How to connect AirOps to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect AirOps once
-
Open Connections, choose Add connection, and pick AirOps.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect AirOps to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect AirOps to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect AirOps to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
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.”
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.
No tools match your search.
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 clientsClaude
ChatGPT
Cursor
Copy the endpoint
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
ElaichiToolsToolboxes
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
ElaichiToolboxesShared 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
ElaichiConnectionsAudit 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 logLaunching 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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch apps
AirOps
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
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 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.
Put AirOps in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.