Ask ChatGPT or Claude about your hotel. OmniGuest stays the source.
Your team already uses AI apps. With the OmniGuest MCP server they connect ChatGPT, Claude or another MCP app to OmniGuest — and ask about today's arrivals, a reservation, a guest's past stays, open service requests or a guest chat. With your permissions, your hotel's rules and pseudonymised guest data.
Works with ChatGPT and Claude
Read-only, and off until your hotel admin switches it on.
Why hotels benefit
OmniGuest becomes the safe source for the AI your team already uses.
AI apps are only as good as what they know. The MCP server gives them your hotel's live data — under your rules, not around them.
A question instead of five screens
Arrivals, a reservation, the open requests of a department: the team asks in the AI app it already knows, and the answer comes from OmniGuest. No new tool to learn.
Answers from your data, not guesses
The AI reads what is actually in OmniGuest and in the guest record OPERA Cloud keeps true, instead of inventing an answer. Every look-up is in the audit log.
Know what is open right now
Which service requests are overdue, what a guest just wrote in the chat, who arrives tomorrow with which wishes — one question, without clicking through lists.
One question across your hotels
A connection can cover several hotels of a group. Every answer says which hotel it belongs to, with that hotel's own day and time zone.
No more copy and paste into chat windows
Without a sanctioned way, guest e-mails end up pasted into AI chats. With MCP the AI gets only what it is allowed, pseudonymised and on record — the hotel stays in control.
An open standard, your choice of AI
MCP is an open protocol. Your hotel is not tied to one AI provider — as more AI apps support it, they can connect the same way.
What your team asks
Plain questions, answers from your live data.
The AI app picks the right OmniGuest tool, OmniGuest answers from the same data your team sees in the app, and the AI turns it into a reply.
At the desk and on the floor
Which arrivals do we have today?
What does the Hartmann reservation say about the guests' wishes?
Which service requests are still open, and which are overdue?
What does our knowledge base say about late check-out?
In the manager's office
Who arrives on Saturday, and who of them has stayed with us before?
Show me the open guest chats that are still waiting for an answer.
Which housekeeping requests from yesterday are not done yet?
Which AI apps
The AI app your team already has.
MCP — the Model Context Protocol — is the open standard AI apps use to reach other systems. OmniGuest offers one address for every hotel and a sign-in made for it.
ChatGPT
As a custom connector in ChatGPT Business or Enterprise, or in Pro, with developer mode switched on — in a workspace by its admin. In Pro, connectors are read-only, which is all OmniGuest needs.
Claude
As a custom connector in claude.ai and Claude Desktop on any plan — Free allows one custom connector — and in Claude Code. In Team and Enterprise, an owner adds it for the organisation.
Other MCP apps
Apps that connect to remote MCP servers with OAuth, such as opencode — if your hotel allows that kind of app.
ChatGPT is a trademark of OpenAI, Claude a trademark of Anthropic; OmniGuest is not affiliated with either. Which plans and workspaces may add custom connectors is decided by each provider and changes often — we check your setup with you during onboarding.
Set up in three steps
Connected in a few minutes.
No installation and no IT project: one address for every hotel, and the sign-in your team already uses.
1
Your hotel admin switches it on
In OmniGuest under Settings → AI apps (MCP): allow AI apps for the hotel, choose which apps — ChatGPT, Claude, others — and which data they may read.
2
Add OmniGuest to your AI app
Add a custom connector with the OmniGuest address. ChatGPT: Business or Enterprise, or Pro, with developer mode switched on (in a workspace, by its admin). Claude: on any plan; in Team and Enterprise an owner adds it first.
3
Sign in and choose
Sign in with your OmniGuest login, passkey or two-factor included. Pick the hotels and data for this app, and whether guests appear pseudonymised. Done — ask your first question.
MCP server addresshttps://mcp.omniguest.ai/mcp
What the AI can read
Read-only, module by module.
In the first version the AI can only read. It cannot change a reservation, close a ticket or write to a guest.
Hotels
The hotels of the connection, with time zone and currency, so answers use the right day.
Arrivals, departures, in house
Today's or any day's movements, straight from the guest record OPERA Cloud keeps true.
Reservations
Search by name, confirmation number, dates or status, and the details of one stay.
Guests
Guest search and the profile with past stays and preferences.
Service requests
Open, overdue or by department — with the same visibility as in the app.
Guest conversations
Guest chats and their messages, read without marking anything as read.
Knowledge base
Your hotel's own documents and procedures, the same knowledge CompanyGPT uses.
Guest chat topics
Next release
What are your guests writing about?
Every guest conversation gets one of fourteen topics, assigned by OmniGuest's own self-hosted AI model — no external AI provider involved. Ask for a period and the AI app gets the number and share of conversations per topic, with short, neutral example sentences.
A topic is set when a conversation is closed, or after 24 hours without a new message
Up to 92 days per question
Example sentences never contain names, room numbers or contact details
With pseudonymised connections, topics with fewer than five conversations are merged into “Other”
Booking inquiry
Booking change
Check-in & check-out
Housekeeping
Maintenance & tech
Food & drinks
Spa & wellness
Transfer
Activities & excursions
Billing
Complaint
Lost & found
General info
Other
Statistics
Next release
Numbers for the morning meeting — without exporting a spreadsheet.
Counts, rankings and trends by day, week or month, in the hotel's time zone. The AI app only ever receives numbers, never the individual records behind them.
Guest chats
By period, channel, status, topic and language.
Service requests
Requests and the items asked for, by department, status and completion.
Reservations
On the books up to 365 days ahead: by status, room type, source, booking channel, market, length of stay, nationality and language — from the PMS data in OmniGuest (for polled connections, the synced window).
Counts only — never a single guest, room or booking
Groups of fewer than five guests are hidden, so no one can be singled out by subtraction
A daily query budget per user and hotel, and every query in the audit log
Staff statistics (“who completed the most requests”) only with their own permission and a hotel switch that is off by default — with a note to involve the works council
Built in
CompanyGPT uses the same tools — inside OmniGuest.
CompanyGPT, the assistant built into OmniGuest, works with the same tools, with no setup and the user's own permissions. It looks first and answers second:
No statement about your hotel without a result from OmniGuest
Replies in the language of the question
Times in the hotel's time zone
Follow-up questions that build on the previous answer
How a question travels
The AI gets the answer, not your database.
01
Your AI app
A colleague asks a question in ChatGPT, Claude or another connected AI app.
02
Signed-in connection
The app calls OmniGuest with a short-lived token for this one connection.
03
Three checks
Your permissions, your hotel's approval and the connection's choices — only what passes all three.
04
Only the answer
OmniGuest returns just what the question needs, guest data pseudonymised, and logs the call.
Security
Built for guest data from the first line.
An AI app outside your hotel reading guest data needs more than a password field. These are the rules the MCP server is built on.
Its own sign-in for every app
Each AI app connects through OAuth with its own connection. The app never sees the colleague's password.
Sign-in on OmniGuest's own page, with passkey or two-factor as usual
Short-lived access tokens; reusing an old refresh token ends the connection
Every connection can be revoked on its own — by the colleague or the hotel admin
You choose what the app gets
On the consent screen the colleague picks the hotels and modules for this app. It gets only those — even if the colleague may see more.
Hotels and modules chosen per connection, changeable later
Options you may not grant are shown greyed out, with the reason
Tools outside the connection are not even offered to the AI
Three locks on every call
What the AI may read is always the overlap of three things: the colleague's permissions, what the hotel allows for AI apps, and what this connection was given.
Checked again on every call, so a change takes effect at once
Same visibility rules as the app — a department sees its own tickets
A colleague who leaves or loses a permission loses it in the AI app too
The hotel decides
AI apps are off until a hotel admin switches them on. The hotel chooses which kinds of app are allowed and which modules they may use.
Master switch per hotel, off by default
Allowed apps — ChatGPT, Claude, other MCP apps — each on or off
A ceiling per module, and a list of every connection to the hotel
Guest data pseudonymised
Unless the hotel admin allows plain text, the AI sees guests as codes like G-7F3AQ2KM instead of names, and contact details are removed.
Names, e-mail, phone, address, birth date and documents removed — and no payment data
Known names, e-mail addresses and phone numbers replaced in free text
Plain text only where the hotel admin allows it, with a notice about the data processing agreement with the AI provider
Every call on record
Each question the AI asks OmniGuest lands in the audit log: who, which app, which tool, which hotel and how many results — never the content of the answer.
Names and e-mail addresses in search values are hashed in the log
Rate limits per connection and per hotel
Guest-written text is marked so the AI does not follow instructions hidden in it
Your data stays in OmniGuest
There is no export and no copy for the AI provider. The AI app receives only the answer to the question asked, and only for the hotels and modules of its connection. What the provider does with that answer is governed by your agreement with them — that is why sending guest names in plain text needs your hotel admin's explicit consent. Free text written by guests can contain details we cannot recognise; the settings page says so before you switch anything on.
Planned
Next: the AI prepares, a person confirms.
Specified for the next stage — not part of the first release.
Planned
Changes with human confirmation
The AI prepares a service request, a Lost & Found entry or a logbook note; anything a guest will see, and anything deleted, is confirmed by the colleague in OmniGuest first.
Planned
Lost & Found and the Duty Logbook
Ask whether an item was handed in, or what happened on the night shift — and record new entries.
Planned
More statistics
Lost & Found, e-mail and logbook figures join guest chats, service requests and reservations — with the same minimum group size.
The PMS stays read-only for AI apps: nothing is written to OPERA Cloud through MCP.
Questions
What hotels ask about MCP
What is MCP?
The Model Context Protocol is an open standard that lets AI apps such as ChatGPT and Claude use tools in other systems. OmniGuest provides those tools; your team's AI app calls them when a question needs hotel data.
How do we get started?
Your hotel admin switches AI apps on under Settings → AI apps (MCP). Then each colleague adds OmniGuest as a custom connector in ChatGPT or Claude with the address https://mcp.omniguest.ai/mcp, signs in with their OmniGuest login and chooses the hotels and data for that app.
Can the AI change anything in OmniGuest or the PMS?
No. The first version only reads. Changes with a human confirmation are planned for a later stage; the PMS stays read-only for AI apps either way.
Who decides which AI apps may connect?
Your hotel admin. AI apps are switched off until the admin turns them on, then the admin chooses the kinds of app and the modules. Each colleague connects their own app and can only pass on what they may see themselves.
Which AI apps can connect?
ChatGPT, Claude — claude.ai, Claude Desktop and Claude Code — and other apps that connect to remote MCP servers with OAuth, such as opencode. Each adds OmniGuest as a custom connector. In ChatGPT that needs Business or Enterprise, or Pro, with developer mode; in Claude any plan works, and in Team and Enterprise an owner adds it first. Plans change, so we check your setup with you during onboarding.
Does the AI provider see guest names?
Not by default: the AI sees guests as pseudonyms and no contact details. Plain text is possible only where your hotel admin allows it — your hotel then needs a data processing agreement with that AI provider, for example OpenAI or Anthropic.
Does an external AI read our guest chats to find the topics?
No. Topics are assigned by OmniGuest's own self-hosted model. The AI app only receives the counts per topic and short example sentences without names, room numbers or contact details.
Can managers see how individual staff perform?
Only if the hotel decides so: staff statistics need their own permission and a hotel switch that is off by default. We recommend involving the works council before switching it on.
Is this the same as CompanyGPT?
CompanyGPT, the assistant built into OmniGuest, uses the same tools. The MCP server opens them to the AI apps your team uses outside OmniGuest — with the same permissions and rules.
Want your team's AI to know your hotel?
Tell us which AI apps your team uses. In the demo we connect ChatGPT or Claude to the demo hotel and ask it live.