Hostaway MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOSTAWAY_API_TOKEN | Yes | The Hostaway API token used for authentication. |
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_unread_guest_threadsB | List recent guest threads with raw unread metadata and derived attention signals. |
| get_conversation_contextC | Return an agent-friendly conversation summary plus recent message history. |
| get_reservation_briefC | Return the minimum useful reservation context for an agent or operator. |
| get_listing_briefC | Return the minimum useful listing context tied to conversations or reservations. |
| search_reservationsC | Lookup reservations by guest name, date range, listing, or reservation id. |
| search_conversationsC | Lookup conversations by guest name, listing, reservation id, or conversation id. |
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 6 tools
Tools are generally well-differentiated by verb (get/search/list) and resource type. While conversation, listing, and reservation domains overlap in hospitality workflows, the tools specify distinct operations (retrieval by ID vs. filtered lists vs. search) that minimize selection errors.
All tools follow a consistent snake_case verb_noun pattern with appropriate verbs (get, list, search). Minor deviation exists in noun choice: two tools use 'brief' while one uses 'context' for similar summary-retrieval purposes, slightly muddling the semantic pattern.
Six tools represent a focused, appropriate scope for guest communication and reservation lookup functionality. The count sits in the ideal range for a specialized retrieval server, avoiding bloat while covering essential read operations.
The surface provides comprehensive read access to conversations, listings, and reservations but lacks write operations such as sending messages, creating reservations, or updating listing status. This read-only limitation creates notable gaps for agents attempting to actively resolve guest issues or modify bookings.