Agentic Hospitality

Turneo MCP server

Turneo’s MCP server lets an AI assistant work for a hotel’s guests: search and book the hotel’s experiences and services, check rooms, and send restaurant, room service and housekeeping requests to the hotel’s team. It is the server behind Turneo’s ChatGPT app, with 21 tools.

Turneo sets the server up for each hotel or hotel group and gives you its endpoint; there is no self-serve sign-up. It comes with a Turneo partner account. The tool list is also available as JSON.

How it works

What to know before you connect

The server sits in the agent layer of the stack: experience tools call Turneo, room tools call the hotel's PMS or booking engine, and request tools email the hotel's team.

See the stack
Transport
Streamable HTTP, stateless. Any MCP client that speaks it can connect, including ChatGPT apps.
Endpoints
One per hotel, or one per hotel group with list_hotels and select_hotel to choose the hotel. Turneo creates them for your account.
Tools per hotel
Each hotel gets the tool groups for the services it has switched on in Turneo. A tool the hotel hasn't enabled returns an error saying so.
Annotations
Every tool declares readOnlyHint, destructiveHint and openWorldHint, so clients can tell reads from actions before calling.
Conversation state
The server keeps each conversation's hotel, open order and pending requests, so tools like complete_order need no IDs.
Widgets
In ChatGPT, experience, room and restaurant results render as cards with photos and a booking link.

Tools

Every tool, by group

Inputs ending in ? are optional. Tools marked Acts change something outside the conversation, so an assistant should confirm the details with the guest before calling them.

Read-only:
Reads data; changes nothing.
Session:
Changes only the current conversation.
Acts:
Books, orders or sends a message outside the conversation. Get the guest's confirmation first.

Experiences and services

Available: When the hotel has experience booking enabled. Works with: Turneo: the same catalogue, availability and booking orders as the Turneo API.

  • search_experiencesRead-only

    Searches the hotel's experiences: tours, activities, spa treatments and other services. Returns each with its description, duration, price and a booking link.

    Inputs: query?, interests?, group?, date_from?, date_until?

  • get_experience_detailsRead-only

    Full details of one experience: description, duration, pricing, what's included and a booking link.

    Inputs: experience_id?, experience_name?

  • check_experience_availabilityRead-only

    Available time slots for an experience on the given dates, with prices and remaining capacity.

    Inputs: date_from, experience_id?, experience_name?, date_until?

  • create_experience_orderActs

    Creates a Turneo booking order (a cart) with its first booking, using a slot from check_experience_availability.

    Inputs: date, party_size, experience_id?, experience_name?, rate_id?, availability_id?, time?, rates_breakdown?, guest_name?, guest_email?, guest_phone?, special_requests?

  • add_to_orderActs

    Adds another booking to the open order.

    Inputs: experience_id, date, party_size, rate_id?, availability_id?, time?, rates_breakdown?, order_id?, experience_name?, special_requests?

  • complete_orderActs

    Checks the order out with the guest's details. A free order is confirmed at once; a paid one returns a payment link, and is confirmed once the guest pays.

    Inputs: guest_name?, guest_email?, guest_phone?

  • check_order_statusRead-only

    Payment and booking status of the conversation's current order.

    No inputs

Restaurants

Available: When the hotel has restaurant requests enabled. Works with: The hotel's restaurant details in Turneo; requests go to the restaurant by email.

  • get_restaurant_optionsRead-only

    The hotel's restaurants that match the guest's preferences, with cuisine, opening hours, location and description.

    Inputs: cuisine?, party_size?, date?, time?, special_requests?, price_range?, ambiance?

  • get_restaurant_detailsRead-only

    Hours, cuisine, price range, location and special features of one restaurant.

    Inputs: restaurant_name

  • send_restaurant_booking_requestActs

    Emails a reservation request to the restaurant. This is a request, not a confirmed table: the restaurant replies, usually within a few hours, and get_pending_requests shows the answer.

    Inputs: restaurant_name, date, time, party_size, guest_name?, guest_email?, guest_phone?, special_requests?

Rooms

Available: When the hotel has room booking enabled. Works with: The hotel's PMS or booking engine, depending on how the hotel is connected.

  • get_room_availabilityRead-only

    Room types with prices and a booking link for the given dates. Called without dates, it recommends room types instead.

    Inputs: check_in_date?, nights?, adults?, child_ages?

  • send_room_inquiryActs

    Emails a room inquiry to the hotel; get_pending_requests shows the reply.

    Inputs: check_in_date, nights, adults, child_ages?, guest_notes?

  • book_roomActs

    Creates a room reservation in the hotel's PMS. Only for hotels whose PMS is connected.

    Inputs: room_name, check_in_date, nights, adults, guest_name, guest_email, child_ages?, guest_notes?, guest_phone?

Room service

Available: When the hotel has room service orders enabled. Works with: The hotel's menu in Turneo; orders go to the hotel's team by email.

  • get_room_service_menuRead-only

    The room service menu, with items, prices and hours.

    No inputs

  • get_menu_item_detailsRead-only

    Finds an item on the room service menu, with its price and description.

    Inputs: item_name

  • place_room_orderActs

    Sends a room service order to the hotel's team.

    Inputs: items, room_number?, special_requests?, delivery_time?

Housekeeping

Available: When the hotel has housekeeping requests enabled. Works with: Requests go to the hotel's team by email.

  • request_housekeepingActs

    Sends a housekeeping request (cleaning, towels, amenities) to the hotel's team.

    Inputs: service_type, room_number?, notes?

Hotel information

Available: Always. Works with: The hotel's own knowledge base and the conversation's open requests.

  • search_hotel_infoRead-only

    Searches the hotel's knowledge base: pool hours, parking, wifi, check-in and check-out times, policies, amenities. It has no access to individual guests' reservations.

    Inputs: query

  • get_pending_requestsRead-only

    Status of the conversation's open requests (restaurant reservations, room inquiries), including the hotel's reply once it arrives.

    No inputs

Hotel selection

Available: Always. Only needed on a hotel group's endpoint; a hotel's own endpoint is already scoped to it. Works with: The hotels in your Turneo account.

  • list_hotelsRead-only

    The hotels behind this endpoint.

    No inputs

  • select_hotelSession

    Picks the hotel the rest of the conversation is about, and returns the tools that hotel has enabled.

    Inputs: hotel_id

Building your own agent?

Use the Turneo API for full control

The MCP server is a ready-made set of guest tools. To build your own guest or staff agent, wrap the Turneo API in your own tools instead: the same catalogue, availability and booking orders, plus booking operations and the activity feed.