TIDY ships a live first-party MCP server at api.tidy.com/mcp, and it is write-capable. That puts TIDY ahead of most turnover platforms on agent access, so for TIDY-only work you should use theirs rather than routing through anything else. The gateway matters here only when a task spans TIDY plus another system, which is the common case for turnover tooling since cleaning state usually has to be read alongside reservations living in a PMS.
Their MCP is live, and it writes
TIDY operates a first-party MCP server at api.tidy.com/mcp. We verified it directly by JSON-RPC probe rather than taking a changelog at face value, and it is both live and write-capable.
Write capability is the part to be deliberate about. An agent connected with write access can change real jobs and schedules, which affects real cleaners showing up at real properties. Read-only exploration is a good default until you trust the workflow.
Where a gateway still helps: turnover questions rarely stop at the turnover platform. Knowing which cleans are scheduled is only half of "which units are at risk tonight"; the other half is checkouts and arrivals living in a PMS. Neither API can see the other, and joining them is what one key and one schema buys you.
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 TIDY 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 TIDY
Because TIDY 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/tidy/tasks \
# 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
What agent access does TIDY already provide?
Yes. TIDY runs a live first-party MCP server at api.tidy.com/mcp, verified by direct JSON-RPC probe, and it is write-capable. That puts TIDY ahead of most turnover and cleaning platforms, which ship no agent interface at all.
What data does TIDY hold that a PMS does not?
The cleaning layer: jobs, schedules, who accepted work, and completion state. A PMS tells you when a guest checks out; TIDY tells you whether the turnover is actually covered. Most useful operational questions need both halves, which is why these two systems are usually read together.
Why route TIDY through the RapidEye API instead of using their MCP?
The RapidEye API earns its place the hop when a task spans TIDY plus a PMS, because no single platform API can answer a question crossing two systems, and when a built tool needs a connection that outlives the agent session that configured it.
Sources
- TIDY Developer Documentation, TIDYhttps://developers.tidy.com/