Guide for AI agents

Help a traveler use Well Travel through the same public website and client account they would use themselves. Connect through the client-authorized MCP tools or follow the browser flow below; both use the current client workflow.

MCP Streamable HTTP endpoint: https://well-travel.net/mcp

Connect an AI agent

  1. The client signs in to the client cabinet, opens Profile → AI agent access, creates a named key, and copies the secret. The full key is shown only once; each key can be revoked separately.
  2. In the MCP client, add a remote server using the endpoint shown above, transport Streamable HTTP, and a custom Authorization: Bearer <client key> header. The selected MCP client must support a fixed bearer key. Do not put the key in a chat, URL, prompt, or source-controlled file.
  3. The server supports MCP protocol revision 2026-07-28 and legacy 2025 revisions. All tools are scoped to the client account that issued the key.

Available tools: catalog_search, property_details, my_requests, create_rental_request, update_rental_request, react_to_option, reserve_option, request_booking_service, create_payment_link, and cancel_booking. The MCP resource welltravel://client/guide provides the workflow principles in machine-readable form.

How to assist the client

  1. Start at the public catalogue. Use its visible filters and listing details to find suitable homes. Availability and final terms must still be confirmed for the requested dates.
  2. To save requests and follow their progress, open the client cabinet. If the client has no account, choose client registration; otherwise sign in. Registration uses the site's email verification flow. The client must enter passwords, one-time codes, and any identity documents themselves.
  3. Submit a request from a listing, or use the cabinet's general request form for a search by city, dates, budget/preferences and other wishes. Check the dates and details with the client before submitting. A request is a request for a search, not a confirmed reservation.
  4. Track updates in My requests. Well Travel managers coordinate with hosts and may add proposed options to the request. The client can inspect an option, react to it, and use the on-screen reserve action where it is available. An option or reserve action alone does not guarantee availability or mean the booking is confirmed.
  5. After Well Travel confirms the property and booking, follow the cabinet's booking card for contract, guest details, payment schedule/links, chat, and other available stay services. Complete only the action shown for the current booking stage. A booking is confirmed only when the site or Well Travel explicitly shows confirmation.
  6. Before and during the stay, use only the services shown for that booking, such as check-in details, transfer or other service requests, and early/late check-in options. Near the end of the flow, submit a property review if the cabinet asks for one.
  7. Use the built-in chat for questions and clarifications. Keep conversation and request changes in the client's own account so they remain attached to the correct request.

How the service works

  • The public catalogue is for browsing; the client cabinet is where an authenticated client can see linked requests and continue their booking.
  • A submitted request is reviewed by the Well Travel team, who checks options with hosts. Catalogue details are not a live guarantee of availability, price, or host approval.
  • Requests move through stages as the team updates them. Read the current status and next action shown in the cabinet; do not infer confirmation from a message, reaction, or button click alone.
  • Contracts, payment links, and service actions appear only when enabled for that booking stage. Use the site's own documents and payment instructions; never invent payment details or mark a payment as complete.

Access and safe use

The MCP key represents the client who created it. It grants account-scoped access to this MCP server only; it is not a website password and does not grant manager or agent access. Revoke it from the client profile if it is exposed or no longer needed.

  • Never ask the client to disclose their website password or one-time code. The MCP connection uses a separate revocable key.
  • Confirm with the client before sending or changing a request, reacting to an option, reserving an option, generating a payment link, requesting an extra service, or cancelling a booking.
  • Collect and enter only information needed for the requested step. Do not expose passport data, private notes, or account information in messages or elsewhere.
  • A payment link does not charge the client. The client completes payment on the Well Travel payment page. The agent must never invent payment details or report payment as complete.
  • If an action is unavailable at the booking's current stage, explain the returned status and ask the client to continue through the cabinet or Well Travel support.