webhotelier-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WH_PASSWORD | Yes | WebHotelier API password/key | |
| WH_USERNAME | Yes | WebHotelier API username (HTTP Basic Auth) | |
| HOTEL_REGISTRY_PATH | No | Absolute path to a JSON file backing list_properties |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_propertiesA | List all known hotels with their WebHotelier property codes. Call this first whenever you don't know a property code. Local lookup — no API call. |
| get_property_infoA | Hotel profile and full room catalog (room types, capacities, amenities) for one property. |
| get_availabilityA | Live availability and prices for a specific stay. Dates are YYYY-MM-DD. Provide checkout OR nights. This is the primary tool for 'is there a room and how much' questions. |
| get_ratesB | Rate plans with cancellation policies for a property, optionally filtered to one room type. |
| get_calendarB | Day-by-day availability over a date range (YYYY-MM-DD). Good for 'which days are free in August'. |
| get_best_rateB | Cheapest available rate (BAR) for a property, optionally for a specific date (YYYY-MM-DD). |
| get_offersB | Currently active special offers/packages for a property. |
| get_reservationsA | Search bookings, optionally by property and check-in date range (YYYY-MM-DD). NOTE: requires a WebHotelier account with reservations access; without it the tool returns a clear permission message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools target distinct data types: rates, property info, availability, calendar, best rate, offers, and reservations. get_availability and get_calendar overlap slightly, but descriptions clarify one is for a specific stay and the other for a date range. get_best_rate is a distinct query for the cheapest rate.
All tools use a verb_noun pattern, predominantly 'get_'. The single exception is 'list_properties', but this is still a clear verb and similar in style. The naming is predictable and consistent.
8 tools is well within the ideal range. Each tool serves a clear purpose in the hotel query domain without redundancy.
The toolset covers the core read-side operations: property lookups, rates, availability, calendar, best rate, offers, and reservations. It lacks write operations, but the server appears intentionally read-only. Minor gap: no tool to fetch a single reservation by ID, but search can accomplish this.