Yes, on your terms and read-only. You create a Hostaway Public API key, run a small MCP server (or expose the API as a custom GPT Action), and ChatGPT only sees the data your tools choose to expose, such as listings and reservations. It cannot change anything unless you deliberately add write tools.
Your options today
ChatGPT added Model Context Protocol support in September 2025 and connects to remote MCP servers over HTTP, so the path is to host the Hostaway MCP server (or wire the Public API into a custom GPT). You decide which endpoints the server wraps, which is what keeps access scoped: if the server only exposes read tools, that's all ChatGPT can ever do.
Your credentials live in the server's environment, not in the chat, and a read-only server never sends a write request to Hostaway. That combination, your own key plus read-only tools, is what makes connecting safe.
The hosted API route
One more option if the manual export loop above gets old: the RapidEye API exposes Hostaway 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.