Yes, on your terms. ChatGPT reaches Guesty through an MCP server, and during beta Guesty's official server is read-only by design: assistants can look up and summarize your data but cannot create, update, or delete records. Access runs on OAuth credentials from an application you create; delete that application and no new tokens can be minted, with any existing token aging out within 24 hours.
Your options today
ChatGPT added Model Context Protocol support in September 2025 and connects to remote MCP servers over HTTP, which matches Guesty's hosted endpoint at https://mcp.guesty.com/v1. The credentials come from Integrations, then OAuth applications in your Guesty dashboard, so nothing gets pasted into the chat itself, and the token is scoped to the application you created.
Want it even tighter? Build the small server from our guide against the Guesty Open API and expose only the endpoints you choose. Whichever path you take, the read-only property holds: looking is all the assistant can do.
The hosted API route
One more option if the manual export loop above gets old: the RapidEye API exposes Guesty as a hosted connector, so a custom tool or agent reads the data through one consistent surface instead of you ferrying CSVs. The catalogue is machine-readable, so an agent can discover it without help.