Hotelbooking vs Voyagier
A side-by-side look at the Hotelbooking and Voyagier MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hotelbooking for travel & transportation work over a hosted endpoint; choose Voyagier for travel & transportation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hotelbooking when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a remote HTTP/SSE transport.
Choose Voyagier when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
VOYAGIER_TOKEN. - You want tools like
doctor, clients_list, client_create.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 47/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | VOYAGIER_TOKEN |
| Verified owner |
Tools & capabilities
Hotelbooking tools
No tool names declared yet. Check the project README from the listing page.
Voyagier tools 21
doctorHealth check: auth, schema, state, version.clients_listRoster of CRM clients; `page`/`limit` page through it.client_createIdempotent by email; a plan needs a client.plans_listOwned + shared plans in one list, each tagged `relationship` `owner`/`shared`; the plan-discovery entry point. `relationship`/`active`/`page`/`limit` filter and page it.search_destinationsFreeform text → ranked structured destinations; run before `plan_trip`.plan_tripScaffold a plan + goal graph from a `template`; returns `nextSteps`. `travel_destination_id` (from `search_destinations`) is preferred over the freeform `destination`.travellers_addAdds the whole party in one call; required before search.search_flightsAsync — `optionCount 0` means poll options.search_hotelsPrices are stay totals, not nightly.search_activitiesBookable per slot.get_selection_optionswait` (default true) polls the async fetch to completion.refresh_optionsRe-fetch a selection's options; `force` after a fetch error.- +9 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Hotelbooking
{
"mcpServers": {
"hotelbooking": {
"url": "https://mcp.rollinggo.cn/mcp"
}
}
}
Voyagier
{
"mcpServers": {
"voyagier": {
"command": "npx",
"args": [
"-y",
"@voyagier/cli"
],
"env": {
"VOYAGIER_TOKEN": "YOUR_VOYAGIER_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Hotelbooking is categorized under Travel & Transportation and uses a remote HTTP/SSE transport. Voyagier belongs to Travel & Transportation and uses a local stdio subprocess. Pick Hotelbooking for travel & transportation work and Voyagier for travel & transportation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Hotelbooking has no declared pricing — check the project's own site. Voyagier has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hotelbooking and voyagier as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hotelbooking has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 11 GitHub stars. Voyagier has 57/100 (Good) with 3 views, 0 installs and 1 GitHub stars.