Apaleo is the PMS Plekify runs on. Seeing them launch an MCP server and an Agent Hub is a signal worth naming plainly: a major hotel PMS vendor has decided agents belong in how hotels operate. We take that as validation, not competition.
Look at what they built. Apaleo's MCP exposes roughly 230 read/write operations, secured with per-hotel OAuth2 that carries the same authority as a PMS master key. An agent authenticated that way can cancel a booking. It can move money. That makes sense — it is built for a hotelier's own operations agents, working inside their property.
Plekify's MCP is a different shape entirely. Five tools, all read-only: search_properties, get_property, check_availability, get_rates, get_checkout_link. Authentication is a scoped Bearer key with no write path at all. Nothing in our surface can book, hold, or charge anything. It exists so a public shopping or travel agent can look up a hotel's real rates and hand a real human off to checkout — nothing more, nothing less.
That difference is the point, not a criticism. Apaleo's Agent Hub is designed to push more rates and availability into Apaleo. Every rate that lands there is a rate Plekify can mirror out to the agents shopping on a hotel's behalf. We build on the same PMS. There is no fight over the operations surface, because we were never on it.
If agents are going to shop for hotel rooms the way they already shop for flights and gear, someone has to expose the read side safely. See it in motion at the Plekify demo store.