Yes, officially. Guesty ships a first-party MCP server, in early beta as of July 2026, and Claude Desktop is one of its documented clients. Run it locally with npx -y @guestyorg/sdk mcp using OAuth credentials from your Guesty account and register it in Claude Desktop or Claude Code. Once connected, Claude can read your listings, reservations, calendar, and guests in plain English.
What works today
According to Guesty's Open API documentation, the official server is read-only during beta: assistants can look up and summarize data but cannot create, update, or delete Guesty records. Guesty also labels the beta experimental, so treat it as a preview rather than a production dependency. Credentials are self-serve if your plan includes Open API access: open Integrations, then OAuth applications, create a new application, and copy the client ID and secret. A hosted endpoint, https://mcp.guesty.com/v1, also exists for clients that can send a bearer token header.
If you want full control over the tool surface, the other path still works: a small MCP server you build yourself against the Guesty Open API, where you decide exactly which endpoints Claude can see. Our guide has the working Node.js code, including the token caching Guesty requires (its docs allow a maximum of five new access tokens per 24 hours).
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.