Connectors / Travel
Travel MCP connectors for Claude, ChatGPT and Cursor
5+ Travel connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.
https://api.elaichi.ai/mcp
The same for every user.
-
Their own access. An agent never gets more than the person it acts for.
-
One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.
The connectors
Travel connectors in the catalog
Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.
8 connectors
-
Cloudbeds Bring your own OAuth app 555 tools
-
Egencia App credentials 44 tools
-
GuestPoint API key 9 tools
-
Navan App credentials 1 tool
-
Navan SCIM API key 2 tools
-
Otto Hosted sign-in
-
Travefy API key 88 tools
-
Tripadvisor API key 18 tools
No Travel connector by that name
It may sit under another category, or not be in the catalog yet — any documented API can become a connector.
In practice
What teams do with Travel connectors
Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.
Finance
-
Reverse a batch of adjustments posted in error
Remove a set of mistaken adjustments in one pass instead of opening each folio, with a record of who did it and when.
-
Pull the receipt for an expense query
Look up an Egencia booking by its reference and fetch the receipt, so a disputed hotel or airfare line can be matched without logging into the portal.
-
Convert a quote for an overseas guest
Look up the currencies GuestPoint supports and the current exchange rates to show an international guest what a stay costs in their own currency.
Operations
-
See every booking departing this month
Ask for the Travefy bookings leaving in the next thirty days and get a plain list you can work through, then update any booking whose dates or details have shifted.
-
Verify a leaver has been removed
Look up a departed employee in Navan by ID and confirm their status has changed, closing the offboarding checklist with evidence.
-
Find the right traveler quickly
Ask which Navan users belong to a given office or department when planning a team offsite, and get the names back in plain language.
Front desk
-
Post a folio adjustment during checkout
Apply a credit for a maintenance issue or a correction for a misposted charge in Cloudbeds while the guest is still at the desk.
-
Change a booking while the guest waits
Extend a stay, move the dates or correct guest details on an existing GuestPoint reservation while the guest is still at the counter.
-
Add breakfast, parking or a late checkout
Attach an extra to a property in GuestPoint when a guest asks for it, so it appears on their stay and their bill.
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.
-
Turn a confirmed proposal into a booking
When a client says yes, ask the agent to create the Travefy booking with the traveler, dates, and details already in the contact record, instead of retyping them.
-
Price a group across properties
Check availability and rates at several properties at once to put together a quote for a tour operator or corporate account.
Once it is connected
Things to ask
Each of these is answered against the access the person asking already has, in the Travel account you connected.
-
Which allotment blocks still have unsold rooms this weekend?
-
Which Egencia bookings are waiting on approval today?
-
Show reservations arriving at the harbour property this week.
-
List everyone with an active Navan account.
-
List all Navan SCIM users added this month.
-
Find a flight to Chicago next Tuesday morning, back Thursday evening
-
Which Travefy bookings depart in the next two weeks?
-
Show recent reviews for our three highest rated locations.
The tools
What an agent can call in Travel
- Connectors
- 5+
- Tools
- 717
- Hosted sign-in
- 1
in the Travel catalog
callable the moment you connect
connect with nothing to register
Of those 717 tools, 8% delete something. Restricting an agent to reads is not a promise here, it is 323 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.
- Read 45%
- 323 tools · list, get, search
- Write 32%
- 228 tools · create, update, send
- Delete 8%
- 54 tools · delete, remove, archive
- Other 16%
- 112 tools · vendor-specific verbs
One endpoint
https://api.elaichi.ai/mcp
Every connector above answers here.
Every Travel connector, by depth
Tool counts are what the connector exposes today; the split is what those tools do.
Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect. API key and App credentials mean an admin pastes them once, with nothing to register.
| Connector | Tools | Read · write · delete | Sign-in |
|---|---|---|---|
| Cloudbeds | 555 | Your own app | |
| Travefy | 88 | API key | |
| Egencia | 44 | App credentials | |
| Tripadvisor | 18 | API key | |
| GuestPoint | 9 | API key | |
| Navan SCIM | 2 | API key | |
| Navan | 1 | App credentials | |
| Otto | Hosted |
FAQ
Frequently asked questions
How many Travel connectors does Elaichi have?
5+ Travel connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.
Can Claude, ChatGPT and Cursor all use Travel connectors?
Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor or any MCP client connects to that same address with OAuth, while the Elaichi Agent reaches the same tools inside the app. Connecting a Travel account once makes it reachable from every one of them.
Do Travel connectors work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Travel connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.
Do Travel connectors need me to bring my own OAuth app?
Most do not. 1 of the Travel connectors uses Elaichi's hosted sign-in, with nothing to register. 6 connect with an API key or app credentials that an admin pastes once, with no app to register. 1 asks you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.
Can I stop an agent from writing to Travel tools?
Yes. Tool restrictions apply at role and individual level, and a restricted tool is left out of the model's tool list and cannot be called. Read-only access to a Travel connector is a matter of allowing the reads and leaving the writes out.
Nearby
Teams that connect Travel usually connect these too
Put Travel connectors in front of your team
14 days on Gold, no credit card. Connect one 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.