Read-only MCP server for short-term rental owners in Poland. Query reservations, availability, pricing, guest reviews, and monthly stats via 10 tools. OAuth 2.1 with PKCE or static Bearer token.
Scored across 10 tools
Tools target distinct resources and actions, with clear separation between availability, reservations, blocks, pricing, stats, reviews, messages, apartments, and account. Only minor overlap exists between get_availability (which includes blocked dates) and list_blocks, but descriptions clarify their different scopes.
Names follow a consistent snake_case verb_noun pattern (get_*, list_*) throughout, with only whoami deviating as a single-word convention. The pattern is predictable and readable.
10 tools is well within the ideal range and covers the core read operations for property management without redundancy. Each tool appears to earn its place.
The surface is entirely read-only; no tools exist to create, update, or delete reservations, blocks, pricing, or to send messages or approve reviews. While the read side is fairly complete, the absence of any mutation operations is a notable gap for an ERP system.
Occupied check-in/check-out date ranges, no guest data: direct reservations plus nights imported from external iCal calendars (Booking.com, Airbnb; status "external", source = feed name) and owner-blocked dates (status "blocked"). Defaults to today through +365 days; the range cannot exceed 366 days.
Inputs: to, from, apartment_id. Returns: data, help_url
Seasonal price overrides, minimum-stay rules and extra fees — the pricing configuration, not a computed quote. The base nightly rate lives on the apartment record (see list_apartments), not here.
Inputs: apartment_id. Returns: data, help_url
Get a single reservation by id.
Inputs: id (required). Returns: data, help_url
Monthly occupancy and revenue for one apartment, confirmed reservations only — the same numbers as the panel's Statystyki page. apartment_id is required: occupancy/revenue from apartments with different nightly rates can't be meaningfully summed.
Inputs: apartment_id (required), months. Returns: data, help_url
List the account's apartments and their ids. Call this before any tool that takes apartment_id — get_stats requires it, the rest treat it as an optional filter.
Inputs: no named parameters. Returns: data, help_url
Owner-created blocked date ranges (maintenance, personal use). Not reservations — no guest, no price.
Inputs: apartment_id. Returns: data, help_url
Message history for one reservation — everything sent to the guest, automatic mail included. The same thread the panel shows.
Inputs: reservation_id (required). Returns: data, help_url
List reservations across the account's apartments, newest first, cursor-paginated. from/to filter by stay date (check-out after from, check-in before to), not by when the reservation was created.
Inputs: to, from, after, limit, +2 more. Returns: data, help_url
Guest reviews, including unapproved ones by default (same as the panel). Pass approved_only to match what is actually published on the booking page.
Inputs: apartment_id, approved_only. Returns: data, help_url
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.
