Your guests’ AI agents can book on your site

If you install Kamra on your own website or server, WebMCP puts booking tools on your public /book page. When a guest (or their assistant) opens that page, agents they already use - Gemini, Grok, Muse, Claude, ChatGPT and others - can search rooms, quote and book direct with you. No OTA in the middle.

This is for hotels that self-host or run Kamra on their own domain - the booking page is yours, and agent bookings stay first-party.

Who this is for

Operators who install Kamra on their own site (self-host, VPS, Frappe Cloud with your domain, or embedded as your hotel’s booking URL). Guests land on your /book. Staff MCP at /mcp is separate - that is for running the front desk with Claude. WebMCP is for the end guest’s agent.

What WebMCP does

WebMCP registers the same booking tools inside the browser on your live /book (and listing) pages. Whatever agent the traveller is using in that session can call those tools - Gemini, Grok, Muse, Claude, ChatGPT, or other MCP-capable assistants - as long as their browser supports WebMCP. You opt in once; you do not build a connector per vendor.

Same live inventory as a human guest (Kamra SIU), not the channel manager
Bookings land as source WebMCP (or Agent for headless /book/mcp)
After a sell, outbound ARI still updates so OTAs stop overselling
Optional Book-direct exclusive % - exclusive vs rack for humans and agents alike

Two ways agents reach you

WebMCP (in the page) - guest opens https://your-hotel/book with an agent in the browser. Tools appear automatically when the property setting is on.
Booking Engine MCP (headless) - https://your-kamra/book/mcp for scripts, n8n, Claude Code, partner bots and any MCP client that talks HTTPS without loading the page. Same tools; rate-limited; optional API key for partners.

Directory for discovery across hotels that opt in: kamrapms.com/book/directory.json.

Guest /book still works for humans

Sticky search, exclusive vs rack, an AI best-deal pick, and room × meal rate cards. Agents see the same prices the page shows.

How to turn it on

Install Kamra and put the booking page on your domain (or use your Kamra site URL as the book link).
In Booking Engine, make sure the public page is live.
Switch on Allow WebMCP / agent direct booking (off by default).
Optional: set Book-direct exclusive % and List in Kamra agent directory.
Share /book as usual. Guests’ agents that support WebMCP can use it when they open that URL. For headless clients:
```
claude mcp add --transport http kamra-booking https://your-kamra/book/mcp
```

Docs

Read the MCP guide Booking Engine MCP docs Star on GitHub

Platform

Deploy

Help