What is a travel MCP server?

A travel MCP server is a program that gives an AI assistant a working travel capability it can call during a conversation — searching live flights, pricing an activity, checking a visa rule, converting a currency — instead of answering from what it read during training. MCP is the Model Context Protocol, an open standard for connecting assistants to outside tools and data. A travel MCP server is simply one whose tools serve a trip, which on MCPHub.travel means one of 8 categories: flights, stays, activities and tours, cars and ground, eSIM and data, visas and entry, delay compensation, and everything else. It searches, prices, compares and checks. Most servers do not book — they return live options and booking links, and the booking happens on the provider’s own site under their terms; a small number can complete a transaction, and the catalog says which.

What is MCP?

MCP stands for Model Context Protocol: an open standard for connecting an AI assistant to tools and data that live outside the conversation. It is a protocol, not a product, and that is the part that matters. A server built once answers to Claude, ChatGPT, Gemini, Grok or a stack you wrote yourself, because none of them is being integrated with — they all speak the same protocol.

A server publishes a tool schema: a machine-readable description of what it can do, what it needs to be told, and what it gives back. The assistant reads that schema, works out which tool answers the question in front of it, calls it, and folds the result into its reply. You see none of this. You see an answer with a real number in it.

What makes a server a travel MCP server?

Nothing in the protocol. MCP has no concept of travel — a server is a travel server because of what its tools do. On this site that means it serves one of eight parts of a trip:

Some of those are crowded. Some are empty. Delay compensation is empty everywhere — a sweep of five ecosystems found no such server in any of them, which is why we are building the first. An empty category is information, not an embarrassment to be hidden.

How is an MCP server different from an API?

Often, underneath, it is the same thing. Kiwi Flights is a travel MCP server and Kiwi.com also has an API; the flight data does not change on the way through.

What changes is who can use it. An API is a contract for a programmer: someone reads the documentation, writes the request, handles the response, ships the code. An MCP server is a contract for a model: it describes itself well enough that the assistant can decide, in the middle of your sentence, that this is the moment to check a fare — and it does that without anyone writing anything.

That is why “wrapping an API in an MCP server” is real work rather than a formality. The schema has to be legible to a model that has never seen the service before, and a badly described tool is one the assistant will call at the wrong moment or not at all.

What can an assistant actually do with one?

It can search (live flights, activities, rental cars), price (what an experience costs today, what €340 is in another currency), check (visa requirements, transport departures, a flight’s emissions) and compare across several sources at once — which is the part a person rarely bothers to do by hand.

Two of those sources searching the same route will disagree, because they see different inventory. An assistant that can call both and put the answers side by side is doing something you could not have got from either.

What can it not do?

Most of them do not book. Nearly every server here returns live options and booking links; the booking happens on the provider’s own site, under their terms, with your own details. MCPHub.travel is the connection, not the merchant of record, and there is no payment step on this site at all — that stays true even for the three servers that can transact. Gondola books hotels and vehicles, HemmaBo creates and checks out a stay with the host, and Pifini generates a Stripe-hosted ticket link. Each of those runs under the vendor’s own terms, and each server’s page says so plainly.

It also does not guarantee that a listed server is reachable. Of the 192 travel services we found with an MCP server behind them, 166 sit behind a login and 3 behind a commercial contract — 23 answer an anonymous call. That is the difference between a catalog that counts listings and one that calls endpoints, and it is why ours sorts on access model first.

How do you use one?

Connect your assistant to MCPHub.travel once and ask in plain language — there is a walk-through for Claude and one for ChatGPT. The current list, with live status, is on best travel MCP servers; the rest of the common questions are in the FAQ.

If you have built a travel MCP server, the listing rules say what we check before listing it, and submitting is free.

By what a trip is made of

100+ travel MCP servers across 8 categories. One page each, including the ones with nothing in them — that is information too.

Questions people ask

What does MCP stand for?
Model Context Protocol — an open standard for connecting an AI assistant to outside tools and data. It is a protocol rather than a product, which is why the same server answers to Claude, ChatGPT, Gemini or your own stack without being rebuilt for each.
What makes a server a travel MCP server?
Nothing technical — the protocol has no idea what travel is. It is a travel server if its tools serve a trip: flights, stays, activities, cars and ground transport, eSIM and data, visas and entry, delay compensation, or a clear travel use that fits none of those.
How is an MCP server different from an API?
An API waits for a programmer to write the call. An MCP server describes its own tools in a schema the model reads, so the assistant can decide when to call one mid-sentence and nobody writes code. Underneath, many travel MCP servers are wrappers around an existing API.
Can an AI assistant book a flight through one?
No. No server on MCPHub.travel books anything. They return live options, prices and booking links; you finish on the provider’s own site under their terms. There is no payment step anywhere here and no server holding your card.
Do I need to be a developer to use one?
No. Connect MCPHub.travel to your assistant once and ask in ordinary language. There are no config files to maintain, nothing to keep running, and no keys to paste except where a server uses your own account with a provider.
If a server is listed in a directory, does it work?
Not necessarily, and this is the trap. Of 192 travel services we found with an MCP server behind them, 166 sit behind a login and 3 behind a commercial contract — only 23 answer without either. Presence in a directory is not the same as being callable.