Twenty-three tools are live and every one of them reads; the fourteen write and guest-messaging operations, plus the conversation history tool (gated because it returns message content) and the IoT property-health add-on, are behind tiers with no release date. That makes this a reporting and lookup surface rather than a management one for now. Two implementation notes from the author are worth carrying: Guesty's reservations endpoint returns only future data, so historical questions go through the calendar instead, and it was built against ten of the author's own rentals rather than in the abstract.
A client for a Guesty property-management account. 43 tools are registered, but only the 23 read-only ones are live today; the write and guest-messaging operations sit behind paid tiers the author says are not yet available.
- Reservations found the way you actually look for them — filtered by dates, listing, status or guest, or searched by guest name, email or confirmation code — with the financial breakdown for any one of them (get_reservations, search_reservations, get_reservation_financials).
- Guests looked up by name or email, and the full profile behind a booking (get_guests, get_guest_by_id).
- Listings and their calendars: property details or the whole portfolio, availability and pricing by date, blocked dates with their reasons, and occupancy calculated over a range (get_listing, get_calendar, get_calendar_blocks, get_listing_occupancy).
- The money view: revenue, payouts and commission; the base price, discounts and fee detail on a listing; owner statements; recorded expenses; and revenue aggregated across every listing (get_financials, get_listing_pricing, get_owner_statements, get_expenses, get_revenue_summary).
- Operations: cleaning and maintenance tasks, guest reviews pulled from every channel, the booking channels connected per property, and the languages a listing supports (get_tasks, get_reviews, get_channels, get_supported_languages).
- Configuration reads: the automation and workflow rules in place, registered webhooks, custom fields, listing photos with their captions, and the account itself (get_automation_rules, get_webhooks, get_custom_fields, get_photos, get_account_info).
- The server's own licensing state, reported without making any Guesty API call (get_license_info).
A Guesty account and an API application with the open-api scope, created under Settings, API in the Guesty dashboard — the client ID and secret go in GUESTY_CLIENT_ID and GUESTY_CLIENT_SECRET. Run it with `npx guesty-mcp-server` over stdio. No license key is needed: the free read-only tier is what runs today, and a paid-tier key is recognised but refused with a message saying those tiers are not yet available, so setting it or omitting it makes no difference.
One command plus a key — npx guesty-mcp-server, then supply credentials