Yes, with caveats. ChatGPT connects to remote MCP servers over HTTP through Developer Mode connectors on paid plans, and Guesty's official MCP server (beta) has a hosted endpoint at https://mcp.guesty.com/v1. The catch: Guesty documents bearer-token authentication for that endpoint, while ChatGPT's connector setup is built around OAuth, and ChatGPT is not on Guesty's tested client list. The dependable path today is hosting the small read-only server from our guide.
What works today
According to OpenAI, ChatGPT's Developer Mode provides full MCP client support for connectors you add by URL. Guesty's documentation lists Cursor, Claude Desktop, and VS Code as its tested clients, and the official server is read-only during beta. Expect beta behavior, which is how Guesty itself labels the release.
The path that works regardless: build the read-only Guesty MCP server from our guide, confirm it works locally with Claude, then host it at an HTTPS URL and point ChatGPT's connector at that. One Guesty-specific rule for anything you host: the Open API allows a maximum of five new access tokens per 24 hours, so the server must cache its token, which the one in our guide does out of the box.
The hosted API route
If you would rather call an API than run and maintain a server, there is a hosted middle path: the RapidEye API exposes Guesty as a hosted connector, so the credential handling and token care above happen on our side and your assistant or script calls one consistent surface. The catalogue is machine-readable, which means an AI agent can discover it and hand you the next step on its own.