Bitvoya MCP

What Bitvoya MCP MCP server does

Bitvoya MCP MCP server gives AI travel assistants access to Bitvoya’s luxury-focused hotel discovery and booking workflow. It is intended for concierge agents, itinerary assistants, premium membership travel copilots, and partner agents that need to compare stay value rather than only headline prices.

The service returns structured hotel, room, rate, benefit, and promotion information. Depending on the property and rate, results may include breakfast, upgrade eligibility, early check-in, late checkout, hotel credits, or long-stay offers such as stay-three-pay-two. Availability depends on the hotel, market, rate, and dates, so returned payloads should be treated as the source of truth.

Pricing is separated into distinct fields. Search results can include indicative supplier_min_price_cny values, while room and rate evaluation provides supplier_total_cny, service_fee_cny, and the guest-facing display_total_cny.

How it works

Bitvoya MCP MCP server is a hosted remote MCP service available at https://bitvoya.com/api/mcp. Clients connect using Streamable HTTP and send an Authorization: Bearer header containing a Bitvoya-issued agent key. The normal flow does not require local deployment, direct database access, or server configuration.

An agent can begin with generic routing through start_travel_planning, or use start_hotel_search when the request is already a clear hotel search. It can then search and compare properties, inspect rooms and rates, prepare a quote, create a booking intent, and poll the resulting state.

Sensitive completion steps remain outside the public MCP conversation. After quote preparation and intent creation, the traveler is directed to a Bitvoya-hosted checkout surface. Card entry, payment execution, and final supplier-facing submission are not owned directly by the public agent.

Setup and configuration

Create an agent key by signing in at Bitvoya, opening Dashboard -> Connect Agent, and creating a named agent connection. The direct agent-key page is https://bitvoya.com/dashboard/agent-keys.

Configure the remote MCP endpoint with the bearer credential:

{
  "type": "streamable_http",
  "url": "https://bitvoya.com/api/mcp",
  "headers": {
    "Authorization": "Bearer <your_agent_key>"
  }
}

Manual tests outside an MCP client should also send Accept: application/json, text/event-stream. Cursor, Windsurf, and Claude Code have documented remote setup paths in the project materials. The credential is a revocable agent key and is separate from a Bitvoya website login password.

Tools and capabilities

Bitvoya MCP MCP server groups its tools around the following workflows:

• start_travel_planning for general first-step routing
• start_hotel_search, search_hotels, and compare_hotels for discovery
• get_hotel_detail, get_hotel_rooms, and compare_rates for property and rate evaluation
• create_booking for starting a booking flow
• prepare_booking_quote for quote preparation
• create_booking_intent for recording booking intent
• get_booking_state for polling order and handoff status

These tools support searches by destination and dates, comparison of premium benefits, inspection of available rooms and rates, and progression toward secure checkout. Strong tool-using models are recommended because the workflow depends on correct tool selection, quote handling, and state polling.

Limitations and notes

The repository and documentation are licensed under Apache-2.0, but that license does not provide access to Bitvoya’s hosted production infrastructure, live inventory, partner feeds, issued agent keys, accounts, or service access outside normal product terms.

The service is designed around Bitvoya’s hosted endpoint. Benefit availability and final pricing can change with property, rate, market, and stay dates. Smaller models can connect, but the documentation notes that they may skip tools or confuse pricing fields more often. Multiple agent keys under one Bitvoya account still map to that account’s booking history.