Start the week with everything in view
Check upcoming departures, see what is still open and keep the team’s feedback list moving.
Which confirmed trips leave in the next 14 days, and what still needs a payment, voucher or supplier confirmation?
Agents
Use your templates, hotels and inbox from the assistant you already work with — with you in control of what gets sent.
Give this to your agent:
Check upcoming departures, see what is still open and keep the team’s feedback list moving.
Which confirmed trips leave in the next 14 days, and what still needs a payment, voucher or supplier confirmation?
Read incoming requests, pull out the details and record what changed after your call.
Summarize the Hartmann request. Update the budget to €12,000 and note that they prefer a quieter final day.
Search your templates, past trips and hotel library, or read a trip from a web page, make the first proposal from what fits — or lay out a new itinerary, and put a second version of the same journey next to it.
Find our Oman trips for a family of four, then create a draft for the Hartmann family from the ten-day template and add a premium option next to it.
Read the itinerary and its history, reshape days and hotel stays, adjust items, services and images, write copy and review suggestions.
Add a quiet day in Jabal Akhdar, split the four nights in Muscat into two stays, move the village walk earlier and rewrite the day text in our brand voice.
Read a trip’s booking and payment status, or compare agency revenue by year, destination or advisor.
Show this year’s revenue by destination, then check the outstanding balance on the Hartmann booking.
See how the trip reaches the customer — brand, public contact and the conditions the page shows — and publish it without sending anything.
Publish the Hartmann offer under our own brand with Lena as the contact, and show me the public link.
Review the recipient, subject and message before you explicitly approve sending the offer.
Prepare the Hartmann offer email and show me the preview. Wait for my approval before sending.
Read your workspace without changing it.
Create and update requests and drafts. Changes stay inside Tourvy and are visible to your team.
Destructive actions need explicit confirmation. Removing items from a confirmed trip is refused.
An offer email needs a preview and your explicit approval before it reaches a guest.
On confirmed trips, item additions and replacements require suggestions with a reason. Day structure and other direct edits remain restricted. Reading and reviewing suggestions stay available.
An OAuth client needs no Tourvy token pasted anywhere: it asks for access, you approve it once, and your agency appears in the assistant you already use. Scripts use a personal token instead.
OAuth with PKCE. It registers itself.
The same handshake, from the terminal.
Dynamic Client Registration, no key to paste.
Dynamic Client Registration, no key to paste.
Talks to the same MCP endpoint; the app manifest and the directory submission are still open.
For scripts: one token, one security level.
The answer path is built; the Slack and Teams routes are switched off.
A thin macOS window around the hosted app, with a native menu and tourvy:// deep links. Built, not yet signed or handed out.
Apple Foundation Models behind that shell, as the “Privacy Mode” add-on. Not started.
Anthropic's connector directory and ChatGPT Apps both run on MCP; what is missing is the ChatGPT app manifest and the trip, request and departure cards its interface expects.
Planned: browser agents could work with tools exposed directly by the Tourvy page, without connecting a separate MCP server.
For developers: 50 tools, with parameters and security levels, in skill.md and the MCP registry.