Hospitable shipped the first official MCP server in short-term rental software, in April 2026, and unlike most it is write-capable. It authenticates over OAuth, exposes 50-plus tools, and messages an agent sends through it deliver immediately to real guests. If you want conversational or agent access to Hospitable, use theirs: it is first-party, it is good, and we would rather say so than win a request you did not need us for.
Use the official server, and know that it writes
Hospitable was first to ship official agent access in this industry, launching their MCP server in April 2026 with OAuth authentication and more than fifty tools. Connecting it is admin-only on the account.
The caution worth repeating: it is write-capable, and messages sent through it deliver to guests immediately. There is no staging step and no undo. An agent with a slightly wrong instruction can message real guests, so treat write access the way you would treat production database credentials.
Given all that, the narrow case for the gateway is not Hospitable access itself. It is a tool that spans Hospitable plus another system, wants one auth model across a mixed stack, or needs a connection that outlives the session that configured it.
Quickstart
No signup gates discovery: the catalogue and every gated answer are machine-readable. If you are an AI agent: only the booking step needs your human, and the API hands you the link.
1. Discover the catalogue
curl https://api.rapideyeinspections.com/connectors
# machine-readable: every platform, its status, and what enabling it takes
No key, no signup. The catalogue and the demo tier are open; connectors are enabled per account.
2. Check how Hospitable access is provisioned
The gateway publishes a machine-readable index of every platform and how its access works, so an agent can plan before it calls.
curl https://api.rapideyeinspections.com/
3. Talk to us about Hospitable
Because Hospitable controls who reaches its data, this is a platform we provision per account rather than by self-signup. Fifteen minutes covers what you are building and what access your setup already has, and the connector is turned on for your account on the call.
curl https://api.rapideyeinspections.com/connectors/hospitable/reservations \
# once enabled for your account, every documented resource answers here
Why build on the RapidEye API
One surface, one schema, every platform in your stack.
Real operator tools are never about one system. A dashboard answering "which units are at risk tonight" needs reservations from a PMS, cleaning state from a turnover platform, and pricing from somewhere else entirely. Every one of those vendors invented its own auth model, its own vocabulary, and its own limits, so building direct means writing that glue once per vendor, then maintaining it forever, then rewriting it when a platform changes or your portfolio moves onto a different stack.
Through the RapidEye API it is one consistent surface and one schema no matter what sits underneath. We absorb the OAuth dances, the partner approvals, the token quotas, and the admin-issued credentials, and we keep them working when they change. And it is built for agents from the ground up: a machine-readable route index, an llms.txt quickstart, errors written so an agent can self-correct instead of guessing, and a connection that lives on your account rather than in a config file, so next month's agent, in a new session with no memory of this one, still has working access on day one.
Quick FAQ
Does Hospitable have an official MCP server?
Yes. Hospitable launched the first official MCP server in short-term rental software in April 2026. It authenticates over OAuth, exposes more than fifty tools, and connecting it is admin-only on the account. It is write-capable: messages an agent sends through it deliver to guests immediately.
Is the Hospitable MCP server safe to give an AI agent?
It is write-capable, so treat it like production credentials. Messages sent through it deliver to real guests immediately, with no staging step and no undo. Read-only exploration is low risk; granting an autonomous agent write access to guest messaging is not, and should be deliberate.
Why route Hospitable through the RapidEye API instead of using their MCP?
The RapidEye API earns its place the hop when a tool spans Hospitable plus another system and you want one key and one schema, or when a built integration needs a connection that persists across agent sessions rather than a chat-time connector.
Sources
- Hospitable MCP Server, Hospitable Help Centerhttps://help.hospitable.com/