OwnerRez MCP Server
Related Servers
Alternatives to OwnerRez MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude to read and act on your OwnerRez account—bookings, properties, guests, financials, and guest messaging—through a secured remote MCP endpoint.MIT
- AlicenseAqualityBmaintenanceConnects OwnerRez property management data to MCP clients, enabling natural-language queries about bookings, check-ins, guest messaging, expenses, and webhooks.18MIT
- AlicenseBqualityBmaintenanceMCP server that connects OwnerRez to Claude and other MCP clients, enabling natural language management of bookings, guest communication, property info, expenses, and webhooks.183MIT
- FlicenseNot gradedqualityDmaintenanceConnects Claude to the Hospitable API v2 for managing vacation rental properties, reservations, guest messages, and reviews.-
- AlicenseAqualityBmaintenanceProvides Claude and any MCP client with live access to property management data, enabling operations on properties, units, leases, tenants, work orders, vendors, accounting, and file attachments through natural language.25MIT
- AlicenseNot gradedqualityFmaintenanceConnects AI agents to RealtyCalendar accounts, allowing users to query bookings, availability, and check-ins via natural language, with local-first privacy and read-only access.MIT
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action: properties, bookings, guests, owners, statements, payments, deposits, refunds, inquiries, messages, availability, and rates. While some tools have similar list/get patterns, their resource names clearly differentiate them, and potential overlaps like get_schedule vs. get_availability are resolved by scope (all properties vs. one property).
All tools follow a consistent ownerrez_verb_noun pattern using snake_case: list for collections, get for single items, search for guests, send for messages, update for rates. No camelCase or irregular verbs are used, making the naming predictable and easy to navigate.
At 21 tools, the set is slightly heavier than the typical 3-15 well-scoped range but still reasonable for a property management domain covering many resource types. Each tool has a clear purpose, and the count is not excessive enough to feel bloated.
The server provides comprehensive read coverage (properties, bookings, guests, owners, statements, payments, deposits, refunds, inquiries) and a couple of write actions (send_message, update_rate). However, it lacks create, update, or delete operations for core entities like bookings, properties, and guests, which are notable gaps that could require workarounds.