Agent-ready · MCP
Connect your AI to the property — or the event.
Your guests and attendees increasingly ask their own AI — Claude, an assistant in their chat app, a copilot in their IDE — “what’s on today?”, “where should I eat near here?”. Aikebom gives every property and event a live MCP endpoint: a read-only, structured source any of those agents can connect to and query directly. Your services, your programme, the city around you — and your partners — answered inside the tool they’re already using. No data collected, nothing to install.
What’s MCP?
The Model Context Protocol is the emerging open standard for connecting AI agents to live data and tools — think “USB-C for AI”. Agents already speak it. Exposing your property or event over MCP means you don’t build an integration for each assistant: they connect to one endpoint and discover what they can ask.
The idea
Every property is its own MCP server.
Point an assistant at a hotel and it gets a property server — house services, check-in and check-out, the neighbourhood, the official partners and outlets. Point it at an event and it gets that event’s programme, venue and exhibitors. The surface speaks each client’s own language, and it’s live: verified right inside Claude, with every partner surfaced alongside the disclosure that has to travel with it. Not a scraped page — the same grounded answers the concierge gives in chat and by voice.
The three layers, in order
The same hierarchy your concierge uses, now machine-readable: your partners and sponsors first (always disclosed), then your official programme, services and venue facts, then the live city — weather, travel times, what’s on. An agent gets your priorities, not a generic web scrape.
A new surface for partners
Opt in and the feed carries your partners, outlets and their offers — with the mandatory disclosure and tracked links — so a partner is visible, and attributed, even inside someone else’s AI. Reach your report can measure, beyond your own app.
You decide what’s open
You switch your endpoint on or off, and you choose exactly which tools are exposed — programme or house services only, or the full city toolkit. The endpoint you hand to partners and integrations is read-only and carries no guest data. A checked-in guest connecting their own assistant is a separate, opt-in connection — scoped to their stay, and the only one that can act: raising a request your staff confirm, or adding a stop to their own plan. Token-gating turns the partner endpoint into a paid API for those who want deeper access.
Nothing else to build
It’s part of the platform. Switch it on in the admin, mint a key, share it. The same grounded answers your concierge gives in chat and by voice — now available to the agents your guests already trust.
How access works
Token-gated by default. You grant the key.
Your property’s — or your event’s — endpoint is read-only and closed by default: you grant access with a key you mint yourself, and revoke at any time. It speaks MCP over Streamable HTTP (JSON-RPC 2.0). Claude.ai connectors can’t send headers, so they take the key on the URL; Claude Code and other clients send it as a bearer header. Both forms below use placeholders — you mint the real key in the admin.
https://aikebom.com/api/mcp?event=<your-event>&key=<token>claude mcp add --transport http your-event "https://aikebom.com/api/mcp?event=<your-event>" --header "Authorization: Bearer <token>"A sample of what an agent can ask
The other door · A2A
An agent card, so the trade can address you directly.
MCP is the door you hand a key to. A2A — the emerging agent-to-agent standard — is the other one: your property or event publishes an agent card at a fixed address on your own domain, and any peer agent can read it and ask. The caller here isn’t your guest. It’s the trade: a travel organiser’s assistant, a DMC’s, a corporate booker’s, or a shopper’s agent hunting a spa hotel in Milan with a room for twelve. It’s open and needs no key — a marketing channel a stranger can’t read isn’t a marketing channel — and everything on it is material you published: no guest data, no bookings, nothing your team hasn’t approved.
Written by your marketing team
A pack you author, for the buyer rather than the guest: your positioning, your meeting and function spaces with their capacities, room types, the packages currently running, your accolades, and who to call in sales and press. Not scraped, not inferred from an old brochure — the words you chose, in the language you chose, answered on request.
Your partners travel with it
Opt in and the card carries your official partners and outlets, and the promotions currently valid — each with its commercial relationship disclosed and its link tracked, so a referral that begins inside somebody else’s agent still lands in your report. Lapsed promotions are filtered out: a machine feed has no reader to notice a dead date.
You see who came asking
Every query is counted in your dashboard by skill, next to what agents asked for and couldn’t get. Clicks arriving through the agent channel are attributed separately from your own traffic — new demand, in a channel that barely has competition yet.
What a buyer’s agent gets back
Where you are and what you are, your spaces and their capacities, your current packages with their validity dates, your accolades, your sales and press contacts, your media kit — and your partners, disclosure attached. Read-only, and switched on per client: it is off until you ask for it.
Two honest limits
The card makes you addressable: an agent that has your address, or follows a link to it, can ask. Getting listed in the directories where assistants go looking is a separate step — by hand, with your consent, never a switch in an admin panel. And the card is promotional by design: your guest-facing announcements and your internal programme are never served on it. Those follow your property’s own access rules, and a public endpoint is not where they belong.
https://aikebom.com/.well-known/agent-card.jsonWe run one on ourselves first. That address is a real card for a real business — fetch it, or point an A2A client at it, and it answers as Aikebom: what we are, what we cost, how to reach us.
For organisers & hoteliers
Switch it on. Curate it. Share it.
You enable the endpoint from your own admin: turn it on, curate exactly which tools are exposed, opt into the partner feed, and mint a separate key per integration. It’s the same content your concierge already grounds on — no new data to maintain.
And an index agents can find
Every property and event also publishes an AI-readable index at /llms.txt — a plain-text map an assistant can read to discover the concierge, its languages, and this endpoint. It’s how agents find you before they connect.
The pitch in one line
Every other property is a PDF and an app you have to open. Yours is a live source your guests’ own AI can simply talk to — with your partners built into the answer.
Inside a guest’s own AI
A hotel, answering inside Claude.
Palazzo Vetra — our fictional demonstration property — connected as a live MCP server inside a guest’s Claude: property facts, partner recommendations with the disclosure attached, tracked links. This is what agent-ready looks like from the guest’s side.
Palazzo Vetra is a fictional demonstration property operated by Aikebom.
Try it on us
Connect your own agent to this very site.
Before you take our word for it, point your own AI at us. We run the same idea on aikebom.com: a live, read-only MCP endpoint your agent can query right now for what Aikebom is, how it works, pricing, FAQ, our case study, and how to get in touch — no human reading the site required. That’s exactly the experience your attendees get, pointed at your event instead.
https://aikebom.com/api/site-mcpclaude mcp add --transport http aikebom https://aikebom.com/api/site-mcp
Scan to hand the URL to an agent on your phone.
Proof, not promises
Watch an agent query this site — right now.
This button makes your browser do exactly what an AI assistant does: call our live endpoint, list its tools, and ask one of them a question. Real endpoint, real response, nothing staged.
›How do I connect it to my assistant?
It’s a standard remote MCP endpoint, so any MCP-capable assistant can read it. The common ones:
Claude (including the iPhone/Android app)
- Custom connectors can’t be added from the mobile app — add it once at claude.ai in a browser, and it syncs to your phone automatically.
- On claude.ai: Settings → Connectors → “Add custom connector”, paste the endpoint URL, then “Add”. No authentication needed — it’s public and read-only, so leave Advanced settings empty.
- In the Claude app (iPhone/Android): open a chat, tap “+”, turn on “Aikebom”, and ask “What is Aikebom, and what does it cost?”
- Works on the Free, Pro, Max, Team and Enterprise plans.
ChatGPT
- Settings → Connectors → enable Developer mode, then add a connector pointing at the endpoint URL. Turn it on from the composer’s tools menu. (Availability depends on your ChatGPT plan.)
Gemini
- Remote MCP is supported through the Gemini API/SDK and the Gemini CLI (Streamable HTTP) rather than the consumer app — point your client at the endpoint URL.
Any MCP client / Claude Code / IDEs
- Run: claude mcp add --transport http aikebom https://aikebom.com/api/site-mcp
Hosted assistants like Claude connect to the endpoint from their own cloud, so it only needs to be reachable on the public web — which it is once this is live on aikebom.com.
What it can answer about us
Make your property agent-ready.
Book a demo and we’ll connect a live endpoint to an agent in front of you — and show the partner feed.
- No engineering on your side
- Live in weeks
- Anonymous & GDPR-by-design