Hospitable's API and MCP can now read your availability rules and your pricing

Hospitable has opened two more parts of its platform to its public API and its MCP server. If you build on Hospitable, or point an AI assistant at it, this is the practical item from the 16 October release.

Availability settings

You can now read a property's availability settings through both the public API and MCP. That covers the booking controls that decide what a guest can actually reserve: check-in and checkout restrictions, preparation time between stays, advance notice, and the availability window.

It also covers booking rules. Instant book and request to book settings come through, along with minimum and maximum stay limits, including day by day variations where you have set them.

Pricing settings

Pricing is the second addition. Through the API and MCP you can now read currency, nightly and weekend rates, cleaning fees, extra guest fees, pet fees, resort fees, security deposit, guest limits and maximum occupancy.

That is close to the full commercial picture of a listing, in a form something else can consume.

What this is good for

The obvious use is reconciliation. If you run a revenue tool, a reporting stack or a spreadsheet that holds its own copy of your rates and rules, you have until now had to maintain that copy by hand, or scrape it, and discover the drift when a booking came in at a price you did not expect. Reading the real values straight out of Hospitable removes that class of problem.

The second use is checking yourself. Minimum stay rules, advance notice and preparation time accumulate over years and across properties, often set once for a reason nobody remembers. Being able to pull all of it into one table makes it possible to audit, which is awkward to do property by property in any interface.

For MCP specifically, this is what makes a question like "which of my properties still has a three night minimum in November" answerable. Hospitable put its MCP server into the ChatGPT app directory earlier in October, and read coverage like this is what decides whether that connection is useful or a demo.

The limit worth noting

This is read access. Nothing in the release says you can write availability or pricing settings back through the API or MCP, and the wording throughout is about retrieving data to keep your own tools aligned with what you set in Hospitable.

So the direction of travel stays one way. Hospitable remains the place you change a rate or a stay rule, and everything downstream can now see the result accurately. For most reporting and reconciliation work that is enough. If you were hoping to drive pricing into Hospitable from your own system, this is not that.

Hospitable has been building this surface steadily. Owner statements came to the API and MCP at the start of the month, including marking them paid, and its MCP server picked up smart lock control in late September. Availability and pricing are the two that most integrations were waiting on.

No plan tier or regional restriction is mentioned.