What is MCP? The Model Context Protocol explained for travel agencies

You probably already use ChatGPT or Claude at your agency. You paste a client brief, ask for an outline, then copy the answer back into your software. Every question means another export and another paste. The AI is clever, but blind: it cannot see your projects, suppliers or invoices. So what is MCP, and what does it change for a travel agency?

‍

MCP is the answer to that blind spot. This guide explains the Model Context Protocol in plain language, with a safety checklist to use before connecting any AI to your agency data.

‍

In short

• MCP (Model Context Protocol) is an open standard, introduced by Anthropic in November 2024, that lets an AI assistant connect to the software where your data lives.
• With MCP, the assistant works on your real data in its source tool, instead of what you paste into a chat.
• A good MCP connector respects each user's access rights, starts in read-only mode and asks for confirmation before any change.
• Ezus runs its own official MCP server so travel agencies can query projects, check files and automate tasks from Claude in plain language.

‍

Want to see MCP working on your own data? Book a demo or discover the Ezus connector for Claude.

‍

What is MCP (Model Context Protocol)?

MCP stands for Model Context Protocol. Anthropic, the company behind Claude, announced it in November 2024 as "an open standard for connecting AI assistants to the systems where data lives". In other words, a common language between AI assistants and business software.

‍

Before MCP, every new data source required its own custom implementation, as Anthropic put it. MCP replaces those one-off bridges with a single shared standard. A software vendor builds an MCP connector once, and compatible AI assistants can use it.

‍

The official MCP documentation uses a simple image: think of MCP like a USB-C port for AI applications. Just as USB-C plugs very different devices into the same socket, MCP gives AI assistants a standard way to plug into files, databases and business tools.

‍

"Open" matters here: MCP does not belong to a single assistant. The official documentation lists Claude and ChatGPT among the AI assistants that support it, alongside development tools such as Visual Studio Code and Cursor. The travel industry is paying attention too: Skift reports that Booking.com, Expedia, Turkish Airlines, Amadeus and Sabre are adopting MCP to power AI-driven travel search and booking.

‍

How does MCP work?

You do not need the technical details, but three words help.

‍

• The client is the AI assistant you talk to, for example Claude.
• The server is the piece run by your software vendor that exposes its data to the AI. For Ezus, it is the official server at mcp.ezus.ai.
• The tools are the specific actions the server allows: list projects, read an invoice, create a step, record a payment. The AI can only do what these tools permit.

‍

Here is what happens when you ask Claude a question through an MCP connector:

1. You ask in plain language: "Which projects leave next week?"
2. The AI picks the right tool offered by the connector.
3. The server checks your account rights and sends back only the data you may see.
4. The AI writes a clear reply. With the Ezus connector, any change is shown first and saved only after your confirmation.

‍

The key point: with a well-built connector, the AI never gets a master key. It works with your own login and rights, as if you were using the software yourself.

‍

Why MCP matters for travel agencies

Most agencies use AI as a smart notepad on the side. That works for emails or destination copy, but hits a wall as soon as money, suppliers or clients are involved. We covered this gap in our comparison of travel agency software vs ChatGPT: a chatbot does not know your rates, your margins or your files.

‍

MCP flips the setup: instead of copying data into the AI, you bring the AI to the data, in the tool where it already lives. No export, no outdated spreadsheet.

‍

For an agency, that means concrete uses:

• Asking business questions in plain language, such as "Which invoices are overdue?" or "What is my net margin on invoices issued in September, by sales manager?"
• Checking a file before sending it to a client: nights without accommodation, travelers missing an email or phone number, margin line by line.
• Turning an itinerary from a Word file, PDF or supplier email into a structured project with steps, services and prices.
• Importing a supplier rate sheet into your supplier catalog, with duplicates and price differences flagged first.

‍

For the bigger picture, read our article on what AI changes in the travel agent's job.

‍

Is it safe? A checklist before connecting an AI to your agency data

Before you switch on any MCP connector, run through this checklist. Here is how the Ezus connector for Claude answers each point.

‍

• Official connector from your software vendor. Ezus runs its own MCP server, built on the Ezus public API.
• Per-user access rights. Each person connects with their own account and the AI only sees what that user's Ezus rights allow.
• Read-only by default. The Ezus connector starts in read-only mode. Write access is enabled for an agency only on request, through Ezus.
• Confirmation before any change. With write access, Claude shows the planned changes and waits for your approval before saving anything.
• No delete. The Ezus connector has no delete tool, so the AI cannot remove your projects, clients or invoices.
• Data stays in the tool. Your data stays in Ezus, with no intermediate copy or syncing to another database.
• Time-limited, controlled access. You should stay in control of who connects and for how long. With Ezus, the Claude session lasts 90 days before it must be renewed, and only admins can create the API key.
• Client data and GDPR. Client information is personal data. Check your obligations and your AI provider's terms before connecting, with whoever handles data protection at your agency.

‍

What MCP looks like in practice: the Ezus connector for Claude

Ezus offers an official MCP connector, currently in beta, that links your Ezus account to Claude. You can query your data, check files and automate certain operational tasks in plain language, without changing how you work. A good first test is to ask "Who am I in Ezus?" or "List my last ten projects."

‍

Setup takes a few clicks. You need the Ezus Premium plan, which includes the public API, and a Claude account. The steps are detailed in the Help Center guide on how to connect Ezus to Claude, and our Ezus connector for Claude article walks through the launch.

‍

To see what agencies do with it, from importing a rate sheet to recording a client deposit, read our guide to Claude use cases for travel agencies. The complete overview lives on the Ezus for Claude page.

‍

Put your AI to work on your real agency data

MCP is not a gadget for developers. It lets your AI assistant stop guessing and work on your actual projects, suppliers and invoices, under your rules. Before connecting, ask three questions: is the connector official, does it respect user rights, and does it ask before changing anything?

‍

Ezus already helps more than 600 travel agencies, DMCs and tour operators in over 70 countries centralize their itinerary builder, budgets, supplier catalog, documents and financial management in one place. The Claude connector adds a plain-language layer on top of that structured data.

‍

Book a demo with Ezus and discover how MCP and Claude can work on your agency data, safely and without changing your habits.

‍

Frequently asked questions

‍

What does MCP stand for?

MCP stands for Model Context Protocol. It is an open standard introduced by Anthropic in November 2024 that defines how AI assistants connect to external software and data.

‍

Is MCP only for Claude?

No. MCP is an open protocol, and the official documentation lists Claude and ChatGPT among the AI assistants that support it, along with tools like Visual Studio Code and Cursor. The Ezus connector is currently documented for Claude.

‍

Do I need technical skills to use an MCP connector?

Not with the Ezus connector. An admin generates an API key in Ezus Settings, the connector is added in Claude in a few clicks, and each user signs in with their own Ezus account.

‍

Which Ezus plan includes the Claude connector?

The connector requires the Ezus Premium plan, which includes the public API. On the Claude side, a Pro, Max, Team or Enterprise plan is recommended; the free plan works but allows only one custom connector. See Ezus pricing for plan details.

‍

Can an AI delete my data through MCP?

It depends on the tools the connector exposes. The Ezus connector has no delete tool, starts in read-only mode, and asks for confirmation before any change when write access is enabled.

‍

Is MCP better than pasting my data into ChatGPT?

For agency data, usually yes. With MCP, the AI reads up-to-date data in your software, within your rights, instead of copies pasted into a chat. With Ezus, your data stays in Ezus and no intermediate copy is made.