Run your tour business by talking.
Tourify ships an MCP server: paste one URL into Claude or ChatGPT and build itineraries, capture leads, create bookings and write your website's blog by describing what you want. Nothing to install, and the same permissions and audit trail as the web app.

A standard plug, not a chatbot widget.
The Model Context Protocol is an open standard, introduced by Anthropic, that lets an AI assistant use real software the way a person does: through named, permissioned actions. Tourify's MCP server exposes 101 of them, covering itineraries, departures, leads, travellers, bookings, rooms, suppliers, costs, your website's blog and read-only finance.
Nothing is scraped and nothing leaves your account behind your back. Your assistant calls the same API your team already uses, over a connection you approve with your ordinary login and can revoke from Settings in one click: rate-limited, org-scoped and capped to the role you chose. Revoke it and it loses access on its very next request.
The result: the CRM work that eats your evenings becomes a sentence you say to your assistant, and the record in Tourify stays as clean as if you had typed it in yourself.
Describe the trip. The itinerary builds itself.
Close the enquiry without opening a tab.
Answers, not report menus.
Permissions you control.
Three minutes, and your assistant is inside your CRM.
No download, no config file, no call with us — one URL pasted into Claude or ChatGPT. You need a Tourify Pro or Business account. MCP is not included on Free or Starter.
- 1
Copy your Tourify address
One URL, the same for everyone at your company. It is not a password — who you are, and how much the assistant may touch, is decided when you sign in at step 3.
https://mcp.tourify.in/mcp
- 2
Paste it into your assistant
https://mcp.tourify.in/mcp
Settings → Connectors → Add custom connector. Works on claude.ai and in the desktop app.
- 3
Sign in and choose what it can reach
You land back on Tourify to sign in and pick a role. Ops is what most people want: trips, itineraries, departures, bookings and the blog. That role is the ceiling on everything the assistant can ever do, and you can revoke the connection from Settings at any time.
- 4
Ask for something
Your assistant now holds 101 Tourify tools. Start with something you can check against the app — it will tell you which organisation it is connected to before it touches anything.
Which Tourify org am I connected to, and how full is my next departure?
The role you pick is the ceiling. An Ops connection cannot read invoices; no connection of any role can reach staff, billing or your API keys. Nothing here can delete a record or cancel a booking — those stayed in the app on purpose. And it works as you, so every change it makes is on the record under your name.
Your next itinerary is a sentence away.
Paste one URL into Claude or ChatGPT, sign in, and describe the trip. If you would rather we set it up with you on a call, we will.