OwnerRez MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_bookingsA | List bookings. OwnerRez bounds this endpoint by |
| get_bookingB | Get full details for a single booking by its OwnerRez ID. |
| who_is_stayingA | Show who is currently staying in each property (in-house guests). Returns one row per active stay (arrival <= on_date < departure) with property, guest name, and dates. Defaults to today. Internally pulls active bookings changed in the last ~year and filters by stay date. |
| list_propertiesC | List properties (id, name, address, timezone). |
| list_ownersB | List property owners (id, name, contact). |
| find_guestC | Search or list guests. OwnerRez bounds this endpoint by |
| list_quotesA | List quotes, optionally filtered to comma-separated property IDs. |
| list_paymentsA | List guest payments, optionally for a single booking. |
| list_refundsB | List guest refunds, optionally for a single booking. |
| list_feesB | List booking fees, optionally for a single booking. |
| list_messagesA | List the messages in a conversation thread. |
| send_messageB | Send a message to a guest on an existing conversation thread. |
| list_webhook_subscriptionsB | List active webhook subscriptions on the account. |
| create_webhook_subscriptionA | Subscribe to OwnerRez events by registering an HTTPS callback URL. |
| delete_webhook_subscriptionA | Remove a webhook subscription by its ID. Blocked in read-only mode. |
| list_open_messagesA | List inbound guest messages captured by the webhook receiver that haven't been marked handled yet — your "open messages" inbox. Each entry includes its store id, thread_id (use with send_message), guest, body, and when it arrived. Requires the webhook receiver to be running and subscribed (see create_webhook_subscription with category "message"). |
| get_message_eventB | Get one stored message event (including its raw webhook payload) by id. |
| mark_message_handledA | Mark a stored message as handled (or reopen it), removing it from the open list. Local bookkeeping only — does not call OwnerRez. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| draft_checkin_message | Draft a warm check-in message for an arriving guest. |
| draft_guest_reply | Draft a reply to an incoming guest message. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| properties_resource | All properties in the account, as a browsable resource. |
| owners_resource | All property owners in the account, as a browsable resource. |
TDQS
Scored across 18 tools
Each tool targets a distinct resource/action: webhook subscription lifecycle, booking reads, current-stay snapshot, property/owner/guest lookups, financial lists, and message inbox/thread operations. The only potentially close pair is list_messages vs list_open_messages, but they are clearly separated by conversation thread vs webhook inbox.
Most tools follow a verb_noun snake_case pattern (list_bookings, get_booking, create_webhook_subscription, delete_webhook_subscription). Minor deviations like who_is_staying and mark_message_handled break the strict noun-object pattern, and find_guest is singular while list_* tools are plural.
18 tools is on the high side but each maps to a meaningful OwnerRez domain area (bookings, properties, guests, messages, payments, webhooks). It feels slightly broad rather than bloated, and no obvious redundancy inflates the count.
The set covers read-side lookup and the webhook-driven message inbox workflow well, including create/delete subscriptions and send/mark-handled. However, it lacks write/update operations for core entities such as bookings, quotes, payments, and guests, and there is no property/guest detail retrieval beyond lists, so full lifecycle tasks would dead-end.