Seven tools is the whole thing, which makes it cheap to load and easy for a model to use correctly. The part to think about is that creating a booking and changing a booking status are guest-facing actions with money attached — worth deciding deliberately whether an assistant should hold that key, or only the read half of the workflow.
An MCP server for the Lodgify vacation rental API, covering the three things a property manager actually asks about: what properties exist, what is booked, and what the calendar looks like. It writes as well as reads — bookings can be created and their status updated.
- Property listings and one property by id — `get_properties`, `get_property_by_id`
- Bookings in bulk or singly — `get_bookings`, `get_booking_by_id`
- Booking writes: create a new booking, and move an existing one to a different status — `create_booking`, `update_booking_status`
- Calendar data for availability — `get_calendar`
A Lodgify API key, exported as `LODGIFY_API_KEY` or set in the `env` block of your client config. The published launch is `uvx lodgify-mcp-server`, so uv needs to be installed — if your client reports `spawn uvx ENOENT`, that is uv missing from PATH. To run from source instead: clone, `uv sync`, and start `entrypoint.py` with `uv run python`.
One command plus a key — uvx lodgify-mcp-server, then supply credentials