guesty-mcp-server
Related Servers
Alternatives to guesty-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceMCP server for the Rizerve direct booking platform. Enables managing properties, bookings, availability, iCal sync, analytics, and webhooks through AI assistants.191-

Hostkit MCPofficial
AlicenseBqualityBmaintenanceMCP server for the Hostkit API, enabling management of properties, reservations, guests, invoices, and other property operations.36MIT- 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
- AlicenseBqualityBmaintenanceA read-only hospitality-focused MCP server that enables users to retrieve reservation details, listing briefs, and guest conversation contexts from Hostaway. It simplifies hospitality workflows by providing specialized tools for searching threads and viewing reservation data through natural language interfaces.652 npmMIT

Rentalot MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceMCP server for the Rentalot API. Manage rental properties, contacts, showings, conversations, and more from any AI assistant.204 npm1MIT- AlicenseAqualityDmaintenanceMCP server for CourtReserve racquet-sports club management, enabling AI clients to manage members, reservations, events, and transactions via natural language.291MIT
TDQS
Scored across 43 tools
Multiple tools overlap significantly, such as get_reservations vs search_reservations, get_financials vs get_reservation_financials vs get_revenue_summary, and get_calendar vs get_calendar_blocks. This creates ambiguity about which tool to use for similar tasks.
Most tool names follow a get_/create_/update_/delete_ verb-noun pattern, but there are inconsistencies like search_reservations versus get_reservations, and respond_to_review/submit_checkout_photos breaking the standard CRUD style. The naming is mostly predictable but not fully uniform.
43 tools is excessive for the apparent scope, especially with many redundant or near-duplicate tools (e.g., get_financials, get_reservation_financials, get_revenue_summary, get_owner_statements). A leaner set with clearer separation would be more appropriate.
The tool set covers a wide range of property management operations—reservations, listings, pricing, calendar, guests, reviews, messaging, financials, webhooks, tasks, and maintenance. However, it lacks obvious CRUD operations for several core entities (e.g., no update_guest, no delete_reservation, no create_listing), leaving notable gaps.