Jomablue MCP: What It Is and What You Can Ask
Jomablue MCP: What It Is and What You Can Ask
What Is Jomablue MCP?
Jomablue MCP lets your AI client, such as Claude or ChatGPT, read your Jomablue event data, so you can ask plain-language questions about your events and get answers without exporting data or checking multiple screens in the portal.
MCP (Model Context Protocol) is a standard way for AI tools to read data from other software. Jomablue MCP is the connection between your AI client and your Jomablue events.
- It’s read-only. Jomablue MCP answers questions and points out what needs attention, but it can’t change your event. Make any changes directly in Jomablue.
- Nothing is shared until an Event Owner approves it. A newly connected AI client can’t see any event data until an Event Owner (someone with the Owner role in Jomablue) grants it a data scope.
- It follows your Jomablue permissions. Your AI client only ever sees the events you already have permission to access in Jomablue.
To connect your AI client, see “Jomablue MCP: Set Up and Troubleshooting”. If your IT or security team needs to review the connection, send them “Jomablue MCP: Security Overview for IT Teams”.
How to Ask Jomablue MCP About Your Events
How Jomablue MCP Works
What happens when you ask a question
- You ask. You ask a question in your AI client, in plain language.
- Your AI client asks Jomablue. Your AI client asks Jomablue for the event data it needs to answer.
- Jomablue checks. Jomablue checks three things: the data scope granted to that AI client, your Jomablue role, and your access to the event.
- You get the answer. Jomablue sends back only the data that passes all three checks, and your AI client writes the answer.
Data Scopes
You can ask about one event or several at once. What your AI client can answer depends on its data scope. A data scope is the setting an Event Owner picks in Settings > MCP Settings to control how much event data an AI client can read. Each scope includes everything in the scope before it. Older articles call these access levels.
| Data scope | What it covers |
|---|---|
| No access | No event data. This is where every new AI client starts. |
| Configuration Auditing | How an event is set up: event, registration form, page, campaign and template configuration. |
| Reporting | Everything in Configuration Auditing, plus aggregate figures such as registration counts by category. |
| PII Data | Everything in Reporting, plus individual attendee records and other personal details. Not available yet. |
What you see also depends on your own Jomablue role and event access, so you and a colleague may get different answers to the same question.
Configuration Auditing
Ask how an event is set up, and catch issues before attendees see them.
| Area | What you can ask about |
|---|---|
| Pages | Landing page status and configuration, including the authored HTML, the delivered HTML and the registration embed snippet |
| Event settings | Sender IDs, session restricted messages, event descriptions, venue name and address, header images, dates and timezone, target attendance, and whether the event is Jomablue-managed |
| Registration forms | Live registration form data for an event |
| Events | Top-level event details, counts and configuration |
| Sessions and speakers | Full session details, including traits, descriptions, session codes, linked speakers and location. An overview of an event’s sessions with their times, locations and overlaps. A speakers list with each speaker’s name, job title, company and sessions |
| Vendors | The vendors for an event and their traits, so vendors and sponsors can be grouped and queried by trait |
| Campaigns | Campaigns for one event or every event you can access: status, send time, content and who they reach (by category name, such as Delegate) |
| Templates | Email, SMS and e-Ticket templates, including subject lines, body content and merge fields |
Built-in checks
- Merge tag check. Jomablue MCP can check every template on an event for merge tags that won’t fill in when sent. An unrecognised merge tag is sent as literal text and doesn’t stop the send, so this check catches typos before attendees see them.
- Audit checklist. You can run a built-in audit checklist across an event’s campaigns and templates, covering live campaigns only or all campaigns. You can also run a built-in audit of an event’s registration forms.
Example questions
- “Which pages are still in draft?”
- “Are all registration forms live for this event?”
- “Check that every email and SMS template mentions the new venue.”
- “Check all templates for this event for merge tag typos.”
- “For this event, are there any more Delegate campaigns going out, and when?”
Reporting
Everything in Configuration Auditing, plus reporting figures such as registration counts and lead totals.
| Area | What you can ask about |
|---|---|
| Registration counts | Registration counts by category, matching the figures in the portal under Insights > Registration. For each category, you can also see where records came from, such as an integration (Ingest API), import, manual addition, online or onsite free registration, or the online store |
| Vendor leads | Booth leads, sponsored-session leads, and unique and non-unique lead totals for each vendor. Booth lead totals match the portal |
| Session attendance | Session name, start and finish times in the event’s local time, location, attendee count, lead count, and whether attendance is scanned or inferred |
| Programs | Ingested and allocated member counts for every program, and allocated member counts per member status for a selected program, including statuses Jomablue calculates, such as Attended. Figures match the Programs area of the portal |
Reading the figures
- Unique and non-unique leads. A unique lead total counts a person captured at both a vendor’s booth and one of its sponsored sessions as one lead. A non-unique total counts that person as two leads.
- Programs and campaigns. Programs are sometimes called campaigns. Jomablue MCP keeps program membership data separate from email and SMS campaign data, so your AI client returns the right information whichever term you use.
Example questions
- “How many people have checked in for each category?”
- “Which vendors are sponsoring a session, and how many leads did each capture at their booth and in the session?”
- “Which programs hold members outside the expected statuses?”
Additional Notes
- Check important figures. Figures come straight from your event data, but AI clients can misread or summarise data incorrectly. Check important figures in the portal before you share them.
- Not covered yet. Jomablue MCP doesn’t cover integrations, communities or digital signage and screens. Coverage is expected to expand over time.
- Compatible AI clients. Jomablue MCP connects to any AI client that supports MCP connectors, including Claude, ChatGPT and Amazon Quick.
- Each connection is separate. For example, an agency with two customers could connect one AI client to each customer’s Jomablue Organisation.
Frequently asked questions
Can Jomablue MCP change my event?
No. It’s read-only, so your event stays exactly as you set it up. Make any changes directly in Jomablue.
Is the data up to date?
Yes. Answers reflect your event data at the moment you ask.
Can I ask about individual attendee records?
Not yet. The PII Data scope, which covers individual attendee records, is not available yet.