Connect an AI assistant

Let an assistant such as Claude or ChatGPT read your trips and bookings, write trip text and translations, and add draft trips and dates, within your own role.

How-to guide2 min read

An AI assistant that supports connectors (MCP), such as Claude, ChatGPT, Cursor or VS Code, can work in Travel Orbit for you. Ask it things like:

"Write a Norwegian summary for Lofoten ridge walk."
"Which departures of the Senja sea kayak week have fewer than three places left?"
"Rewrite day 2 of Lofoten ridge walk so it mentions the sunrise on Reinebringen."
"Add a departure for Lofoten ridge walk on 14 June 2027 with 10 places."
"Which booking requests are waiting for us?"

Connect one

Open AI assistants under Developers in Travel Orbit and copy the address.
In your assistant, add a connector or MCP server with that address. On the same page, Add to Cursor and Add to VS Code do this for you, and Copy Claude Code command copies the command for a terminal.
The assistant opens a page from Travel Orbit. Sign in to Orbit if you aren't, choose the organisation and select Allow.

In Claude, add a custom connector with the address under Settings, Connectors. In ChatGPT, create a connector under Settings, Apps and connectors. Custom connectors depend on your ChatGPT plan.

What it can do

It works with your role:

Everyone: find and read trips, departures, places left, destinations, bookings and requests
Editors and Admins, also: write a trip's name, summary, description, highlights, what is and isn't included and itinerary day texts, in any of your languages; translate what isn't translated yet; write destination pages; add draft trips and departure dates

A trip it adds is a draft with a price of 0, so nothing goes on sale until someone on your team sets prices and publishes it. A date it adds to a published trip starts closed for booking, unless you asked it to open the date.

What it never does

Change prices, payment plans, discount codes or cancellation terms
Publish trips, refund, take payments, or touch Stripe or settings
See travellers' emails, phone numbers, addresses, passports or dates of birth. Bookings show names, dates, what was booked and what is paid.

Check what it writes before you publish. Its words are its own, even when the facts come from Travel Orbit.

See what it did

Every change an assistant makes is in the audit trail, as you and the assistant together, such as "Kari via Claude".

Disconnect one

Under AI assistants, select Disconnect next to it. It stops at once. Admins see every assistant connected in the organisation and can disconnect any of them; everyone else sees their own. An assistant also stops when the person who connected it loses Travel Orbit, and after 30 days without use.

Was this page helpful?

The MCP serverConnect any MCP client to Travel Orbit with OAuth sign-in, and the tools it gets for trips, departures, destinations and bookings.AI writingDraft, improve, shorten or warm up trip, destination, guide and place texts with AI, in your brand voice, following your own templates and in every language you offer. Set it up once with your organisation's own AI key. You decide what is used.Who can do whatViewers read everything, Editors also run trips and bookings, Admins also manage Stripe, refunds, settings, keys and people, and only owners delete images for good.LanguagesOffer your trips, destinations, booking site and traveller emails in more than one language, translate them yourself, with DeepL or with your AI provider, keep names like Lofoten untranslated, and see what still needs translating.The audit trailSee who changed trips, departures, bookings, payments, codes, the library, settings, Stripe, keys and roles, and when.