Connect Tineo to Claude Code for travel planning
Connect your Tineo trips to Claude Code with a short setup, then start with an itinerary summary and a clearly scoped travel request.
On this page
You can connect Tineo’s travel service to Claude Code so that a conversation can work with the trips in your Tineo account. The useful starting point is modest: find a trip, summarize its plans, and ask a focused question before requesting changes.
This guide is for people who already use Claude Code. If you prefer Claude in a browser, start with the Claude tab on Tineo’s Claude & ChatGPT setup page. That is a different setup from the Claude Code instructions below. You can also use Tineo Assistant directly without connecting an external app.
Tineo publishes this guide. Setup information was checked September 14, 2026 against Tineo’s current connector screen and Claude Code’s connection documentation. The command combines the documented Claude Code setup with Tineo’s published endpoint; this article does not claim a completed sign-in test on your account.
What you need
Have Claude Code installed and working, a Tineo account you can sign into, and a trip you recognize. An existing reservation makes the first check much easier: you can compare the response with something you know is correct.
If your organization manages Claude Code, its permissions may affect which connections you can add. Follow those controls rather than placing a personal travel connection into a shared configuration.
Connect your account
Tineo’s setup page shows the connection address: https://api.tineo.ai/mcp. You do not need to build anything to use that remote connection.
In your terminal, run:
claude mcp add --transport http --scope user tineo https://api.tineo.ai/mcp
Then open Claude Code, enter /mcp, select Tineo, and follow the sign-in prompt. Review the requested access and use the intended Tineo account. The user scope keeps this setup in your own Claude Code configuration instead of sharing it with a project. Claude Code setup and authentication.
If the connection name already exists, check it in /mcp rather than repeatedly adding it. Being listed is not the same as being signed in: finish authentication and check the connection status before starting the travel conversation.
Begin with a read-only question
Try an explicit first request:
Use Tineo to list my upcoming trips. Do not change anything.
Choose a trip from the answer, then ask for one small summary:
Summarize the first day of that trip, including the arrival and hotel details already saved in Tineo. Tell me what information is missing.
Compare the result with the itinerary in Tineo. This is a useful connection check because it tests the right account and the right trip without asking for a modification. It also makes missing information visible before you build a plan around it.
Keep suggestions separate from saved changes
Once you have the right trip, you can ask for ideas around the existing schedule. “Suggest a relaxed afternoon near my hotel” leaves room for discussion. “Add the option I chose on Friday afternoon” is a different request: it asks for a change.
Be clear about which one you want. Review permission prompts when shown, and inspect the saved itinerary after a change. A suggested hotel or saved activity is not a booking confirmation, and an itinerary edit does not cancel a reservation with its provider.
For a concrete planning pattern, use our day-planning walkthrough. You can adapt its questions to the connected conversation without learning a catalog of commands.
If your trip does not appear
Check the connection status and account first. Then open Tineo and confirm the trip is present there. If it is missing in Tineo too, resolve the import or create the trip before expecting Claude Code to find it. If access has expired, reconnect through the authentication flow.
For ongoing connection trouble, use Tineo support and include the error wording without passwords or sign-in tokens. To remove the Claude Code connection, run claude mcp remove tineo --scope user; consult Claude’s management instructions if your setup uses a different scope.