November 6, 2026. Travel Code has opened its Model Context Protocol (MCP) server for write access: from Claude, ChatGPT, Gemini or an IDE assistant, an employee can now search, book, change and cancel flights and hotels under their own company's rules. The same release gives Robert, Travel Code's AI travel agent, the opposite direction — it connects to the MCP servers of other systems a company already runs, such as Notion, Linear, Jira, HubSpot, an HR system or a CRM, and uses them as its own tools.
What changed on November 6
Until now the connector read data. Three things are new.
- Booking, changes and cancellation run through the assistant. The server address is
https://mcp.travel-code.com/mcp; setup for each client is on the connect page. - Confirmation happens on the server, not in the model. Four actions — create an order, modify an order, cancel an order and contact travelers — never execute on the first call.
- Robert works outward. A company admin can point Robert at any MCP server the company uses, tool by tool.
The mechanics of the protocol itself, the tool list and the client-by-client setup are covered in our standing guide to the Travel Code MCP server; this article is about what the write access does and where the limits are.
What a booking actually looks like
An employee types "find me a Warsaw–Berlin flight on Thursday morning" in their assistant. The assistant calls Travel Code's search, the person picks an option, and Travel Code returns a summary card and asks them to confirm. On confirmation the order is created on the company account.
Payment follows the company's existing payment profile rather than the chat. A flight booked this way on a balance or invoice profile is paid immediately and sent for ticketing. On a card profile the order is created and stays awaiting payment, to be paid in Travel Code. Where the fare requires a hold or an extra action, the order is held as a pre-booking. Hotels are confirmed with the supplier and stay awaiting payment through the company's usual flow. Rail, car rental and transfers are not exposed through the connector: it covers flights and hotels.
Scopes, confirmation and policy: what stops an assistant going too far
An AI assistant that can spend money needs its limits in the server, not in the prompt. Travel Code's MCP server signs the assistant in over OAuth, so it receives a temporary token and never the user's password, and access is split into named scopes — the server publishes flights:search, flights:status, flights:stats, airports:read, airlines:read, hotels:search, tourist:read, orders:read and orders:write in its OAuth metadata. Write actions then pass through a second gate. Where the client supports MCP elicitation, Travel Code raises the Confirm / Cancel prompt itself, so the model cannot answer on the traveler's behalf; where it does not, the server returns a summary plus a single-use code bound to that session and those exact parameters, valid for ten minutes. Travel policy is checked when the order is created: an option outside the company's rules is refused rather than quietly booked. And the connector carries no extra privilege — a traveler can do through it only what they can do in Travel Code, which for most employees means booking for themselves.
One limit is worth stating plainly: the connector has no submit-for-approval step. An out-of-policy option that a company would normally send to a manager is refused through MCP, and the person completes that request in Travel Code instead.
Robert working through the company's own systems
The reverse direction is the part that changes how trips get planned. In Robert automation → Connections an admin adds a connector by name and MCP server address, with an OAuth client id and secret where the server needs one, and signs in. Robert then has those tools alongside its own: it can read the launch date and city from a project in Notion, take a new hire's department and manager from an HR system, or check a client request against an agency's CRM before proposing an itinerary.
Each tool of a connected system is set to Always, Ask or Off, so an admin decides what Robert may do unattended and what needs a person to approve a card in the chat. Passport details, card numbers, dates of birth and contact details are not sent to a connected system until that category is explicitly allowed. What a connected system returns is treated as data and never as instructions, which is the standard guard against prompt injection through a third-party tool. Every call is logged; if a server changes its tool list, the connection pauses until it is approved again; a sign-in completes only for the person who started it, and stored secrets are encrypted. Employees can also sign in to company connections under their own account and add personal ones. Robert loads tools on demand — search first, then call — so a long list of connections does not degrade its behavior.
Where this sits among travel MCP connectors
Several travel platforms have shipped MCP connectors since spring 2026, and the differences are mostly about write access and direction rather than the protocol. Travel Code is not claiming to be first: Vibe announced search, booking, payment and amendments through ChatGPT, Claude and Microsoft Copilot in July 2026, and Perk added booking to its connector in August. What is unusual in this release is the pairing — a write-capable server for other assistants, plus an agent of our own that consumes other systems' MCP servers — and the fact that agencies running on Travel Code get the same connector for their own clients.
| Platform | Announced | Write access through an assistant | Agent consumes other MCP servers |
|---|---|---|---|
| Travel Code | Nov 6, 2026 | Book, change, cancel flights and hotels; server-side confirmation; policy checked at booking | Yes — Robert connects to third-party MCP servers |
| Navan | Jul 2, 2026 | Read-only at launch, write tools listed as coming; booking runs through its Ava agent in Gemini Enterprise over A2A | Not announced |
| Perk | Jul 13, 2026; booking added Aug 19, 2026 | Booking and expense submission per its own release | Not announced |
| Vibe | Jul 20, 2026 | Search, book, pay and amend per its own release, for TMCs | Not announced |
| Amex GBT (Egencia) | Jul 27, 2026 | Booking in Claude announced, availability stated for Q3 | Not announced |
| BCD (TripSource) | May 28, 2026 | MCP framework for shopping and booking; no assistant named in the release | Not announced |
Claims in the right-hand columns are each company's own, taken from the releases linked at the end of this article.
"Companies already work across several AI assistants, and business travel has to be there too — and not in read-only mode. We've opened Travel Code in both directions: Claude or ChatGPT books and changes trips under the company's rules, and Robert sees the projects, people and clients in the company's own systems and suggests who needs to travel where," said Egor Karpovich, CEO and founder of Travel Code.
What it means for TMCs
For agencies the connector is a channel, not a bypass. A TMC running on Travel Code can let its clients book from the assistant they already use while the booking stays inside the agency's setup: its content, the client's travel policy, the client's payment rules and the agency's reporting. Staff with the right role can act on behalf of a traveler. Agencies connect their own software to Robert the same way — CRM, mid-office, internal reference data — which is the same overlay logic Travel Code applies everywhere else: it runs alongside what a company already books with instead of replacing it.
The MCP server is open source at Travel-Code-Inc/mcp-travelcode, so partners can read exactly which tools exist and how confirmation is enforced before building on it.
How to connect
- Travel Code in your assistant: setup for Claude (web, desktop, Claude Code), ChatGPT, Gemini, Codex CLI, Cursor and VS Code with Copilot is on the connect page. The server address is
https://mcp.travel-code.com/mcp, and the first request opens a Travel Code sign-in window. The repository lists Claude Desktop and Claude Code as tested and other MCP clients as compatible. - Your systems in Robert: Robert automation → Connections → "Add custom connector". Robert's wider automation capabilities are described on the AI agents page and in the release covering Robert running a TMC end to end.
Frequently Asked Questions
Which AI assistants can book through Travel Code?
Any client that speaks MCP. Setup instructions are published for Claude on web, desktop and Claude Code, ChatGPT, Gemini, OpenAI Codex CLI, Cursor and VS Code with GitHub Copilot. Claude Desktop and Claude Code are the clients listed as tested in the repository; others are listed as compatible.
Can an assistant book a trip without my confirmation?
No. Creating, changing and cancelling an order, and messaging travelers, all require an explicit human confirmation that the Travel Code server itself demands — either as an in-client Confirm / Cancel prompt or as a single-use code tied to that session and those exact parameters for ten minutes.
What can be booked and changed through the connector?
Flights and hotels. Changes cover dates, baggage, passport details and contacts, and the connector checks which changes the fare or rate actually allows before offering them. A cancellation shows the penalty and the refund before it is executed. Rail, car rental and transfers are not exposed through MCP.
Is the company travel policy still enforced?
Yes. Policy is checked when the order is created, and an out-of-policy option is refused rather than booked. Because the connector has no submit-for-approval step, a trip that needs a manager's exception is completed in Travel Code rather than in the chat.
Does the assistant get access to everything in our account?
No. OAuth scopes limit what the assistant may call, and the person's own permissions still apply on top: a traveler books for themselves, an admin sees admin tools. Access is a temporary token, never a password.
What does Robert send to a connected system?
Only what the admin has allowed. Passport details, card numbers, dates of birth and contact details are withheld until that data category is explicitly enabled, each tool is set to Always, Ask or Off, every call is logged, and a connection pauses for re-approval if the remote server changes its tool list.
Is Travel Code a TMC?
No. Travel Code is a corporate travel and expense platform that also powers TMCs, and it works as an overlay: companies keep booking where they book, and agencies keep their own content, policy and reporting while the platform adds automation on top.
Sources
- Travel Code MCP server, open source: github.com/Travel-Code-Inc/mcp-travelcode; live OAuth metadata at
https://mcp.travel-code.com/.well-known/oauth-protected-resource/mcp(verified November 6, 2026). - Navan, "Navan Launches Model Context Protocol (MCP) for Travel & Expense," July 2, 2026; Navan Anywhere with Ava in Gemini Enterprise, June 8, 2026.
- Perk, MCP release July 13, 2026 and booking release August 19, 2026.
- Vibe, "Vibe enables corporate travel booking through ChatGPT, Claude and Microsoft Copilot," July 20, 2026.
- Amex GBT, Egencia connector for Claude, July 27, 2026.
- BCD Travel, Model Context Protocol framework for TripSource, May 28, 2026.
