> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vidimo.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Claude or ChatGPT
> Let your own AI app read your property data, so you can ask about reservations, occupancy, or compliance from the chat you already use.
If you already use Claude or ChatGPT, you can connect it to Vidimo and ask
about your properties there: occupancy for last month, who checks in tomorrow,
whether a guest's registration went through. The connection uses your Vidimo
account, respects your role's permissions, and is strictly read-only.
This is separate from the built-in [AI assistant](/messaging/ai-assistant),
which needs no setup. Connect your own AI app when you prefer working in
Claude or ChatGPT, or want to combine your property data with things
Vidimo doesn't do, like web search.
## Connect from Claude
In Claude's settings, open **Connectors**, choose to add a custom
connector, and enter this address:
```
https://mcp.vidimo.app/mcp
```
Claude opens a Vidimo sign-in page in your browser. Sign in with your
usual Vidimo account.
On the **Allow access to your Vidimo data?** screen, review what the
connection can read, then tap **Allow access**. Choose **Deny** if you
change your mind, and the connection is not made.
Back in Claude, the Vidimo tools are available in that conversation.
Try **"What's our occupancy for this month?"**
ChatGPT can use the same address and sign-in flow; adding custom connectors
there currently requires developer mode on a paid plan, in the web app.
## What your AI app can read
The connection offers the same lookups as the built-in assistant: reservations,
guests, availability, cleaning and maintenance tasks, your property and rooms,
team members, occupancy statistics, tourist tax amounts, reservation balances,
and guest registration status.
Reservation lookups name everyone staying in a room, not only whoever made the
booking, and carry each guest's nationality once their ID has been scanned at
check-in registration. Guests who have not registered have no nationality on
file, so an answer about nationalities covers your registered guests, not every
booking. Like everything else the connection reads, these guest details leave
Vidimo for your AI app.
Long lists come back in batches. A broad question like "list all our
reservations" answers with the most recent ones and says the rest were left
out, rather than returning nothing at all. Add a date range, a status, or a
room to see the part you mean.
It sees exactly what your role can see in the app, nothing more. An operator's
connection, for example, only sees their own tasks, no guest names or
nationalities, and cannot read tourist tax or payment figures.
The connection is read-only. Your AI app cannot create, change, or send
anything in Vidimo, and it cannot file registrations or take payments.
## Working with several properties
If your account manages more than one property, mention which property you're
asking about. The AI app can list your properties by name when it needs to ask
you which one you mean.
## If something looks off
* **Sign in required** on the consent screen means your Vidimo session
ended mid-connection. Sign in, then restart the connection from your AI app.
* **Connection request expired** means the request is stale. Close the tab and
reconnect from your AI app.
* To stop using a connection, remove the connector in your AI app's settings.
## Where to go next
The built-in assistant answers the same questions inside Vidimo, with
no setup.
What each role can see determines what a connected AI app can read.