Part of AI
Your company, from the chat you already use
Many owners already keep ChatGPT or Claude open all day for emails and itineraries. TripNerve's connector lets that same chat work inside your company: ask who's on next Saturday's Everest departure, add the spring dates for Mardi Himal or draft a new trip, and the app does it in TripNerve as you. Your team sees the change at once in TripNerve and the mobile app.
- Which enquiries are waiting on a reply, and who owns them?
- Show me everyone booked on the Everest Base Camp departure on 14 November
- Add departures for the Annapurna Circuit every Saturday in March and April
- Put Pasang on the 14 November departure as lead guide
- Draft a new 12-day Gokyo Lakes trek
- Change the hero heading on our home page and show me how it looks
Connecting takes about a minute
In TripNerve, open AI apps in the sidebar and copy TripNerve's address. In ChatGPT, open Plugins, choose + and Add custom MCP server, and paste it. In Claude, open Settings, then Connectors, and choose Add custom connector; on a Claude Team or Enterprise plan an owner adds it for the organisation. In Claude Code, run the command shown on the AI apps page, then /mcp to sign in.
The app then sends you to TripNerve's sign-in page. If you work for more than one company you choose which one this connection is for, and you approve the app. Each connection is for one company, so your other companies stay out of its reach. Connected apps are listed on the same page with the company they work in.
One tool for each thing you can do
TripNerve gives the app a separate tool for each action your role allows, named after it: trips_list, departures_createMany, bookings_update, site_updateSection and so on, each with its own description and inputs. Tools are marked as reading or changing data, and those that reach outside your workspace, such as publishing the site or sending a booking email, are marked as well, so the app knows which to confirm with you.
There are also tools to see where you're connected and to take a screenshot of a page of your draft or live website, and search and fetch tools for ChatGPT's deep research. New features in TripNerve become tools as they ship, without you reconnecting. Long AI jobs such as drafting a trip or writing a blog post run in the background on TripNerve's server; the app gets a job to check on instead of waiting.
Safe to let it work
Every tool call runs as you, through the same permissions, validation and history as a click in TripNerve. A sales agent's connection can't change team roles, and nobody's connection can see more than they can in TripNerve. Changes take effect as soon as the app runs the tool, so TripNerve asks the app to confirm with you before anything you didn't clearly ask for, anything that affects travellers, such as confirming, cancelling or emailing, and anything deleted. ChatGPT and Claude also show each tool call and, depending on your settings, ask before running it.
Disconnect an app under AI apps and it stops working straight away. If someone loses their role in your company, their connection loses it too.
The connector and Ask AI, the assistant built into TripNerve, do the same jobs through the same actions. The difference is where you sit. Ask AI lives inside TripNerve and waits for your approval on every change. The connector suits owners who already plan their day in ChatGPT or Claude, want TripNerve next to their email drafts and notes, or use Claude Code for bigger jobs such as restyling the website or adding a whole season across several trips. Use whichever is open; your team sees the result the same way.
Worked example
Khumbu Path from Claude on a phone
The owner of Khumbu Path is in Namche Bazaar on Sunday 8 November with patchy signal and Claude on her phone, connected to TripNerve the week before.
| What she asked | Tool Claude used | Changed anything |
|---|---|---|
| Who's on the EBC departure on Sat 14 Nov? | bookings_list | No: 9 travellers on 4 bookings |
| Put Pasang on that date as lead guide | departureCrew_add | Yes, after she confirmed |
| I've got 14 photos from today for the Everest album | media_createUploadLink | Gave her a link valid for 1 hour |
| Draft a 12-day Gokyo Lakes trek | trips_generate | Started a background job |
The first answer came back with the 9 travellers and their nationalities in a short list. Putting Pasang on the 14 November departure was a change, so Claude asked first; TripNerve then cleared the warning that the date had no lead guide. Anyone else already busy on those days would have been flagged as a clash, as on the Departures screen.
For the photos Claude gave her an upload link into the Everest album. She opened it in her phone's browser, without signing in, and the 14 photos went straight into the album on the website. The Gokyo draft ran on TripNerve's server while she walked down to Phakding the next morning. When she asked Claude about it later, it checked the job and told her the draft trip was ready to review in TripNerve.
Common mistakes
Connecting the wrong company
If you work for two companies, check the one you pick at sign-in. The connection works in that company only.
Sharing one owner login
Changes are recorded under whoever connected. Give each person their own TripNerve account and their own connection.
Approving every tool call unread
Changes take effect at once. Read what the app is about to do, especially cancellations and emails to travellers.
Leaving old connections in place
Disconnect apps you no longer use from AI apps, such as one set up on a laptop you've passed on.

