Perk MCP is Perk’s Model Context Protocol server. It connects AI assistants such as Claude and ChatGPT to a company’s Perk travel, spend, invoice, and event data so users can ask questions and take actions—like searching trips or submitting expenses—inside the assistant.

Can Perk MCP complete a booking inside the chat?

Per Perk’s help center, the assistant can search and book flights, hotels, trains, and cars, then hands off a checkout link so the traveller completes payment in the Perk web app. It does not charge the card inside Claude or ChatGPT on its own.

How does that compare to Ramp’s travel MCP?

Ramp’s documented travel flow for Ramp Plus customers searches policy-aware flights and hotels and books in the chat only after a fresh preview and an explicit confirmation, on company funds and approvals. Perk’s documented flow builds the itinerary in the assistant and finishes payment in Perk.

Does Perk MCP cover insurance, eSIM, or lounges?

Public Perk MCP docs emphasise flights, hotels, trains, cars, expenses, invoices, policy, and events. Perk also says the assistant can answer visa and entry-requirement questions. They do not describe travel insurance, eSIM, lounge day passes, or security fast track as bookable tools.

Is MCP here the same as Mobile Passport Control?

No. MCP means Model Context Protocol, the open standard for connecting AI assistants to external tools and data.

News

Perk MCP puts corporate travel in Claude and ChatGPT: what builders should take from it

By Loris Mazloum Published 12 October 2026

Corporate travel platforms are wiring the same protocol OTAs and airlines already use. Perk now documents a Model Context Protocol (MCP) server that connects Claude, ChatGPT, and other MCP clients to company travel and spend—so a traveller or travel manager can search, approve, and file expenses without opening the Perk app first.

What Perk documents

According to Perk’s developer docs, product page, and help center:

Connectors: listed as an official connector in Anthropic’s Claude directory and as an official plugin in ChatGPT’s marketplace; also works with Gemini CLI, Cursor, and VS Code.
Travel actions: search and book flights, hotels, trains, and cars. The assistant builds the itinerary and hands off a checkout link; the traveller completes Checkout & pay in the Perk web app.
Ops beside the trip: look up trips, approve or send back pending trips, download PDF confirmations, create and approve expenses, query invoices, check policy, and set up Perk Events.
Entry info: ask about visa and entry requirements for a destination (information only).
Access: every Perk customer; the assistant only sees what the signed-in user’s Perk role already allows.

That is a different shape from consumer plugins that only search. Perk keeps payment, company policy, and expense ledger on the corporate platform, and uses the assistant as the front door.

Where Ramp draws a sharper line

Ramp’s travel agent docs (Ramp Plus) describe in-chat booking for one-way and round-trip flights and single-hotel stays: search with policy status, traveller picks the option, a fresh preview shows total, policy result, funding, and approvals, then the agent books only after a new explicit confirmation. Changes and multi-city trips still go to the Ramp web app.

Together, Perk and Ramp show the corporate pattern builders should expect: policy and money stay with the company account, and the assistant is either a full book-in-chat surface (Ramp) or a search-and-handoff surface (Perk). Both still need a clear confirm step before anything costly happens.

Why it matters for AI travel agent builders

Corporate MCP is no longer just a TMC press slide. Perk and Ramp publish tool-level behaviour: scopes, RBAC, preview-then-confirm, and what stays out of chat. If you sell to OTAs or agent platforms that also serve business travellers, design for those constraints early.

Handoff vs in-chat pay is a product choice, not a bug. Search-then-checkout (Perk, easyJet, Southwest) and book-in-chat (Ramp, Mirai hotels, eDreams on Alexa+) will coexist. Your ancillary tools should work beside both: quote in the session, take an explicit yes, then issue with an idempotency key whether payment sits in your chat or on a partner site.

What is still outside the conversation

Neither Perk’s nor Ramp’s public travel MCP docs describe bookable tools for travel insurance, eSIM, lounge day access, security fast track, or airport transfers. Perk can answer visa and entry questions; that is information, not a fulfilment API.

On Ancilair those extras are tools you call beside the corporate or OTA booking layer—insurance quoted against the itinerary, eSIM for the destination, lounge search then book on a layover, plus fast track, transfers, and visa checks—over MCP, REST, or CLI, at supplier rates with 0% markup. See the travel MCP servers map and the Beside the ticket workflow.

What to watch

Whether Perk moves payment into the assistant, or keeps checkout in-app on purpose.
Whether Amex GBT (Egencia), BCD, and FCM ship the Claude or MCP connectors they have announced.
Whether corporate MCPs add a post-ticket ancillary shelf, or leave that to a second tool layer.

Sources

Not affiliated with Perk, Ramp, Anthropic, OpenAI, or Engine. Details summarised from public docs and coverage as of October 12, 2026. Not legal or immigration advice.

Questions

What is Perk MCP?: Perk MCP is Perk’s Model Context Protocol server. It connects AI assistants such as Claude and ChatGPT to a company’s Perk travel, spend, invoice, and event data so users can ask questions and take actions—like searching trips or submitting expenses—inside the assistant.
Can Perk MCP complete a booking inside the chat?: Per Perk’s help center, the assistant can search and book flights, hotels, trains, and cars, then hands off a checkout link so the traveller completes payment in the Perk web app. It does not charge the card inside Claude or ChatGPT on its own.
How does that compare to Ramp’s travel MCP?: Ramp’s documented travel flow for Ramp Plus customers searches policy-aware flights and hotels and books in the chat only after a fresh preview and an explicit confirmation, on company funds and approvals. Perk’s documented flow builds the itinerary in the assistant and finishes payment in Perk.
Does Perk MCP cover insurance, eSIM, or lounges?: Public Perk MCP docs emphasise flights, hotels, trains, cars, expenses, invoices, policy, and events. Perk also says the assistant can answer visa and entry-requirement questions. They do not describe travel insurance, eSIM, lounge day passes, or security fast track as bookable tools.
Is MCP here the same as Mobile Passport Control?: No. MCP means Model Context Protocol, the open standard for connecting AI assistants to external tools and data.