> For the complete documentation index, see [llms.txt](https://docs.guestway.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guestway.io/ai/guestway-mcp.md).

# Guestway MCP

Guestway MCP connects AI assistants such as Claude, ChatGPT and Cursor to your Guestway data, read-only by default.

{% hint style="info" %}
**Requirements**

* The Supervisor, Admin or Super admin role, the **MCP user** role, or a custom role with the **MCP Guestway** feature. The Operator, Super operator, Viewer and Cleaner roles alone cannot connect.
* A personal Guestway account. Managed accounts cannot connect.
* An AI assistant on a plan that supports custom connectors.
  {% endhint %}

## The Guestway MCP page

The page is **Settings** → **Guestway MCP**. It has four tabs: **About**, **MCP Users**, **Active sessions** and **Audit log**. You see only the tabs that your role gives access to.

### About

| Field                      | What it does                                                                                                                                                                     | Limits                                                                                  |
| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| **Server URL**             | The address of the connection: `https://mcp.guestway.io/mcp`. **Copy** copies it.                                                                                                | None                                                                                    |
| **Connect your assistant** | Shows the way to connect for each assistant: **Claude** (**Add to Claude**), **ChatGPT** (**Open ChatGPT**), **Cursor** (**Add to Cursor**) and **Other** (**Copy server URL**). | **Other** works with any assistant that supports remote MCP servers with OAuth sign-in. |
| **Try asking**             | Example questions. A click copies the question.                                                                                                                                  | None                                                                                    |
| **You stay in control**    | A summary of the access that you choose when you sign in.                                                                                                                        | None                                                                                    |

When your roles give no access to the MCP, the tab tells you that your role cannot connect yet, and to ask an Admin to update your role.

### MCP Users

The users whose role lets them use the MCP. Shows for Admins and Super admins, and for roles with access to the users of the organization.

| Column or button    | What it does                                                                                                                                                | Limits                                                                                                          |
| ------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **MCP access**      | **Read only**: the user can look things up. **Read & write**: the user can also change data, as far as their role allows.                                   | Only users with a personal account are listed.                                                                  |
| **Give MCP access** | Adds the built-in **MCP user** role to the roles of a user, as on the **Users** page. The other roles of the user stay. The user then has **Read & write**. | You need access to edit users and to give the **MCP user** role. Cleaners and managed accounts are not offered. |
| **View audit log**  | Opens the **Audit log** tab for that user.                                                                                                                  | Only with access to the audit log.                                                                              |

### Active sessions

The apps that users connected through the MCP and that can still use it. Shows for Admins and Super admins, and for roles with access to the users of the organization.

| Column or button   | What it does                                                                                                  | Limits                                                                                                                         |
| ------------------ | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **Name**           | The user who connected the app. The tooltip shows the email address.                                          | None                                                                                                                           |
| **App**            | The app that is connected, for example Claude or ChatGPT.                                                     | None                                                                                                                           |
| **Last active**    | When the app last used Guestway. The tooltip shows when the app was connected.                                | For an app that has not used a tool since Guestway records it, this is when the app last renewed its access, to about an hour. |
| **Allowed**        | What the user allowed when they signed in: **Changes**, **Personal data** and **Risky actions**.              | None                                                                                                                           |
| **View audit log** | Opens the **Audit log** tab for that user.                                                                    | Only with access to the audit log.                                                                                             |
| **Disconnect**     | Ends the session in every organization that it covers. The app loses access until the user connects it again. | You need access to edit users. An Admin cannot disconnect a session of a Super admin.                                          |

### Audit log

The changes that connected apps made in Guestway through the MCP, kept for 90 days. Shows for Admins and Super admins, and for roles with the **Audit log** feature.

* Each row shows what was done, what it was done to, the user, the app and the outcome.
* The outcome is **Succeeded**, **Denied** (a permission or the connection did not allow it, and nothing was changed) or **Rejected or failed**.
* Click a row for the details: **Outcome**, **Response** and **Changed fields**. The audit log keeps the names of the changed fields, not their values.
* You can filter on the outcome, the user or the action.
* Questions that only read data are not in the audit log.

## What the connection gives you

The assistant looks up your Guestway data while you chat with it, with your own account and your own permissions. By default, the connection is read-only: the assistant cannot change anything in Guestway.

| Area                                   | Examples of what you can ask                                                                                               |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Reservations & occupancy**           | “How many arrivals do we have next week per property?” · “Which listings had the most cancellations last quarter?”         |
| **Inbox & messaging**                  | “How many conversations are still waiting for a reply?” · “What are guests asking about most this month?”                  |
| **Auto-pilot & knowledge base**        | “How often did auto-pilot answer on its own last week?” · “Which knowledge-base suggestions are still waiting for review?” |
| **Housekeeping**                       | “How many clean tasks are planned for Saturday, per cleaning team?”                                                        |
| **Upsells, deposits & damage waivers** | “Which upsells sold best in August?” · “How many security deposits are still on hold?”                                     |
| **Reviews**                            | “What’s our average review score per listing this year?” · “Which reviews have no reply yet?”                              |
| **Access & smart devices**             | “Which smart locks reported a failed action this week?” · “How many access codes were created yesterday?”                  |
| **Setup & configuration**              | “Which automations apply to the Riverside building?” · “Which properties have no check-in journey?”                        |

## Changes

The assistant can change data in Guestway only when both are true:

* Your role allows changes through the MCP: **Admin**, **Super admin**, the **MCP user** role, or a custom role with **Edit** on the **MCP Guestway** feature.
* You ticked **Allow changes** when you signed in.

The assistant can then change only what your role lets you change in the app. A new Auto-Pilot configuration or a new automation that the assistant creates starts in testing mode.

Some actions are hard to undo or reach beyond Guestway, for example opening a door, refunding a guest or changing every conversation at once. The assistant can run them only when you also ticked **Allow risky actions**. Without it, Guestway refuses them.

With **Allow** under **Personal data**, the assistant can also read the guest portal link of each reservation. Anyone with this link can open the guest portal of that reservation, also after the connection ends.

## Access permissions

You choose the access when you sign in, for each assistant. Each assistant is a separate connection with its own choices.

| Choice                  | What it does                                                                                                                                                          | Limits                                                                                                          |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| **Holding**             | The company account the connection works in.                                                                                                                          | Required. One holding per connection.                                                                           |
| **Organizations**       | The organizations the assistant can read.                                                                                                                             | All organizations are ticked by default.                                                                        |
| **Personal data**       | **Do not allow** keeps guest names, email addresses, phone numbers and addresses hidden before anything reaches the assistant. **Allow** lets the assistant see them. | The default is **Do not allow**.                                                                                |
| **Allow changes**       | Lets the assistant change data in Guestway for you, as far as your role allows. Without it, the connection can only read.                                             | Not ticked by default. You cannot tick it when your role in the holding does not allow changes through the MCP. |
| **Allow risky actions** | Lets the assistant run actions that are hard to undo or reach beyond Guestway, such as opening a door or refunding a guest.                                           | Not ticked by default. A risky change also needs **Allow changes**.                                             |

A new sign-in replaces the earlier choices of that connection.

## Disconnecting

* A connection ends when you remove the Guestway connector in the settings of your AI assistant.
* An Admin or Super admin can end a connection with **Disconnect** on the **Active sessions** tab.
* Unused connections are cleaned up automatically.
* Removing someone from your organization in Guestway blocks their connection immediately.
* When the roles of a user no longer give access to the MCP, their connection stops working at once. It can still show on **Active sessions** until it expires or an Admin disconnects it.
* Guestway support at **<support@guestway.io>** can cut off a connection right away, for example after a lost laptop or when an employee leaves.

## Related

* [How to connect an AI assistant with Guestway MCP](https://docs.guestway.io/ai/guestway-mcp/how-to-connect-an-ai-assistant-with-guestway-mcp.md)
* [About Guestway MCP](https://docs.guestway.io/ai/guestway-mcp/about-guestway-mcp.md)
* [Analytics](https://docs.guestway.io/reviews-and-analytics/analytics.md): **Copy context for your AI assistant** copies the queries of a chart for your assistant.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guestway.io/ai/guestway-mcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
