Product guide: Connect an AI assistant

    Connect an AI assistant

    Connect a compatible MCP client to EasyPlanning so an external assistant can use your company’s tour and scheduling tools.

    What you need

    • A company account with access to Settings → API Keys.
    • An MCP client that supports a remote Streamable HTTP server and a custom authentication header.
    • Your intended company, dates, and timezone when asking about schedules.

    Connection screens vary by assistant and version. Use the values below in your client’s supported remote-server setup. If it cannot send the custom header, use a compatible client or ask for setup help.

    Connect in three steps

    1. Create a company key. Open Settings → API Keys, create a key, and copy it when it is shown.
    2. Add a remote MCP server in your client. Enter these connection values and replace the placeholder with your key.
      Server URL
      https://api.easyplanning.io/mcp
      Transport
      Streamable HTTP
      Header name
      x-api-key
      Header value
      YOUR_API_KEY
    3. Verify with a read request. Ask the assistant to list your company’s tour templates. Then request a small date range of departures and compare it with Calendar.

    What the connected assistant can do

    Read and explore

    List tour templates and tags, search cities, inspect dated departures and staff positions, read freelancer availability, and list candidates for a departure.

    Make scheduling changes

    Create tour templates and dated departures, or update a departure through the available write tools. Specify the intended change and check the result in the application.

    The MCP toolset does not include every app screen or report. Candidate availability is not a complete suitability check; also review role, languages, skills, and other tour requirements.

    Try these requests

    • “List our tour templates and the staff roles each one needs.”
    • “Show departures in Vienna next week that have open staff positions. Use Europe/Vienna time and state the dates you checked.”
    • “Show candidates for this departure and compare their roles, languages, and skills with its requirements.”

    For date-range tools, the client must supply full datetimes with a timezone. Schedule range requests cover at most 92 elapsed days; use smaller ranges for longer planning periods. Open positions refer to tour staff, not remaining tickets.

    Use company keys carefully

    A company API key permits scheduling writes through the exposed tools. Store it in the client’s credential settings and delete it in Settings → API Keys when the connection is no longer needed. Start with read requests before trying a write.

    When updating staff positions, the scheduling tool replaces the departure’s complete staff configuration. Preserve the other positions and review the resulting Team after the change.

    For ready-to-use requests, read 10 practical workflows for tour operations with Claude.

    Get connection help