Jomablue MCP: Set Up and Troubleshooting
Jomablue MCP: Set Up and Troubleshooting
What Is Jomablue MCP?
Connect your AI client to Jomablue in three steps: you connect it, an Event Owner approves it, and you check it works.
Jomablue MCP lets your AI client, such as Claude or ChatGPT, read your Jomablue event data so you can ask questions about your events. It’s read-only, and a new AI client can’t see any event data until an Event Owner (someone with the Owner role in Jomablue) approves it.
For what you can ask once you’re connected, see “Jomablue MCP: What It Is and What You Can Ask”. If your IT or security team needs to approve the connection first, send them “Jomablue MCP: Security Overview for IT Teams”.
How to Set Up Jomablue MCP
Connecting is done in your AI client, so you or your IT team handle that part. If you have the Owner role, you can do all three steps yourself.
What you need
- A Jomablue user account with a role at Support level or higher
- An AI client that supports MCP connectors
- Someone with the Owner role in Jomablue to approve the AI client
Step 1: Connect Your AI Client (You)
In your AI client
- Get your MCP server URL from an Event Owner. They can copy it from Settings > MCP Settings in Jomablue, using the copy button next to the URL. It’s your Jomablue web address followed by
/mcp, in the formhttps://[your Jomablue address]/mcp. - In your AI client, add a new MCP connector and paste in the MCP server URL. Each AI client does this differently, so check its support documentation on adding MCP connectors.
- When your AI client prompts you, sign in with your own Jomablue account, the same way you normally do.
What you should see: your AI client shows Jomablue as connected, but it can’t answer questions about your events yet. It’s waiting for an Event Owner to approve it.
Step 2: Approve the AI Client (Event Owner)
In Jomablue
- Go to Settings > MCP Settings.
- Scroll to MCP OAuth Clients and find the AI client. AI clients are grouped by web address, such as claude.ai. A new AI client has no data scope yet.
- Under Data scopes, select the highest scope this AI client should reach: Configuration Auditing for event setup, or Reporting for event setup plus reporting figures.
- Select Save scopes.
What you should see: the scope you saved shows as selected for that AI client.
Step 3: Check It Works (You)
In your AI client
- Start a new chat. If your AI client still can’t see your events, refresh the Jomablue connector. Each AI client does this differently, so check its support documentation on refreshing MCP connectors.
- Ask a simple question, such as “Which of my Jomablue events can you see?”
What you should see: a list of the events you have access to in Jomablue.
Good to Know About Approval
- The data scope belongs to the AI client, not the person. Everyone who uses that AI client gets the same scope. Each person’s own Jomablue role still decides which events they can see through it.
- One approval can cover a whole team. People who connect through the same web address, such as claude.ai, can share one approved AI client. An Event Owner chooses which one new connections join by turning on Set as the default client. Only one AI client per web address can be the default.
- Some tools need approval for each connection. Tools that sign in from your own computer, such as Claude Code, register as a new AI client each time they connect, and each one needs a data scope.
Removing Access
An Event Owner can remove access at any time in Settings > MCP Settings, under MCP OAuth Clients.
| Action | What it does |
|---|---|
| Revoke client | Signs every person out of that AI client |
| Revoke (next to a person’s name) | Removes that person’s access and leaves the AI client usable for everyone else |
If Something Isn’t Working
| What you see | Why | What to do |
|---|---|---|
| Your AI client is connected but can’t see any event data, or says it’s waiting for approval | The AI client is new and has no data scope yet | Ask an Event Owner to complete Step 2 |
| Your AI client says you don’t have MCP permission | Using Jomablue MCP needs a Jomablue role at Support level or higher | Ask an Event Owner in your organisation to check your role |
| Your AI client says a tool is unavailable because your role doesn’t allow it | Your Jomablue role doesn’t include that tool | Ask an Event Owner in your organisation to check your role |
| An Event Owner changed the data scope but answers haven’t changed | Your chat started before the change | Start a new chat. If that doesn’t help, refresh the Jomablue connector in your AI client |
| Your AI client says the question needs a data scope it hasn’t been granted | The question needs Reporting and the AI client only has Configuration Auditing | Ask an Event Owner to change the data scope |
| One AI client works and a second one doesn’t | Each AI client is approved separately | Ask an Event Owner to grant a data scope to the second AI client |
| You and a colleague see different events | Each person only sees the events their own Jomablue role allows | Check your event access in Jomablue |
If none of these fits, try rephrasing your question. If the issue is with Jomablue MCP itself, create a support ticket.
Additional Notes
- Only Event Owners see the settings page. Only people with the Owner role can see Settings > MCP Settings.
- PII Data isn’t available yet. The PII Data scope is listed under Data scopes, but it can’t be used yet.
- Steps differ by AI client. Adding and refreshing an MCP connector works differently in each AI client, so check its support documentation.
Frequently asked questions
Do I need the Owner role to connect my AI client?
No. Anyone with a Jomablue role at Support level or higher can connect an AI client. An Event Owner then approves it in Step 2.
Does everyone on my team need to be approved separately?
Not always. The data scope belongs to the AI client, so people who connect through the same web address, such as claude.ai, can share one approved AI client. See “Good to Know About Approval”.
Can I take access away from one person only?
Yes. An Event Owner can select Revoke next to that person’s name. The AI client stays usable for everyone else.