LabscoMCP early access ↗
MCP SERVER

Guesty Write-Capable MCP Server

Run a short-let portfolio from the chat window — reservations, calendars, pricing, guest messages, tasks and reviews — across a Guesty account.

by DLJRealty ↗Real Estate & PropertyCommunity

LABSCO SUMMARY

Writes and guest messages are open — decide what an agent may change before you connect.

Version 0.11.3 opened everything: reservation, listing, calendar and pricing writes, guest messaging and the property-health tools all run with no license key. That makes this a management surface, not only a reporting one — an agent can change prices and message guests, so settle which of those you want it doing first. Two notes from the author are worth carrying: Guesty's reservations endpoint returns only future data, so historical questions go through the calendar instead, and the server runs in production on the author's own rental portfolio.

What it is

A client for a Guesty property-management account, with write and guest-messaging tools alongside the reads as of version 0.11.3.

What you get

  • 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).
  • Changes as well as reads: create and update reservations and add notes to them; update listings, calendars, photos and pricing; record expenses, create tasks, respond to reviews, and register or remove webhooks.
  • Guest messaging — read a conversation's history and send the guest a message (get_conversations, send_guest_message).
  • Property health: a turnover-readiness score, a per-property health snapshot, checkout-photo uploads and open maintenance alerts, fed by an optional IoT webhook receiver — with nothing reporting they return empty device data, not errors.
  • The server's own licensing state, reported without making any Guesty API call (get_license_info).

Requirements

A Guesty account with API access, on the Professional plan or higher, 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: GUESTY_MCP_LICENSE_KEY is optional and changes nothing.

Setup effort

One command plus credentials — npx guesty-mcp-server, then supply credentials