Skip to main content

Connecting Besty to Claude, ChatGPT and other AI apps (Besty MCP)

Besty MCP lets you ask about reservations, guest messages and revenue from Claude, ChatGPT, Cursor or Copilot. How to connect, and the four access rules that catch people out.

Written by Sam Dundas

What Besty MCP does

Besty MCP connects your Besty account to an AI app you already use. As Besty describes it: "Ask about reservations, guest messages, and revenue, or review your workflows and guidebooks, straight from Claude, ChatGPT, Cursor, and any other app that supports MCP (Model Context Protocol). Each connection gets exactly the access you approve."

MCP stands for Model Context Protocol, an open standard for letting an AI app work with an outside system. You do not need to understand the protocol to use this. You copy one URL from Besty into your AI app, sign in, and approve what it may see.

Where to find it

Go to Settings, then the Besty MCP tab. Your Besty server URL is shown there with a Copy button. That URL is what your AI app needs.

Settings, Besty MCP tab, showing the server URL and the per-client setup tabs

Set up your app below it has a tab per client, and choosing a tab swaps the instructions underneath:

  • Claude, web and desktop

  • ChatGPT, web and apps

  • Cursor, the IDE

  • Microsoft Copilot, via Copilot Studio

  • Other MCP clients, any app that supports the protocol

Connecting, in four steps

  1. Add Besty to your app. In the app's settings, add Besty as a custom connector and paste the Besty server URL.

  2. Sign in to Besty. A browser window opens on the Besty login page. Sign in with your normal credentials.

  3. Approve access. Choose exactly what to approve: read access, guest personal information, write access, and which listings are visible.

  4. Start asking. The app can now work with your Besty data, within the access you granted.

The four step connection flow shown beneath the client tabs

Four rules that catch people out

Most support questions about MCP come down to one of these four.

  • Approving a connection requires full account access. A teammate whose access is limited to certain listings, or who does not have full permissions, cannot approve a connection. An owner has to do it for them.

  • Write access cannot be combined with a listing-limited grant. If you want the app to make changes, it gets all listings. If you want it restricted to certain listings, it is read only. There is no middle option.

  • Connections expire after 30 days. This is deliberate. When a connection lapses, the app has to ask for access again rather than keeping it indefinitely.

  • Guest personal information is a separate opt-in. It is its own choice on the approval screen, not something included by default with read access.

What an app can change, and how to undo it

An app can request write access, which covers editing guest messaging and journeys, guidebook pages, knowledge base notes, rental agreements, and your notification preferences.

Every change an app makes is recorded and can be undone. That record is the reason write access is worth granting at all: you are not taking it on trust.

Notes for Claude specifically

Besty MCP is available on all Claude plans. The Free plan is limited to one custom connector.

On Team and Enterprise plans the connector is added once by an owner under Organization settings, and individual members then click Connect rather than each adding the URL themselves.

Still Having Trouble?

If a connection will not complete or an app cannot see data you expect, check first whether you have full account access and whether the grant was listing-limited. If that does not explain it, reach out via chat or at support@getbesty.ai.

Did this answer your question?