Otto MCP connector
Connecting Otto to Elaichi lets Claude, ChatGPT, Cursor and the Elaichi Agent search and book real flights and hotels and plan trips in Otto, with each person acting as themselves and every booking recorded.
-
How it connects. Connects over OAuth. 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 Otto to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Otto once
-
Open Connections, choose Add connection, and pick Otto.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Otto. Otto's own window opens. Whoever approves it decides what this connection can reach.
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.
Otto MCP connector for 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.
Otto MCP connector for 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.
Otto MCP connector for 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 Otto 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 Otto through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Sales
Book the trip while the deal is warm
Ask for flights and a hotel near the prospect's office for next Tuesday, and Otto returns real options you can book without leaving the conversation.
-
Executive assistants
Plan a multi-city week in one ask
Describe the week, the cities and the meetings, and the assistant builds the itinerary in Otto, then books each leg as the executive confirms it.
-
Operations
Get the whole crew on site together
Search flights and rooms for six people heading to the same plant on the same day, then book from a shortlist the AI puts in front of you.
-
Events
Line up speaker and staff travel
Hand over the speaker list and the venue, and the assistant searches and books arrivals in Otto so everyone lands before the doors open.
-
People
Bring a new hire in for onboarding week
Ask for a flight and a hotel near the office for a new starter's first week, and it is booked in Otto before their laptop ships.
-
Customer success
Show up in person for the renewal
Plan the visit around the customer's calendar, compare flight times, and book the trip in Otto from the same chat where you prepped the agenda.
Try asking
- “Find a flight to Chicago next Tuesday morning, back Thursday evening”
- “Book a hotel near the Austin office for the sales offsite”
- “Plan a three-city trip for the London customer visits in May”
Compare
Elaichi vs Zapier MCP vs Composio for Otto
All three can connect Otto to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Otto tools | Allow or restrict single Otto 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 Otto 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.
See it in Elaichi
What connecting Otto gets you
5 screens from the product, each doing one job for your Otto account.
The agent
Ask about your trips in plain language.
Flights, hotels and bookings in Otto, answered from live records as you type.
- trips
- flights
- hotels
- bookings
Ask Elaichi to work across your apps.
Find a flight to Chicago next Tuesday morning, back Thursday evening
Book a hotel near the Austin office for the sales offsite
Plan a three-city trip for the London customer visits in May
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint brings Otto to every client.
Claude, ChatGPT and Cursor reach Otto through one governed address, no SDK and no shared key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Toolboxes
Each team gets its own Otto toolbox.
Sales books client visits, People handles onboarding trips, and each team sees only its own.
- Sales
- Executive assistants
- Operations
- People
ElaichiToolboxesShared connections
Share one Otto connection without sharing passwords.
Teammates book travel through a shared Otto account and never see the credential behind it.
- Sales EMEA
- Executive office
- Field operations
- People team
ElaichiConnectionsAudit log
Every Otto booking has a name on it.
When, who, what happened and which trip, recorded in a log nobody can edit.
- 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
Monday's travel digest writes itself, then waits.
Upcoming Otto bookings are fetched, grouped by trip, drafted, approved by a person, then posted back.
Otto digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch trips
Otto
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
Otto
Queued
Collections and dashboards
Otto travel numbers, refreshed without a prompt.
Bookings over 14 days, split by team, computed on a schedule with no model in the math.
Otto health
Refreshed 4 minutes ago · every 15 minutes · from the trips collection
Trips
1,284 ↓ 12%
Flights
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Trips created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Executive office 27%
Field operations 21%
People team 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Otto to Claude?
Connect Otto in Elaichi first: pick Otto from the catalog, and Otto asks you to sign in with your usual Otto account and approve access. There is no client ID or secret to generate and no OAuth application to register. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you into Elaichi and Otto appears.
Does Otto work with ChatGPT and Cursor as well as Claude?
Yes. Once Otto 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 Otto once and every client you use picks it up.
What can an AI agent actually do with my Otto data?
With Otto connected, an assistant can search real flights and hotels, compare options, build a trip around your meetings and book it, all from a chat. Exactly what is available depends on what your Otto account has set up. Short, concrete asks such as a flight to Denver on Thursday morning get better results than long paragraphs.
Does connecting Otto give the AI everything in my travel account?
No. Every request to Otto runs as the person who signed in, so the AI can only see and book what that person can see and book in Otto themselves. Elaichi can narrow that further with restrictions, and it never widens it.
Can I stop an agent from booking or changing things in Otto?
Yes. Restrictions in Elaichi work per action, so you can allow searching flights and hotels in Otto while blocking booking, cancellation or changes. A restricted action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to an Otto connection when someone leaves?
Offboarding a person in Elaichi ends their access to Otto immediately, across every client they used. A shared Otto connection keeps working for everyone else on the team. Disconnecting Otto once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Otto MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Otto 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 Otto?
Yes. Both let Claude, ChatGPT or Cursor use Otto. 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 Otto call.
How is Elaichi different from Composio for Otto?
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 Otto: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Otto in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
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.