All servers · Travel & booking

Aurinia — book across venues via your AI assistant

online.aurinia/connect · v0.1.1

Measured by MCP Station

Description written by the publisher, not verified

Find availability and book across a network of independent venues via your AI assistant.

Connect

claude mcp add --transport http connect https://aurinia.online/mcp

{
  "mcpServers": {
    "connect": {
      "url": "https://aurinia.online/mcp"
    }
  }
}

Tools as reported by the server

• find_providers
  Find a venue in the Aurinia network (doctor, hostel, spa). Optional: query (e.g. 'vertebrologist'), city, type. Returns a providers array; use a provider_id from it for get_availability / book.
• get_provider_info
  Details for one venue by provider_id: id, type (doctor/hostel/spa), name, city, address. Read-only, no auth. Use it to confirm a venue before get_availability / book.
• get_availability
  Availability and price at a venue. provider_id is required. Use EXACTLY these param names: doctor — date (YYYY-MM-DD); hostel — check_in, check_out, guests (with underscores: check_in/check_out, NOT 'checkin'/'checkout'; guests is an integer). There is no room_type param — a dorm bed is the default.
• book
  REAL action: book at a network venue on the user's behalf. provider_id + item (the venue interprets it). Doctor: item={date,time}. Hostel: item={check_in,check_out,guests,promo_code?} — do NOT ask for name/contact: identity comes from a one-time Telegram consent. Spa: item={date,time,procedure}. Hos
• reschedule
  REAL action: reschedule a booking at a network venue. provider_id + item (doctor: {date, from, to} — SAME day, ATOMIC: if the target slot was just taken, the user KEEPS their current slot — never loses the held slot; that guarantee is the point). For a DIFFERENT day just book again (cross-day needs
• cancel
  REAL action: cancel a booking at a network venue IMMEDIATELY — no confirmation step. If the user said cancel, cancel; do NOT re-ask (repeated confirmations frustrate users — act decisively). provider_id + item {booking_id} — the booking id from list_current_bookings. Do NOT ask for consent up front
• list_current_bookings
  The user's current/upcoming bookings at a network venue (by date, nearest first). Each has a status field (e.g. booked/confirmed/cancelled) — distinguish active vs cancelled. provider_id optional (without it — the first venue). Requires authorization.
• list_past_bookings
  The user's past bookings at a network venue (by date, most recent first). Each has a status field. provider_id optional; limit (default 20)/offset for pagination. Requires authorization.

JSON · Text for agents · Registry updated 2026-08-27