Agent-ready · MCP

Your event, as a source your attendees’ AI can talk to.

Your attendees increasingly ask their own AI — Claude, an assistant in their chat app, a copilot in their IDE — “what’s on at the conference today?”, “where should I take a client near the venue?”. Aikebom gives every event a live MCP endpoint: a read-only, structured source any of those agents can connect to and query directly. Your programme, your venue, the city around it — and your sponsors — 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 event over MCP means you don’t build an integration for each assistant: they connect to one endpoint and discover what they can ask.

01

The three layers, in order

The same hierarchy your concierge uses, now machine-readable: your sponsors and partners first (always disclosed), then your official programme and venue facts, then the live city — weather, travel times, what’s on. An agent gets your event’s priorities, not a generic web scrape.

02

A new surface for sponsors

Opt in and the feed carries your partners and their offers — with the mandatory disclosure and tracked links — so a sponsor is visible, and attributed, even inside someone else’s AI. Reach your sponsor report can measure, beyond your own app.

03

You decide what’s open

Per-event on/off, and you choose exactly which tools are exposed — programme only, or the full city toolkit. Read-only by design: no attendee data, no writes. An optional token-gated tier turns it into a paid API for partners who want deeper access.

04

Nothing else to build

It’s part of the platform. Switch it on in the admin, copy the URL, share it. The same grounded answers your concierge gives in chat and by voice — now available to the agents your attendees already trust.

For developers

One endpoint. Connect in a line.

The endpoint speaks MCP over Streamable HTTP (JSON-RPC 2.0), read-only. Point any MCP client at it and it discovers the available tools. Here’s the whole setup in Claude Code:

Your event’s endpoint
https://your-event.aikebom.com/api/mcp
Add it to an agent
claude mcp add --transport http your-event https://your-event.aikebom.com/api/mcp

A sample of what an agent can ask

Programme & sessionsVenue & event factsLive announcementsExhibitor directoryWeather & conditionsTravel & transit timesWhat’s on in the citySponsors & offers (opt-in)

The pitch in one line

Every other event is a PDF and an app you have to open. Yours is a live source your attendees’ own AI can simply talk to — with your sponsors built into the answer.

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.

The Aikebom endpoint
https://aikebom.com/api/site-mcp
Add it to an agent
claude mcp add --transport http aikebom https://aikebom.com/api/site-mcp
QR code for https://aikebom.com/api/site-mcp

Scan to hand the URL to an agent on your phone.

›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

getOverviewhowItWorksgetPricinggetAudienceValuegetFaqgetCaseStudygetContact

Make your event agent-ready.

Book a demo and we’ll connect a live event endpoint to an agent in front of you — and show the sponsor feed.

Demo buchen
  • No engineering on your side
  • Live in weeks
  • Anonymous & GDPR-by-design
MCP — agent-ready events · Aikebom