Bitvoya MCP

com.bitvoyaPublished by bitvoya.comOfficial publisherv0.3.1Updated Oct 24, 2026

Luxury hotel search, rate comparison, booking quotes, and secure checkout handoff.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle Business & Commerce

Server details

Identifier: com.bitvoya/bitvoya-mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to bitvoya.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.bitvoya%2Fbitvoya-mcp.svg)](https://sourceweft.com/mcp/com.bitvoya%2Fbitvoya-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Hosted MCP for luxury hotel search, rate and benefit comparison, quote preparation, and handoff to Bitvoya's own secure checkout.

What you can do: Route a request and search or compare luxury hotels by city
Read hotel details, rooms and rates, including structured benefits and promotions
Prepare booking quotes and create booking intents
Start a booking and poll order or handoff state
Hand the traveler off to a Bitvoya-hosted checkout surface for payment
When to use it: Use it when building or running an AI travel assistant, concierge or itinerary agent that needs premium hotel discovery, benefit-aware rate comparison and quote preparation, with payment kept off the chat surface.
Requirements: A remote Streamable HTTP endpoint; no self-hosting. A Bitvoya account and a revocable agent key created under Dashboard -> Connect Agent, sent as an Authorization bearer header. Manual testing outside an MCP client also needs an Accept header for JSON and event-stream.

Before you install

The agent key is a credential: keep it out of shared configs and revoke it if exposed. Booking intents and quotes create state on the Bitvoya account, and multiple agent keys map to the same account history. Card entry, payment and final supplier booking are not done by the agent; the traveler is handed to Bitvoya-hosted checkout. Hotel and rate data comes from Bitvoya, and returned payloads should be treated as the source of truth.

Installation

In SourceWeft

Open Bitvoya MCP in the dashboard and add it to a workspace.
Connect Authorization token credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.bitvoya%2Fbitvoya-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bitvoya": {
      "type": "http",
      "url": "https://bitvoya.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

[Bitvoya]

[Bitvoya MCP]

[Apache-2.0 License] [Hosted Remote MCP] [Streamable HTTP] [Recommended Models]

Luxury hotel intelligence and secure checkout handoff for AI travel agents.

Hosted public MCP for premium hotel discovery, benefit-rich rate comparison, quote preparation, and Bitvoya-controlled checkout completion.

Quick Start · Client Setup · Security Model · Secure Handoff · server.json

Public users connect to the hosted endpoint https://bitvoya.com/api/mcp with a Bitvoya-issued agent key from Dashboard -> Connect Agent. No self-hosting is required for normal usage.

Why Bitvoya MCP

Bitvoya is not a generic hotel feed wrapped in MCP. It is designed around luxury booking value and the handoff boundary real travel agents actually need.

What Bitvoya does well	Why it matters for agents
Luxury-first hotel coverage	Better fit for high-end trip planning, concierge, and member travel flows
Structured benefits and promotions	Agents can explain breakfast, upgrade eligibility, late checkout, and property credits without scraping prose
Explicit pricing semantics	`supplier_total_cny`, `service_fee_cny`, and `display_total_cny` stay distinct
Secure checkout handoff	Card entry and payment stay on Bitvoya-owned surfaces instead of agent chat
Remote hosted MCP	Users connect directly over Streamable HTTP with bearer auth

Built For

AI travel assistants
concierge and itinerary agents
premium membership travel copilots
Bitvoya-connected partner agents
workflows that care about stay quality, perks, and real booking value

Quick Start

1. Create an agent key

Sign in to https://bitvoya.com
Open Dashboard -> Connect Agent
Create a named agent connection

Direct page:

https://bitvoya.com/dashboard/agent-keys

2. Connect the hosted MCP

Use the hosted endpoint:

https://bitvoya.com/api/mcp

Add this header:

Authorization: Bearer <your_agent_key>

Minimal remote MCP configuration:

json

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

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

If you are testing manually outside an MCP client, also send:

Accept: application/json, text/event-stream

3. Start with a tool-driven travel prompt

Examples:

Search luxury hotels in Tokyo for next weekend and compare the best options.
Find five-star hotels in Paris with breakfast and explain which rate has the best value.
Prepare a booking quote for the strongest Shangri-La option in Singapore.

Recommended Models

Bitvoya works best when the driving model is strong at tool selection, stateful booking flows, and not hallucinating hotel details from prior knowledge.

prefer Claude 4.6, GPT-5.4, or comparable flagship reasoning models
these models follow quote, intent, and state-polling steps more reliably
smaller models can connect, but they are more likely to skip tools or blur pricing semantics
for weaker automatic tool choosers, the safest generic first-call entry tool is start_travel_planning
if the request is already clearly a live hotel search, start_hotel_search remains the hotel-specific fast path

Supported Client Setups

Client-specific setup guides are in docs/public/CLIENT_SETUP.md.

Client	Remote MCP	Notes
Cherry Studio	Yes	Use the wrapped import shape plus manual `Authorization` header entry
Cursor	Yes	Works with `mcp.json` and environment-backed bearer auth
Windsurf	Yes	Remote Streamable HTTP with custom headers
Claude Code	Yes	Use `claude mcp add --transport http`
GitHub Copilot CLI	Yes	Configure as remote HTTP MCP
Goose	Yes	Use the remote MCP endpoint and bearer header

What Agents Can Do

Bitvoya MCP is designed for discovery, comparison, quote preparation, and secure completion handoff.

Workflow	Primary tools
Generic first-step routing	`start_travel_planning`
City and hotel discovery	`start_hotel_search`, `search_hotels`, `compare_hotels`
Hotel detail and room/rate exploration	`get_hotel_detail`, `get_hotel_rooms`, `compare_rates`
High-level booking start	`create_booking`
Quote preparation	`prepare_booking_quote`
Booking intent creation	`create_booking_intent`
Order and handoff state polling	`get_booking_state`

Luxury Value Edge

Bitvoya is strongest when the traveler cares about premium stay value instead of just the lowest visible headline rate.

participating rates can surface breakfast, upgrade paths, early check-in, late checkout, and hotel credit such as USD 100 property credit
long-stay promotions such as stay 3 pay 2 and stay 4 pay 3 can materially change effective value
benefits and promotions are returned in structured output, so the agent can compare real booking quality instead of guessing from marketing copy

Benefit availability still depends on hotel, rate, market, and stay dates. Returned hotel and rate payloads should always be treated as the source of truth.

Booking Journey

Bitvoya intentionally keeps sensitive execution on Bitvoya-hosted surfaces.

The agent discovers hotels, rooms, and rates.
The agent prepares a booking quote and creates a booking intent.
The traveler is handed to a Bitvoya-hosted secure checkout surface.
The agent continues polling state with get_booking_state.

Public agents do not directly own:

raw card entry
payment execution
final supplier-facing booking submission

That boundary is deliberate. It keeps the public MCP useful without pushing payment risk or card handling into third-party chat tools.

Price Fields

Agents should present pricing carefully.

search-stage output may include supplier_min_price_cny as indicative discovery pricing
final room and rate evaluation comes from get_hotel_rooms
get_hotel_rooms returns:
- supplier_total_cny
- service_fee_cny
- display_total_cny
display_total_cny is the guest-facing total aligned with current Bitvoya product behavior

Docs Hub

client setup: docs/public/CLIENT_SETUP.md
FAQ: docs/public/FAQ.md
security model: docs/public/SECURITY_MODEL.md
secure handoff design: docs/public/SECURE_HANDOFF.md
release notes: docs/public/releases/v0.3.1.md
registry metadata: server.json
maintainer setup: DEVELOPMENT.md

License

This repository is licensed under Apache-2.0. See LICENSE and NOTICE.

The open-source license covers this repository's code and docs. It does not grant access to:

Bitvoya hosted production infrastructure
live hotel inventory and partner data feeds
Bitvoya-issued agent keys or user accounts
Bitvoya trademarks, brand assets, or service access outside normal product terms

Important Notes

Bitvoya calls this flow Connect Agent
the generated credential is a revocable agent key
website login credentials and MCP credentials are intentionally different
multiple agent keys under one Bitvoya user still map to the same Bitvoya account history
normal users connect to the hosted MCP and do not need direct database or server configuration

Source: README.md at commit b56a67c

Tools

This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

v0.3.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declaredRequired10 pts
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts