Back to blog

    What Is an MCP Server? Explained for Tour Operators

    Tour operator working late beside a rainy Vienna street with scheduling software and an AI assistant
    July 14, 20266 min readAI & Automation

    An MCP server is a standardized connection that lets an AI assistant work with business software. For a tour operator, that can mean asking an assistant to create a scheduled departure, update a meeting point, or inspect reusable tour details without copying data between a spreadsheet and a chat window.

    MCP stands for Model Context Protocol. Anthropic introduced it as an open standard in November 2024, and it is now supported by a growing range of AI products. OpenAI, for example, supports custom MCP-based apps in ChatGPT, subject to plan and workspace settings.

    That is the technical vocabulary you need. The useful question is what this connection changes inside a tour operation.

    What Problem Does MCP Solve for a Tour Operator?

    An AI assistant can write a customer email or summarize a document without seeing your internal systems. It cannot reliably answer operational questions or change a schedule unless it has an approved way to reach the relevant data and actions.

    Without a connection, the workflow usually looks like this:

    1. Export data from the scheduling system.
    2. Paste or upload it to the assistant.
    3. Ask the question.
    4. Manually carry the answer back into the original system.

    The information starts going stale as soon as it is exported. The assistant also has no reliable way to know which fields are required, which guide qualifications exist, or how a valid scheduled tour should be created.

    MCP replaces that improvised handoff with a defined set of tools. The scheduling platform describes what the assistant is allowed to call, what inputs each action needs, and what structured result comes back.

    MCP does not make an AI omniscient. It gives the AI a controlled, documented doorway into the specific data and actions a software provider exposes.

    What Can You Actually Ask Once It Is Connected?

    The answer depends on the tools exposed by the MCP server. A connection is not automatic access to every screen and report in a product.

    EasyPlanning's current MCP server focuses on concrete tour-scheduling work. It can expose tools for:

    • listing reusable tour templates and their languages, skills, roles, prices, notes, and attachments;
    • listing the configured tags used to match tours and freelancers;
    • finding the correct city before a tour is created;
    • creating a reusable tour template;
    • scheduling a departure from an existing tour template; and
    • updating a scheduled tour's details, including time, meeting address, language, booking information, attachments, customers, or seat assignments.

    That makes prompts like these practical:

    Show me our existing Vienna tour templates and the languages each one supports.

    Find the correct city and create a reusable English-language Old Town walking tour with two guide seats.

    Schedule the Old Town tour for July 24 at 09:00 in Europe/Vienna and add the booking number.

    Update scheduled tour 4812 with the new meeting address and voucher number.

    Those examples map to defined tools. Questions about reports, fill rates, or unassigned departures require the server to expose those read capabilities first. That distinction matters: MCP is the connection standard, while the server's tool catalogue determines what the assistant can actually do.

    Do You Need a Developer to Connect It?

    Not when the scheduling platform already provides the MCP server.

    For EasyPlanning, a company administrator creates a named API key in Company Settings → API Keys, then adds the EasyPlanning server URL and key to a compatible AI client. The exact screens differ between Claude, ChatGPT, and other MCP clients, and some products limit custom connections by plan or administrator policy.

    Our EasyPlanning MCP setup guide contains the current endpoint and client-specific configuration. Once the connection is active, the people using it can work in ordinary language. They do not need to write integration code for every request.

    The deeper requirement is still good operational data. If scheduling is spread across unrelated spreadsheets and WhatsApp threads, there is no single current record for an assistant to use. AI does not repair a fragmented process by itself. It becomes more useful after tours, guide requirements, assignments, and availability live in a structured system. If that is your current bottleneck, start with our guide to moving beyond spreadsheet scheduling.

    Is It Safe to Connect AI to Scheduling Data?

    An MCP connection should be treated like any other privileged software integration.

    EasyPlanning authenticates the public MCP connection with a company-scoped API key. That key can be revoked, but while it is active the connected client can call the read and write tools exposed to API-key sessions. It is therefore important not to describe the key as harmless or automatically read-only.

    Use a practical control checklist:

    1. Create a separate, clearly named key for each AI connection.
    2. Copy it only into a trusted client and never place it in a shared document or prompt.
    3. Review the tools the client asks to call, especially before creating or changing scheduled tours.
    4. Keep confirmation prompts enabled for consequential write actions when the AI client supports them.
    5. Revoke the key immediately when the connection is no longer needed or a device is lost.

    The operator remains responsible for deciding which assistant is trusted and which changes require human review. MCP makes the boundary explicit; it does not remove the need for that judgment.

    Why Does This Matter Now?

    The useful shift is not that an AI can chat about tour operations. It is that the assistant can work through the same structured records your team already uses.

    That reduces context switching for repeatable tasks: preparing a new tour template, scheduling a departure, correcting booking details, or updating an assignment. It also creates a foundation for richer operational questions as more read tools are added over time.

    EasyPlanning already runs a public MCP endpoint rather than presenting MCP as a roadmap concept. Existing customers can follow the setup guide and connect a compatible client today. Operators still on disconnected spreadsheets should solve the data structure first; once the system of record exists, the AI connection is the smaller step.

    FAQ

    What does MCP stand for?

    MCP stands for Model Context Protocol, an open standard for connecting AI applications to external systems, data, and tools.

    Which AI assistants can use an MCP server?

    Claude supports MCP connections, and ChatGPT supports custom MCP-based apps on eligible plans and workspaces. Availability and setup can vary by product plan and administrator settings.

    Is MCP the same as an API?

    They are related but not identical. An API exposes software capabilities, while MCP gives AI applications a standard way to discover and call approved capabilities.

    Can an AI change my schedule or assign guides on its own?

    An EasyPlanning API-key connection can expose both read and write tools. The AI can only use the tools the server provides, and you can revoke the key at any time, so use a trusted client and review consequential changes.

    My scheduling is in Excel. Can I connect that to AI?

    An AI can read a clean spreadsheet, but the result is only as current and structured as the file. A scheduling platform is more reliable for live operational work because tours, assignments, and availability have defined records and workflows.

    Connect an AI assistant to EasyPlanning

    Follow the current setup guide to create an API key and connect a compatible MCP client, or book a short demo if you want to see the workflow first.

    Written by Steve, Co-founder of EasyPlanning and tour operator. Published .