My Profile
Sign Out
Knowledge Base
Tickets
Login
Articles in this section
  2. Integrations and API

Jomablue MCP

Published:
Updated:

Jomablue MCP gives your AI client, such as Claude or ChatGPT, a secure connection to your Jomablue event data. Ask plain-language questions about one event or several, and get answers directly from your AI client, 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 read-only. It answers questions and points out what needs attention, but it can’t change your event. Make any changes directly in Jomablue.

What You Can Ask About

Jomablue MCP helps you to work the way you want to by answering questions about a single event or several events at once. You can ask any question about your events, but the answers depend on your access level in Jomablue.

There are three access levels, and each gives more access than the last: Event Configuration, Event Reporting and PII (Personally Identifiable Information). See “Access Levels” below.

Screenshot_2026-10-22_at_91409 AM.png

Access Levels

Your access level controls which event data your AI client can see. It’s based on your Jomablue user account and tied to the connection you set up in your AI client, so each connection is separate. For example, an agency with two customers could connect one AI client to each customer’s Jomablue Instance.

Each access level includes everything in the level below it:

•  Event Configuration: configuration and audit data
•  Event Reporting: everything in Event Configuration, plus reporting data.
•  PII: everything in Event Reporting, plus questions about individuals.

You grant one access level per AI client in MCP Settings. The AI client has no access until you do. If you change an access level, you may need to refresh the MCP connector manually. You select one access level per AI client.

Your AI client explains why it can’t answer when:

•  it’s waiting for approval
•  you don’t have MCP permission
•  the question needs an access level it hasn’t been granted

Event Configuration

Ask questions about how an event is set up, from pages and forms to campaigns and templates, and catch issues before attendees see them.

Area
What You Can Ask About
Pages
Landing page status and configuration for an event, including the authored HTML, the delivered HTML and the registration embed snippet used to place a form on a page
Event settings
Email and SMS sender IDs, session restricted messages, short and long event descriptions, venue name and address, default header images, start and end dates and timezone, target attendance estimates, and whether the event is Jomablue-managed
Registration forms
Live registration form data for an event
Events
Top-level event details, counts and configuration
Vendors
The list of vendors for an event, and vendor traits, so vendors and sponsors can be grouped and queried by trait
Campaigns
Campaigns for one event or across every event you have access to, including status, send time, content and who they reach (shown by category name, such as Delegate), filtered by timing, status, type and channel.
Templates
Email, SMS and e-Ticket templates, including subject lines, body content and merge fields

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 rather than stopping the send, so this check catches typos before attendees see them. You can also run a built-in audit checklist across an event’s campaigns and templates, covering live campaigns only or all campaigns. See Managing Campaigns and Email Templates.

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?”
•  “Proofread the email templates and make sure the content suits the audience each campaign is sent to.”

Event Reporting

Everything you can ask with Event Configuration, plus questions about reporting figures such as registration counts and lead totals.

Area
What You Can Ask About
Registration counts
Registration counts by category for an event, matching the figures in the portal under Insights > Registration. See Registration reporting.
Vendor leads
Booth leads, sponsored-session leads, and unique and non-unique lead totals for each vendor. Booth lead totals match the vendor lead figures in the portal.
Sessions
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 in an event, with the program name and UID (unique identifier). Also 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.

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 each capture separately, so that person counts as two leads.

Session attendance aligns with sponsored-session lead reporting, so you can ask which session a vendor is sponsoring and how many people attended it.

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.

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.

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?”
•  “How many total leads are there for vendors with a given trait?”

What It Doesn’t Do

Jomablue MCP doesn’t cover custom fields, 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. The list keeps growing as more AI clients add MCP support.

Setting Up Jomablue MCP

Anyone with the Owner role or a Jomablue role at Support level or higher can set up Jomablue MCP.

FAQs

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. With a PII access level, it will be possible to ask about individual attendee records.

Can I rely on the figures my AI client gives me?

Your figures come straight from your live event data. As with any AI tool, check important figures in the portal before you share them.

Why can’t my AI client see data after my access level has been changed in Jomablue?

You may need to refresh the MCP connector manually. How you do this differs for each AI client, so check its support documentation on setting up and refreshing MCP connectors.

What do I do if it can’t answer my question?

Your AI client explains when it’s waiting for approval, you don’t have MCP permission or the question needs an access level it hasn’t been granted. If none of these applies, you may need to rephrase your question. “What You Can Ask About” and “What It Doesn’t Do” sections above show what’s covered.

Need Help?

Create a ticket at support.jomablue.com
Attachments
Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Access denied
Access denied