One secure link between AI assistants and your hotel
MCP (Model Context Protocol) is an open standard for connecting AI assistants to software. Kamra ships an MCP server inside every install, on your own domain. Connect Claude or any MCP client, sign in with your Kamra user, and the assistant works as you: it sees what your role sees and does what your role may do.
Quick start
- Give Kamra a public HTTPS address. Claude connects from Anthropic's cloud. Any Kamra install behind a real domain works. For local tests, use Claude Code.
- Make sure you have MCP access. Admins always do. Everyone else needs MCP Read or MCP Manage from a hotel admin, see Permissions and roles.
- Press Connect Claude. In Kamra, open Kamra Agent, then Connect Claude. Claude opens its connector dialog with your hotel's name and URL filled in. Press Add, sign in, pick the property.
Connect a client
Labels in third-party apps change over time. What stays the same is the server URL, https://your-kamra/mcp, and the Kamra sign-in.
Claude (web and desktop)
- Use Kamra Agent, Connect Claude in Kamra, or open Claude's settings, Connectors, Add custom connector.
- Name it after your hotel and paste
https://your-kamra/mcp. Leave Client ID and Secret empty. - Press Connect, sign in to Kamra and choose the property.
- Optional: in the connector's tool permissions, set write tools to need approval. Kamra marks every tool as read-only or not, so this is one click per group.
Claude Code
claude mcp add --transport http kamra https://your-kamra/mcp
Run /mcp in Claude Code and sign in. Claude Code signs in through localhost, so it also works with a Kamra running on your own machine.
ChatGPT
Add Kamra as a custom connector (ChatGPT may call it a plugin or app). Use https://your-kamra/mcp as the server URL with OAuth, then approve the sign-in. Select Kamra from the tools menu inside a chat.
n8n, scripts and unattended agents
For a self-hosted n8n, ask your admin to add its OAuth callback to Kamra's allowed redirects, then use n8n's MCP Client node with OAuth. ChatGPT's callbacks are allowed out of the box. For headless jobs, create an API key for a dedicated Kamra user and send it on every request:
Authorization: token <api_key>:<api_secret>
The agent acts as that user, with that user's roles and MCP access.
Authentication
- OAuth 2.1 with PKCE (S256) and dynamic client registration. This is what Claude, Claude Code and ChatGPT use.
- Short-lived tokens. Access tokens last one hour; refresh tokens rotate and last 30 days. Tokens are stored hashed.
- Bound to a person and a property. Each sign-in is tied to one Kamra user and the property they chose.
- API keys for unattended agents, using Kamra's standard
token key:secretheader. - Revocation. Staff can disconnect themselves in Kamra Agent; admins can revoke any connection from the AI access page.
Permissions and roles
You decide who can use MCP, and what they can do. Two roles control access, assigned per person next to the roles your team already has. A person reaches only the properties they can already open in Kamra.
| Role | What it allows |
|---|---|
| MCP Read | Look things up through an AI assistant: arrivals, reservations, folios, reports, housekeeping. No changes. |
| MCP Manage | Everything in MCP Read, plus making changes: bookings, check-ins, charges, room moves, night audit. |
- Roles work together. An MCP role only opens the door. What a person can see and change is still limited by their normal Kamra roles and the modules turned on for the property. Nobody can do more through Claude than they can in Kamra.
- No role, no access. Without MCP Read or MCP Manage a user cannot use MCP at all. Hotel admins and system managers always can.
- Instant. Roles and property switches are checked on every request, so a change applies straight away, without reconnecting.
- Property switches. On Settings, AI access (MCP), an admin can turn MCP off for a property, block all write tools, or block single tools.
- See who is connected. The same page lists every active connection with its user, property and client, with a Revoke button.
Endpoints
| MCP (Streamable HTTP) | /mcp |
| Protected resource metadata | /mcp/.well-known/oauth-protected-resource |
| Authorization server metadata | /mcp/oauth/.well-known/oauth-authorization-server |
| Authorize, token, register | /mcp/oauth/authorize, /mcp/oauth/token, /mcp/oauth/register |
An unauthenticated call to /mcp returns 401 with a pointer to the metadata, so clients start the sign-in on their own.
Tool capabilities
Tools wrap Kamra's own APIs, so business rules, pricing and taxes stay in the PMS. Each tool carries MCP annotations that say whether it changes data. The full list with JSON schemas is available from tools/list or the documentation.
| Area | Tools | Covers |
|---|---|---|
| Front desk | 34 (21 read, 13 write) | Today board, availability, quotes, bookings, waitlist, check-in and out, room moves, bulk room assignment |
| Banquets | 21 (10 read, 11 write) | Enquiries, menus, quotes, event orders, payment terms, pipeline |
| Restaurant POS | 18 (8 read, 10 write) | Outlets, menus, tables, orders, KOTs, kitchen queue, room charges |
| Billing | 16 (4 read, 12 write) | Folios, charges, payments, voids, allowances, payment links, deposits, company credit |
| Housekeeping | 6 (1 read, 5 write) | Task queue, assignment, room status, minibar and consumables |
| Laundry | 5 (2 read, 3 write) | Board, rates, collection, status, delivery |
| Groups | 4 (2 read, 2 write) | Blocks, pickup, group billing |
| Night audit | 4 (1 read, 3 write) | Precheck, End of Day, audit pack, business date recovery |
| Operations | 3 (1 read, 2 write) | Service tickets |
| Briefings | 2 (2 read, 0 write) | Owner and position briefings |
| Onboarding | 2 (0 read, 2 write) | Property setup, booking import |
| Revenue | 1 (0 read, 1 write) | Room rates |
Safe usage
For hotel teams
- Try new workflows on a test property first.
- Start people on MCP Read; move to MCP Manage when they are ready.
- Set write tools to need approval in Claude.
- Keep refunds, rate changes and cancellations human-approved.
For technical teams
- Give each agent its own Kamra user and the smallest role it needs.
- Use idempotency keys on bookings so retries never double-book.
- Treat tool output as untrusted input before you prompt with it again.
- Read the activity log; every MCP call is recorded there.
Guest data
Kamra keeps guest data on your server. When staff use an AI assistant, treat its provider as a data processor: use a plan with a Data Processing Agreement (with Claude, the Team, Enterprise and API plans include one through Anthropic's commercial terms), enable only the tools people need, and share only the data a task requires. Under GDPR or India's DPDP Act, consider an impact assessment and document your setup.
General guidance, not legal advice. Check your provider's current terms.
FAQ
What is the Kamra MCP server URL?
Your own Kamra address followed by /mcp, for example https://pms.yourhotel.com/mcp. Every Kamra install has its own MCP server; there is no shared Kamra cloud endpoint.
Why does Claude say I have no MCP access?
Your Kamra user needs the MCP Read or MCP Manage role for that property. Ask your hotel admin to grant it in Settings, AI access (MCP). It works on your next request, with no need to reconnect.
Why can Claude read but not change anything?
You have MCP Read, the property has write tools blocked, or your normal Kamra role does not allow that action. Writes need MCP Manage and a role that can do the same thing in Kamra.
Claude cannot reach my hotel. Why?
Claude connects from Anthropic's cloud, so your Kamra site needs a public HTTPS address. On a laptop or a local install, use Claude Code, which signs in through localhost.
Can I try MCP on the public demo?
No. MCP is turned off on demo.kamrapms.com because it is shared. Install Kamra on a small server or locally and connect Claude Code to try it safely.
Claude does not seem to load Kamra's tools.
Open a new chat, check the Kamra connector is turned on in the chat's tools menu, and reconnect if your role changed. Large tool lists load best when the connector's tools are set to load up front. After an admin changes your access, start a new chat so Claude reloads the tool list.