> 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/about-guestway-mcp.md).

# About Guestway MCP

This page explains why Guestway MCP lets an AI assistant read your data safely, and what it means for guest data and cost.

## What an MCP connection is

**MCP** (Model Context Protocol) is an open standard that lets AI assistants connect safely to other software. It works like a universal plug: an assistant that supports MCP connects to Guestway without any custom setup. You sign in with your Guestway account, so there are no API keys to manage.

The assistant looks things up while you chat, with your own account and your own permissions. It sees what you are allowed to see in Guestway, and no more.

## Guest data and privacy

Guest names, email addresses, phone numbers and addresses are personal data. That is why they stay hidden unless you allow them when you connect. With **Do not allow**, they are removed before anything reaches the assistant.

Whatever the assistant does receive is handled under the privacy terms of your AI provider. Check the policy of your organization before you allow personal data. Because each assistant is a separate connection, you can allow personal data in one assistant and not in another.

## Cost

The connection needs a plan with your AI provider that supports custom connectors. That plan is the cost to check before you start.

## Related

* [Guestway MCP](https://docs.guestway.io/ai/guestway-mcp.md)
* [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)


---

# 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/about-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.
