Apaleo's MCP runs your hotel. Plekify's MCP sells your rooms. Those are two different jobs, and Plekify MCP v1 is built for the second one: giving AI agents a clean, read-only way to see what a hotel actually has to sell, so the agent can point a guest toward a real booking instead of a guess.
V1 ships five tools. search_properties finds hotels that match a query. get_property returns details on one of them. check_availability checks open inventory for given dates. get_rates returns live pricing from Apaleo. get_checkout_link produces a link to the hotel's own Shopify checkout, the one behind Shop Pay, where the guest finishes the booking themselves.
Every call needs a Bearer key. No key, no data. This is deliberate: it's a read surface for verified integrations, not an open endpoint for anyone to scrape.
We're calling this read-only because that's exactly what it is. Nothing an agent reads through these five tools creates a booking, holds a room, or charges a card. The agent finds the room and the rate, then hands the guest to checkout. A human still clicks pay. That's not a limitation we're hiding — it's the whole design of v1. A distribution-side MCP for hotel direct booking should be honest about what it does and doesn't do yet, and this one is.
The full tool schemas, auth details, and example calls are worth a closer look if you're building against this.