One MCP server with verified facts about the five Travellers Group properties and their towns — rooms, distances, events, local guides, policies — plus honest property matching, direct-booking handoff and consented enquiries. Five properties across regional NSW & QLD: Burnett Riverside (Bundaberg), Cityville (Rockhampton), Bluegum (Dubbo), Yallungah Boutique Hotel (Orange), Emerald Inn (Emerald).
MCP · Streamable HTTP · stateless en-AU v1
Point any MCP-capable client at the endpoint:
{
"mcpServers": {
"travellers-group": {
"type": "http",
"url": "https://agent.travellersgroup.com.au/v1/mcp"
}
}
}
Or call it directly — JSON-RPC 2.0 over HTTP POST:
curl -X POST https://agent.travellersgroup.com.au/v1/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
Machine mirror: OpenAPI 3.1 · status: /status.json
search_contentSearch the published six-site Travellers Group corpus (guides, hubs, FAQs, pages). Returns ranked answer capsules (≤120 words) with canonical URLs.
Example: “What is the pet policy at Travellers Group properties?”
get_propertyCanonical entity record for a Travellers Group property: address, contacts, quick facts, policies, booking URL, parent entity.
Example: “Give me the address and phone number for Bluegum Dubbo.”
get_room_typesRoom catalogue for a property: occupancy, bedding, amenities, who-it-suits, booking deep link per room. traveller_context re-ranks honestly — it never invents inclusions.
Example: “Which rooms at Yallungah Boutique Hotel have a balcony?”
get_distancesMeasured distances from a property (km, drive/walk minutes) to hospitals, mines, airports, venues, wineries. Fuzzy destination filter ('the zoo', 'hospital'). Serves published measured figures only.
Example: “How far is Bluegum Dubbo from Taronga Western Plains Zoo?”
get_eventsVerified events for a town. Serves only entries published with explicit dates — never extrapolates a date.
Example: “What events are on in Orange NSW?” — answers only from published, structured event data; it never parses prose into dates.
get_town_guideTown knowledge layer: open-late, essentials, eat, with-kids, working-in, hospital-visitor, itineraries. Unbuilt topic returns 'not yet published' plus the town guide root.
Example: “Plan two days in Bundaberg staying at Burnett Riverside.”
get_indicative_ratesIndicative rate ranges from the published, commercially-signed rate module only — framed as indicative, never a quote. Where no figure is published, returns the booking link instead (never an estimate).
Example: “Roughly what does a night in Rockhampton cost?” — serves only signed rate strings; until they exist it returns the booking link honestly.
recommend_propertyHonest matching across the Travellers portfolio. If no Travellers property suits the need, says so plainly and names the accommodation category that does. Never oversells. [Templates DRAFT pending G1.]
Example: “I am travelling to Dubbo with a dog — where can I stay?” — honest matching, including honest declines.
check_availabilityTier A handoff: returns a dated, pre-filled booking-engine link — LIVE availability and pricing are at that link. This tool never asserts that dates are available.
Example: “Is there a room in Dubbo 12–14 August for 2 adults?” — returns a dated, pre-filled direct-booking link; makes no availability claim either way.
create_enquirySends a booking enquiry to the property team (groups, crews, blocks, weekly stays, functions). Requires the guest’s explicit consent to pass their details and conversation context to the property.
Example: “Ask the hotel whether a ground-floor room is possible for those dates.” — requires explicit guest consent before anything is sent.
get_corporate_account_infoThe Travellers Group corporate-account answer as data: one account, five properties, direct billing and consolidated invoicing.
Example: “How do corporate accounts work across the group?”
create_corporate_enquiryCorporate-account or group-booking enquiry, routed to the Travellers Group corporate team. Requires guest consent, as with create_enquiry.
Example: “Set up a corporate rate conversation for my company.” — requires explicit consent.
check_availability returns a dated, pre-filled direct-booking link and says plainly that no availability data is integrated.Every response carries provenance (canonical source URL, property, date current as at) and this footer: “Information maintained by Travellers Group. Rates indicative — live availability and pricing at the booking link. Book direct for best rate.”
We store intent, not identity. Tool calls are logged as: timestamp, tool name, scrubbed parameters, outcome and duration — used to improve answer quality and coverage. No user identifiers are stored; contact fields are stripped wholesale and free text passes a PII scrub before logging. Raw telemetry is retained for 90 days, then only aggregates. The single exception: when a guest gives explicit consent to send an enquiry, the enquiry content (including contact details) is delivered to the property team and retained in their enquiry system under its policy — that is the point of the tool, and it happens only with consent.