What is an MCP travel connector?
An MCP travel connector is a product’s listing of a server an assistant can call, so the reply can use a tool result instead of a guess from the chat. MCP, the Model Context Protocol, is the open protocol for that call, and the specification is at modelcontextprotocol.io. Tineo’s server is at https://api.tineo.ai/mcp. Claude lists the Tineo connector at claude.com/marketplace/connectors/tineo.
A call, then a result
Chat answers are sentences completed from your message and from the model’s training. A tool call is a different step. The assistant asks a server to run something specific, such as reading a trip the signed-in account may open, and then it talks about the result that came back.
That result can be wrong if the underlying record is wrong, and it can be stale if the record is stale. It is still a different kind of answer from a paragraph the model composed with no lookup. You can ask which trip it read. You can open that trip and compare.
A connector is the product’s name and switch for that server. You authorize it in Claude, or in another product that lists Tineo, so the assistant has a permitted path to the server. The protocol describes how the call is shaped. The connector is how that product exposes the server to you. Product screens change. Use the current screen in Claude, and use the ChatGPT post linked below for ChatGPT.
Paste-only chats hold what you typed
Paste a hotel confirmation into a thread and the model can summarize that text, pull out a date, or list questions about the paragraph in front of it. The summary still has to be checked against the paste. The thread does not gain your other trips, your companion’s trips, or any booking you forgot to include.
What to keep from a booking confirmation lists the fields worth having in the record itself. A paste into chat is a copy of whatever you selected. If the flight number was missing from the paste, the model does not recover it from the airline by thinking harder.
Read access and a separate permission to change
With a connector authorized for read access, tools can read the trips that account is allowed to see. That is the traveler’s own trip data on Tineo, within that account’s permission: the booked and saved itinerary the account can open. It is not a feed of every airline’s inventory.
Write access is a separate grant. Tools can change those trips only if that permission was granted. Leave write off when you want answers and you want the itinerary left as it is. Turn it on only when you intend edits to the trip record.
Changing a trip record is an edit to the itinerary in the account. It does not purchase a seat, issue a boarding pass, or file a visa. Tineo does not do those jobs. A connector does not make the model an airline. Fares, seat maps, and the carrier’s schedule still live on the airline. You book there, then the confirmation can be added to the trip.
Where Tineo is listed
Tineo publishes the MCP server at https://api.tineo.ai/mcp. Claude’s marketplace lists the Tineo connector at https://claude.com/marketplace/connectors/tineo. Authorizing that connector lets Claude call the server under the permissions you accept.
ChatGPT can use Tineo too. The steps for that app are in Connect Tineo to the ChatGPT app. Follow that post for the screens. Grant write access only when you want the assistant to change trips.
This page also does not list every tool on the server. The stable description is the permission split: read the trips the account may see, and change them only with the separate grant. If a product asks for a broader grant than you need, stop and read what that grant covers before you accept it.
Entry rules stay on the government page
A connector does not know a visa rule unless a tool returns one. Tineo’s tools are about the traveler’s own trips, not government entry rules. A question such as “do I need a visa for this passport on these dates” is answered on the official page for that passport and destination, not by assuming the trip record contains the law.
What AI trip planners get wrong covers stale entry rules as a failure mode. How to use ChatGPT or Claude to plan a trip is the drafting method for a week that is not booked yet. Use the connector when the trip already exists in the account. Use the draft-and-verify method when you are still deciding what to buy.
If you ask a connected assistant about a visa and it answers with a smooth paragraph and no tool result, treat that paragraph as an ordinary chat guess. Open the government page. Write down the date you opened it. The trip record can remind you that a flight to that country exists. It does not replace the page that states whether you may board.
Two sessions, both illustrative
Session one: you paste a sentence about a hotel in Kyoto and ask what night you arrive. The city is an illustration. The model can work only from that sentence. If the sentence omitted the year, the model should say so, or it may fill a year that you never typed. You still have to look at the confirmation.
Session two: the same account has authorized the Tineo connector with read access, and the Kyoto stay is already a segment on a trip the account can open. The assistant can ask the server for that trip and answer from the segment, including the date stored there. It still cannot see a trip on another account. It cannot edit the date unless write permission was granted. It cannot tell you the current entry rule for your passport, because that rule is not one of Tineo’s trip tools.
Put the two sessions side by side before you trust a reply. Ask whether the answer came from a tool result on your trip or from the model’s completion of the prompt. The tool result is the trip record. The completion is a guess.
How a booked segment gets there for the connector to read
A connector answers from trips the account already holds. Forward the confirmation to [email protected], or paste it, and Tineo turns the booking into segments a later question can use. Connecting Gmail is optional. Filling the itinerary from a confirmation is a different job from asking a model to invent the plan.
Frequently asked questions
What is MCP?
MCP, the Model Context Protocol, is an open protocol for connecting an assistant to tools. The specification home is modelcontextprotocol.io. In practice, the assistant calls a tool on a server and uses the result, instead of composing an answer only from the text in the chat.
What can a Tineo connector see?
With read access, authorized tools can read the trips that account is allowed to see. A separate permission is required before those tools can change trips. The connector reaches Tineo's MCP server at api.tineo.ai/mcp.
Does a travel connector know visa rules?
A connector knows a visa or entry rule only when a tool returns one. Tineo's tools are about the traveler's own trips, so an admission rule still has to come from the official page for your passport and destination. Check that page before you rely on it.
Can ChatGPT use Tineo?
ChatGPT can use Tineo. The current connection steps are in Tineo's post at tineo.ai/blog/connect-tineo-chatgpt-app/, and that post is the place to follow the screens. Authorizing a product still limits the assistant to the trips and permissions on that account.
Related guides
- How should you use ChatGPT or Claude to plan a trip?
Ask ChatGPT or Claude for a draft week and the questions you forgot, then confirm every fare, hour, and entry rule on the source page before you pay.
- What do AI trip planners get wrong?
AI trip planners finish a plausible sentence, so confirm every flight, hour, route, and entry rule on the page that owns that fact before you pay.
- What should you keep from a booking confirmation?
Keep the traveler names, the locator, times with a zone, the address, the cancellation deadline, the amount paid, and a phone number. Skip the marketing.
Sources
- Model Context Protocol, specification home (accessed 2026-11-20)
- Claude, Tineo connector (accessed 2026-11-20)
- Tineo MCP server (accessed 2026-11-20)
- Tineo, Connect Tineo to the ChatGPT app (accessed 2026-11-20)