# 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.

Source: https://elaichi.ai/connectors/otto/

## Facts

| | |
| --- | --- |
| Application | Otto |
| Category | Travel |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Otto builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | support@ottotheagent.com |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Otto is connected

- 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

## Connect Otto in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Otto.
2. Optionally set Share with, then press Connect.
3. Approve it in Otto. Otto's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Otto tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Otto MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Connect Otto to any MCP client

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Otto tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Otto through Elaichi

### Book the trip while the deal is warm

Sales. 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.

### Plan a multi-city week in one ask

Executive assistants. 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.

### Get the whole crew on site together

Operations. 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.

### Line up speaker and staff travel

Events. Hand over the speaker list and the venue, and the assistant searches and books arrivals in Otto so everyone lands before the doors open.

### Bring a new hire in for onboarding week

People. 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.

### Show up in person for the renewal

Customer success. 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.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## 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 my team share one Otto connection?

Yes. One person connects Otto in Elaichi and shares the connection with a team, and nobody else ever handles an Otto credential. Each teammate still signs into Elaichi as themselves, so the audit log shows who searched for which trip and who booked 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.