It is Tuesday evening, pre-sales for the autumn concert are running, and the chair sends a message: "How are we doing?" You log in, click through to the dashboard, then the event, then the ticket types, and type the answer across. Five minutes of work for one sentence. Tomorrow the treasurer asks the same question, but split out per ticket type.
Many organisers now have an AI assistant open anyway: Claude, ChatGPT, Cursor or the assistant in VS Code. It writes your newsletter and tidies up your notes, but it knows nothing about your ticket sales. The AI connector changes that. You connect your assistant to your MijnEvent dashboard and simply ask.
What is the AI connector?
The AI connector is a secured MCP server for your own organisation. MCP stands for Model Context Protocol: an open standard that lets an AI assistant use the tools of another system. MijnEvent supplies those tools, such as "fetch sales per ticket type" or "find an order". Your assistant picks the ones it needs to answer your question.
The difference with copying figures yourself: the assistant fetches the data from the dashboard at the moment you ask. There is no export from last week and nothing is guessed. And because you use your own assistant, you pay MijnEvent nothing for the language model and there is no fee per question.
What you can ask
You type your question the way you would ask a colleague. A few examples:
Asking your figures
- "How many tickets sold this week, and how does that compare with last week?"
- "Which ticket type for the summer festival is nearly sold out?"
- "What is the revenue for the fair so far, per ticket type?"
- "How many visitors have checked in already, and how many are we still expecting?"
Looking things up without clicking
- "Find the De Vries family's order. Has it been paid?"
- "Which discount codes are still active, and how often has MEMBERS been used?"
- "Who changed something on the King's Day event yesterday?"
- "Is the MijnEvent invoice for the spring concert still open?"
Having draft work prepared (only if you allow drafts)
- "Create a draft for next year's flea market, based on this year's."
- "Prepare a discount code MEMBERS25: 25 percent off, valid until 1 December."
- "Add a frequently asked question about parking at the sports hall."
- "Resend the confirmation email for the Jansen order."
For recurring work there are four ready-made prompts: a weekly report, a checklist that reviews a draft event before you publish, a briefing for the day itself and a debrief afterwards. The modules you use decide what else is available: if the Courses module is switched on, for example, the assistant can also look up enrolments.
Step 1 — Have the module switched on
The AI connector is a free module. Get in touch and we switch it on for your organisation; then you accept the module terms in the dashboard.
Step 2 — Add the address in your assistant
The address is the same for every organisation: https://mijnevent.nl/mcp. You add it in your assistant; when you sign in you enter your own organisation's address (the address of your dashboard, for example your-club.mijnevent.nl). That is all: there is no key to copy.
- claude.ai and the Claude app: go to Settings → Connectors and choose Add custom connector. Give it a name, paste the address, click Add and then Connect.
- ChatGPT: this only works with developer mode. Turn it on in the settings, create a connector with the address and choose OAuth as the authentication.
- Claude Code: one line in your terminal. Then type
/mcpin Claude Code, choose the server and then Authenticate. - Cursor and VS Code: a small configuration block with just the address. Then click Login in Cursor; VS Code asks by itself whether you want to sign in.
For Claude Code, that one line looks like this:
claude mcp add --transport http mijnevent https://mijnevent.nl/mcp
The dashboard shows the steps and the ready-made block for each assistant, with the address already filled in. No programming needed.
Step 3 — Sign in and choose what the assistant may do
Your assistant then opens a MijnEvent sign-in screen at your own organisation's address. If you are not signed in yet, you sign in first as usual. Then you choose two things: whether the assistant may only read or also prepare drafts, and how long the connection stays valid: 30, 90 or 365 days. You click Connect and you are done.
Feel free to start read-only. You can always allow drafts later with a new connection. The connection then appears in the dashboard under Your connections, with the name of the app. That is also where you revoke it.
Step 4 — Ask your first question
Ask, for example: "How are sales going for my next event?" The assistant only sees the tools that match your permissions and your connection. If you may not see orders in the dashboard, the assistant cannot see them through the connection either.
Rather use a key? For your own scripts
Are you writing your own script, or using an assistant that does not support signing in through Connect? Then expand Advanced: key for your own scripts under AI connector in the dashboard. You choose a name, read-only or also drafts, and a validity of 30, 90 or 365 days. The key is shown once; copy it straight away and keep it like a password. You send it in the Authorization header. The dashboard gives examples for Claude Code, Cursor, VS Code and your own script.
If your assistant can connect, use that instead. Then no key is passed around anywhere.
What the assistant cannot do, and why
An assistant can make mistakes: pick the wrong event, read a question differently from what you meant. With a figure that is awkward at most. With money, or with messages to hundreds of visitors, it is a real problem. That is why these actions do not exist as tools, not even if you allow drafts:
- refunding money
- publishing an event
- sending a mailing
- exporting data
- erasing data
If you ask for them you get a link to the right page in the dashboard and click yourself. What the assistant does create is a draft: an unpublished event, a discount code or a frequently asked question that you review and adjust. Every write action also starts as a preview, so you see what will happen first. It is the same principle as the AI helpers in the dashboard: the assistant does the first bit of work, you decide.
Permissions and privacy
A connection belongs to one team member and can never do more than that person. If you have set permissions per team member, for instance only certain events or view-only access to orders, they apply to the assistant too. Revoke a permission and it applies to the connection straight away.
The connection is sparing with personal data:
- Order lists contain amounts, status and quantities, but no names or email addresses.
- Customer data only comes along when you ask for one specific order.
- Every write action and every request for customer data is recorded in the activity log, together with the name of the connection.
- Exporting is not possible through the connection.
One thing to think about deliberately: whatever your assistant retrieves is processed by the provider of that assistant. That falls under your own agreement with that provider. So choose an assistant and a subscription whose privacy terms you know, and do not casually connect a personal account to your club's data.
Has a laptop gone missing, or is a volunteer stepping down? Revoke the connection with one click; other connections keep working. And every connection expires on its own anyway.
Which assistants work
The AI connector works with claude.ai and the Claude app, ChatGPT with developer mode, Claude Code, Cursor and VS Code. With all of these you add the address and sign in to MijnEvent. For your own scripts and other tools you use a key.
Two caveats. ChatGPT only works with your own MCP servers when developer mode is on, and that is not available on every plan. And if you use a business Claude account (Team or Enterprise), an admin of that account adds the connector first; then you click Connect.
Note the difference with the public events MCP. Every organiser already has one on their own subdomain, so visitors' AI assistants can find your published events and availability. It is read-only, needs no sign-in or key and comes with every pricing model. The AI connector is a separate, secured server for your own team.
What it costs
Nothing. The AI connector is free: there is no fee per question or per action. You bring the language model yourself: you pay the provider of your assistant for that, not MijnEvent. The fixed fee per ticket sold does not change.
Want to know more? The MCP server page puts everything side by side, including every tool. Price and terms are on the AI connector module page.
