Articles in this section

Jomablue MCP: Security Overview for IT Teams

Published:
Updated:

Jomablue MCP: Security Overview for IT Teams

What Is Jomablue MCP?

Jomablue MCP is a read-only connector that lets an approved AI client query your organisation’s Jomablue event data, with access off by default and three checks on every request.

Jomablue is an event technology platform. Jomablue MCP lets people in your organisation ask an AI client, such as Claude or ChatGPT, questions about their Jomablue events. MCP (Model Context Protocol) is a standard way for AI tools to read data from other software. This guide covers what an IT or security reviewer needs to assess the connection.

  • Read-only. Jomablue MCP can’t create, change or delete anything in Jomablue.
  • Off by default. A newly connected AI client sees no event data until it’s approved in Jomablue.
  • Checked on every request. The AI client’s data scope, the person’s Jomablue role and the person’s access to the event are all checked each time.

How Access and Data Are Protected

Connection Details

Item Detail
MCP server URL Shown in Settings > MCP Settings in Jomablue, in the form https://[your Jomablue address]/mcp
Authorisation OAuth 2.1 with PKCE (SHA-256)
Client secret None
Access Read-only
Standard The published Model Context Protocol (MCP) authorisation specification

Sign-In

  • The connector uses OAuth 2.1, the current standard for secure delegated access.
  • People sign in with their own Jomablue account. No one shares passwords or API keys with the AI tool.
  • Sign-in supports single sign-on (SSO) and multi-factor authentication (MFA).
  • Every sign-in uses PKCE (SHA-256), which stops a stolen authorisation code being reused.
  • Access tokens travel only in a request header, never in a URL.

Approval Before Any Data Flows

  • Data access is off by default for every new AI client.
  • The Owner role (the Event Owner in our other MCP guides), the Trusted Admin Integrator role and the Trusted Support Integrator role can manage MCP connections. Someone with one of these roles must approve each AI client before it can read data.
  • Using Jomablue MCP needs a Jomablue role at Support level or higher.
  • An AI client, or one person’s access to it, can be revoked at any time.

Each AI client is approved for one of these data scopes:

Data scope What the AI client can read
No access No event data. Every new AI client starts here
Configuration Auditing Event, registration form, page, campaign and template configuration
Reporting Configuration Auditing, plus aggregate figures such as registration counts by category
PII Data Reporting, plus individual attendee records and other personal details. Not available yet

Three Checks on Every Request

Jomablue checks each request against:

  1. The AI client’s approved data scope.
  2. The signed-in person’s Jomablue role.
  3. The person’s access to the specific event.

Two people using the same AI tool see only the events their own roles allow.

Data Minimisation

  • Reporting returns aggregate counts, not attendee records.
  • Vendor data excludes contact details.
  • Attendee email addresses used in campaign filters are withheld. Only a count is shown.

Dedicated Endpoint and Encryption

  • Each customer has a dedicated endpoint and its own sign-in server.
  • All traffic is encrypted in transit over HTTPS.

AI Safety Guidance

  • The server instructs AI tools to treat event content as data, never as instructions. This reduces the risk of prompt injection through text stored in Jomablue.

Open Standards

  • The connector follows the published Model Context Protocol (MCP) authorisation specification.
  • It works with any compliant AI client, with no custom integration.

Additional Notes

  • PII Data isn’t available yet. No data scope currently gives an AI client access to individual attendee records.
  • Issues with the connector. If you run into an issue with Jomablue MCP itself, create a support ticket.

Frequently asked questions

Can Jomablue MCP change data in Jomablue?

No. It’s read-only. It can’t create, change or delete anything in Jomablue.

Do people share passwords or API keys with the AI tool?

No. Each person signs in with their own Jomablue account through OAuth 2.1 with PKCE, and no client secret exists.

Can an AI client read individual attendee records?

Not yet. Reporting returns aggregate counts, not attendee records, and the PII Data scope, which covers individual attendee records, is not available yet.

Related articles

Was this article useful?
Like
Dislike
Help us improve this page
Please provide feedback or comments
Access denied
Access denied