How to Use Claude to Streamline Tour Operations: 10 Practical Workflows

November 10, 202611 min readAI & Automation

Short answer: a tour operator can use Claude for daily operations by connecting it to the scheduling system through MCP (Model Context Protocol). Once connected, Claude can read your departures, open staff positions and guide availability, and it can create or update tours on request. The work that benefits most is the repetitive checking and cross-referencing that fills an operations manager's morning: which tours still need a guide, who is free to cover a cancellation, whether next month has enough Spanish-speaking guides.

This article is a practical playbook. It shows how to connect Claude to EasyPlanning, then walks through ten workflows with example prompts, what Claude does behind each one, and where a person should stay in control. MCP is an open standard for connecting AI assistants to business software. If you want the background first, read What Is an MCP Server? Explained for Tour Operators.

Why Tour Operations Are a Good Fit for an AI Assistant

Running freelance guides across many departures is mostly information work. The decisions themselves are usually simple. Getting to them is slow because the facts are spread across a calendar, availability lists, guide profiles and booking emails.

A typical operations question looks like this: "Which of next week's departures in Vienna still have an open guide position, and who could cover them?" Answering it by hand means filtering the calendar, opening each departure, checking which guides marked themselves available, ruling out the ones already booked at that time, and comparing languages and skills. None of it is hard, and all of it takes time.

An AI assistant with direct access to structured schedule data can do that cross-referencing in one request and explain its reasoning. The operator keeps the judgment: who is the right person for a VIP group, whether a guide who is technically free is actually a good fit, and when to call someone instead of writing.

What it does not do is fix messy data. If departures live in one spreadsheet, availability in WhatsApp and guide skills in someone's head, there is nothing reliable for an assistant to read. AI pays off after scheduling lives in one system of record. Our guide to scheduling freelance tour guides covers that foundation.

What Claude Can and Cannot Do with EasyPlanning

Claude works only through the tools the EasyPlanning MCP server exposes. That list is deliberately focused on scheduling.

Two details matter in practice. First, schedule requests cover at most 92 days at a time, so a season review needs a few requests. Second, "open seats" means unfilled staff positions (guide, driver, assistant), not remaining tickets.

How to Connect Claude to EasyPlanning

You need a company account with access to API keys and a Claude client that can connect to a remote MCP server with a custom header.

1. Create a key. In EasyPlanning, open Settings → API Keys, create a key with a clear name such as "Claude – operations", and copy it.
2. Add the server. The server URL is https://api.easyplanning.io/mcp, the transport is Streamable HTTP, and the key goes in the x-api-key header. In Claude Code, that is one command:

claude mcp add --transport http easyplanning https://api.easyplanning.io/mcp --header "x-api-key: YOUR_API_KEY"

3. Check with a read request. Ask Claude to list your tour templates, then ask for departures in a short date range and compare the answer with your EasyPlanning calendar.

Connection screens differ between Claude apps, versions and plans. The MCP setup guide has the current values; if your client cannot send a custom header, use a client that can or ask us for help.

Tip: start every session by telling Claude your timezone and the city you mean. EasyPlanning returns times in UTC, and Claude converts them correctly when it knows where you are.

10 Workflows for Daily Tour Operations

Each workflow below lists an example prompt, what Claude does with the connected tools, and what you should check. Adapt the city, dates and language to your operation.

1. The Morning Check: Departures That Still Need Staff

Show all departures in the next 7 days that still have an open staff position. Use Europe/Vienna time, group them by day, and state the date range you checked.

Claude lists departures in the range with only unfilled positions included, then groups them for you. This replaces scrolling through the calendar and opening each tour. Asking it to state the date range is a cheap way to catch a misunderstanding about "next week".

2. Covering a Last-Minute Cancellation

Our guide for tomorrow's 10:00 Old Town walk just cancelled. Show who is free for that departure and compare their languages and skills with what the tour needs. Don't change anything yet.

Claude reads the departure, then asks EasyPlanning for guides whose declared availability covers it, who match the city and guide group, and who have no blockout or conflicting assignment. It then compares each candidate with the tour's language and skill requirements. Availability is not suitability: the candidate list is time and location only, so the comparison step is what makes the answer useful. For the rest of the process, see what to do when a tour guide cancels last minute.

3. Assigning the Replacement Safely

Assign Maria to the open guide position on departure 4812. Keep every other position exactly as it is and show me the before and after before you apply it.

Updating staff replaces the departure's complete staff configuration, so a careless update can remove other guides. Asking Claude to read the departure first, preserve the other positions and show the change before applying it avoids that. Afterwards, ask it to read the departure again and confirm the result.

4. Turning a Booking Email into a Departure

Create a departure of our Wine Country day trip from this booking email: date, start time in Lisbon time, booking and voucher numbers, partner, price, guest names and the hotel pickup as the meeting point. Show me the fields before you create it. (paste the booking email)

Claude finds the right template and creates the departure with the start time, price, booking number, voucher and partner reference. The departure inherits the template's duration, roles, notes and attachments. Claude then updates it with the guest names and the pickup address. Unless you ask otherwise, EasyPlanning's automatic assignment looks for matching guides as soon as the departure exists. Letting Claude extract the fields from the email removes the most error-prone retyping in tour operations.

5. Correcting Details Across Several Departures

The meeting point for all Danube Cruise departures next week moves to Pier 7, Handelskai 265. List the affected departures first, then update them after I confirm.

Claude lists the departures for that tour and range, waits for your confirmation, then updates each one. Asking for the list first gives you a natural checkpoint and a record of what changed.

6. Checking Language Coverage Before the Season

For April, compare the Spanish-language departures in Barcelona with the guides who marked availability in April. Which days look short on Spanish-speaking guides?

Claude reads departures filtered by city and language, reads availability windows for the month, which include each guide's languages, and compares the two. Treat the result as an early warning, not a guarantee: declared availability changes, and existing assignments are only fully accounted for in the per-departure candidate check.

7. Guide Workload and Fairness

How many departures does each guide have confirmed between 1 and 30 June? Flag anyone with more than 20 or with back-to-back days without a break.

Claude reads the month's departures, counts confirmed positions per guide, and highlights the outliers. Freelance teams stay loyal when work is spread fairly; this check makes imbalances visible before a guide complains or burns out.

8. Setting Up a New Tour Product

Create a new tour template: "Jewish Heritage Walk" in Kraków, 3 hours, English and Polish, one guide, meeting at Szeroka 24, price 45 EUR per person. Use our existing tags for history tours.

Claude searches for the correct city, reads your existing tags so it uses real skill codes instead of inventing them, and creates the template. Review the result in the Tours page before scheduling departures from it.

9. The Weekly Briefing

Write a short operations briefing for next week: number of departures per city, departures still missing staff, multi-day tours starting, and anything unusual. Keep it under 200 words.

Claude turns raw schedule data into a summary you can paste into a team chat or a Monday meeting. Because it reads live data, the briefing is current at the moment you ask, not as of the last export.

10. Auditing Your Tour Catalog

Review all our tour templates. List any without a price, without attachments, or without a meeting address, and any duplicates that look like the same tour.

Claude reads every template with its prices, notes and attachments and gives you a cleanup list. A tidy catalog makes every other workflow above more reliable, because departures copy their defaults from templates.

How to Write Prompts That Work for Operations

A few habits make the difference between a vague answer and a reliable one:

• Name the place and timezone. "Next Monday in Lisbon" is unambiguous; "Monday" is not.
• Ask for the range it checked. Claude will state the exact dates, which catches misunderstandings early.
• Separate looking from changing. End exploratory prompts with "don't change anything yet", and ask for a preview before any write.
• Refer to IDs once you have them. After Claude lists departures, "departure 4812" is safer than "the 10:00 walk".
• Ask it to verify. After a change, "read the departure again and confirm" takes seconds.

Safety Rules for Connecting AI to Your Schedule

A company API key allows real changes to your schedule. Treat it like a password with write access:

1. Create one named key per connection, so you can revoke one without breaking another.
2. Store it only in the client's credential settings, never in a shared document or a prompt.
3. Keep tool confirmations on in Claude for actions that create or update departures.
4. Start with read-only questions until you trust the setup.
5. Delete the key in Settings → API Keys as soon as a connection is no longer needed or a device is lost.

The assistant is a fast, tireless colleague for checking and data entry. Decisions about people, such as who leads a sensitive group or how to handle a guide who cancels repeatedly, stay with you.

Where to Start

Pick the workflow that costs your team the most time today. For most operators that is the morning check or covering cancellations. Run it read-only for a week next to your usual process and compare the answers. Once they match, let Claude handle the routine version and spend the saved time on guests, guides and new products.

FAQ

Can Claude manage my tour schedule?

Connected to EasyPlanning through MCP, Claude can read departures, staff positions and guide availability, and it can create tour templates, create departures and update them. It works only through the tools EasyPlanning exposes, and a person should review every change.

Do I need a developer to connect Claude to EasyPlanning?

No. A company administrator creates an API key in EasyPlanning and adds the server URL and key to an MCP client that can send a custom header, such as Claude Code. The setup guide at easyplanning.io/docs/mcp lists the values.

Can Claude assign a guide to a tour?

Yes, by updating the departure's staff positions. The update replaces the departure's full staff configuration, so ask Claude to read the departure first, keep the other positions, and show the change before applying it.

Can Claude message guides or customers for me?

Not through the EasyPlanning connection. It can draft messages from schedule data, but sending emails, chat messages and guide notifications still happens in EasyPlanning or your own tools.

Is it safe to give an AI assistant access to scheduling data?

Treat the API key like a password with write access. Use a separate named key per connection, store it only in the client's credential settings, keep confirmations on for write actions, and delete the key when it is no longer needed.

Does this work with ChatGPT or other assistants?

EasyPlanning uses the open Model Context Protocol, so any client that supports remote Streamable HTTP servers and a custom authentication header can connect. Availability depends on the product and plan.