AI connector (MCP)

Run your ticketing from your own AI assistant

With the MijnEvent MCP server you ask questions about your own figures, look up orders without clicking around and have draft work prepared. From Claude, ChatGPT, Cursor or VS Code: you add one address, sign in to MijnEvent and from then on work with the same permissions you have in the dashboard.

View the module Request the connector
In short

What is the MijnEvent MCP server?

The MijnEvent MCP server is a secured connection between your dashboard and your own AI assistant, such as claude.ai, the Claude app, ChatGPT, Claude Code, Cursor or VS Code. MCP (Model Context Protocol) is the open standard that lets such an assistant talk to other software. You add your organisation's address in your assistant and sign in to MijnEvent. There you choose whether the assistant may only read or also prepare drafts, and whether the connection expires after 30, 90 or 365 days. From then on you ask in plain language how sales are going, which ticket type is nearly sold out or where an order has got to. If you allow drafts, the assistant prepares an event, a ticket type, a discount code or a frequently asked question. Refunding, publishing, sending mailings, exporting and erasing are things it cannot do. The connection follows the permissions of the team member who connects it, and whatever the assistant writes or views of personal data is recorded in your activity log. It is the free AI connector module.

What is MCP

A plug between your assistant and your dashboard

On its own, an AI assistant knows nothing about your club. Ask how many tickets have sold for the autumn concert and you first have to look the figures up yourself and paste them into the conversation. MCP solves that. It is an agreed way for an assistant to use the tools of another system. MijnEvent supplies those tools; your assistant picks the ones it needs to answer your question.

An open standard

Claude, ChatGPT, Cursor, VS Code and other assistants speak MCP. You are not tied to one provider: switch to another assistant and you add the same address there.

Your own assistant

You use the subscription you already have. You pay MijnEvent nothing for the language model, and there is no fee per question or per action.

Up-to-date data

The assistant fetches the figures from the dashboard at the moment you ask. It does not have to guess and does not work from last week's export.

What you use it for

Ask, look up and prepare

Examples as you would literally type them into your assistant.

Ask your figures

Dashboard, statistics, sales per ticket type and the check-in count, without building a report first.

How you ask
  • “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?”
  • “How many visitors have checked in at the fair so far?”

Look things up without clicking

Orders, discount codes, your team, the activity log and your MijnEvent invoices. The assistant searches; you do not have to go through five screens.

How you ask
  • “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?”

Have draft work prepared

If you allow drafts when connecting, the assistant prepares them for you. Every action starts as a preview, so you see what will happen first. Publishing is up to you.

How you ask
  • “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.”
  • “Resend the confirmation email for the Jansen order.”

Ready-made prompts

For recurring work there are four prompts your assistant runs in one go. In Claude Code you call them as a command, for example /mcp__mijnevent__weekrapport. In claude.ai, the Claude app, Cursor and VS Code they appear in the prompt menu; in other assistants you simply ask for them.

  • weekrapport Weekly report: sales, revenue and anything notable from the past week, in a short overview.
  • publicatie-checklist Pre-publication checklist: goes through a draft event before you press publish, covering dates, ticket types, capacity and texts.
  • dag-van-het-event Event-day briefing: expected visitors, check-in status and points to watch.
  • nabespreking Debrief: figures and lessons after the event, as a starting point for the evaluation with your team.
Connecting

Connected in four steps

No programming and no key to copy. You add one address in your assistant and sign in to MijnEvent.

  1. Request the module

    We switch the AI connector on for your organisation. You accept the module terms in the dashboard.

  2. Add the address

    Add the address mijnevent.nl/mcp in your assistant as a connector or MCP server. The address is the same for everyone; you choose your organisation when you sign in. In claude.ai and the Claude app you do that under Settings → Connectors; the dashboard shows the steps per assistant.

  3. Sign in and choose

    Your assistant opens MijnEvent. You enter your organisation's address, sign in as usual and choose read-only or also drafts, and a validity of 30, 90 or 365 days. Then you click Connect.

  4. Ask your first question

    Ask how sales are going, for example. The assistant only sees the tools that match your permissions and your connection.

Example for Claude Code
# One line in your terminal. The address is the same for every organisation.
claude mcp add --transport http mijnevent https://mijnevent.nl/mcp
# Then in Claude Code: /mcp, choose mijnevent and then Authenticate to sign in.
Read the full explanation on the blog →
Security

You decide what the assistant may do

Through the connection an assistant can never do more than the team member who connected it.

The team member's permissions

A connection belongs to one team member. If that person may only manage events or only see a few events, the same applies to the assistant. Revoke a permission and it applies straight away.

Your own sign-in, with an expiry date

You connect by signing in to MijnEvent yourself, so no key is passed around. Every connection expires after 30, 90 or 365 days. You revoke it with one click, without stopping any other connection.

Everything in your activity log

Every write action, and every time the assistant requests customer data, is recorded in the activity log together with the name of the connection.

Overviews without names

Order lists show amounts, status and quantities, not names or email addresses. Customer data only comes along when you ask for one specific order.

What is never possible

Refunding, publishing an event, sending a mailing, exporting or erasing data do not exist as tools. If you ask for them, you get a link to the right page in the dashboard.

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.

Two MCP servers

Public for your visitors, secured for your team

MijnEvent has two MCP servers. They use the same standard but serve a different purpose.

Public events MCP

For whom
Your visitors' AI assistants
What
Your published events, prices and availability. Read-only.
Access
No key needed
Address
{organiser}.mijnevent.nl/mcp/events
Price
Included with every pricing model

Dashboard MCP (AI connector)

For whom
You and your team members
What
Your dashboard data and draft work, within your permissions.
Access
Sign in through Connect (OAuth) or a key for your own scripts, always with an expiry date
Address
mijnevent.nl/mcp (or mijnevent.nl/mcp/{organisation})
Price
Free module
Works with

Which assistants you can connect

You add the address and sign in through Connect. For your own scripts, or an assistant that does not support that sign-in, you create a key in the dashboard.

  • claude.ai
  • Claude app
  • ChatGPT (with developer mode)
  • Claude Code
  • Cursor
  • VS Code
  • Your own scripts (with a key)

Good to know

ChatGPT only works with your own MCP servers when developer mode is on, and that is not available on every plan. If you use a business Claude account (Team or Enterprise), an admin of that account adds the connector first. Assistant menus change now and then; the dashboard shows the steps per assistant.

Tools

What the assistant can call

Which tools your assistant sees depends on your permissions, what you allow when connecting and the modules you have switched on.

Reading

  • get-organisation
  • get-dashboard
  • get-statistics
  • list-events
  • get-event
  • get-event-sales
  • get-checkin-stats
  • list-orders
  • get-order
  • find-order
  • list-coupons
  • list-team
  • get-activity
  • list-invoices
  • open-in-beheer

Drafts, only if you allow them

  • create-event-draft
  • update-event
  • upsert-ticket-type
  • create-coupon
  • create-guest-order
  • resend-order-confirmation
  • upsert-faq

Modules, only when the module is switched on

  • list-mailings
  • get-mailing-stats
  • get-feedback-results
  • list-rental-bookings
  • list-course-enrolments
  • get-membership-stats
  • get-city-card-stats
  • get-occupancy
  • get-attendee-data-summary
Frequently asked questions

Questions about the MCP server

What is an MCP server, in plain language?
MCP stands for Model Context Protocol. It is an open standard that lets an AI assistant use the tools of another system. The MijnEvent MCP server offers those tools for your dashboard: requesting figures, looking up orders and preparing drafts. Your assistant decides which tool it needs to answer your question.

Which AI assistants can I connect?
claude.ai and the Claude app (via Settings → Connectors), ChatGPT with developer mode, Claude Code, Cursor and VS Code. You add your organisation's address in your assistant and sign in to MijnEvent. For your own scripts, or an assistant that does not support that sign-in, you create a key in the dashboard.

Do I have to copy a key?
No, usually not. Your assistant opens a MijnEvent sign-in screen, you sign in and choose what it may do, and the connection then appears in the dashboard. You only create a key for your own scripts or for an assistant that does not support that sign-in. That key is shown once and you send it in the Authorization header.

Can the assistant refund money, publish an event or send a mailing?
No, and that is a deliberate choice. Refunding, publishing, sending mailings, exporting data and erasing data do not exist as tools, not even if you allow drafts. 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 that you review and adjust.

What does the assistant see of my visitors?
A list of orders contains amounts, status and quantities, but no names or email addresses. Customer data only comes along when you ask for one specific order, and that is recorded in your activity log every time. Exporting is not possible through the connector. Whatever your assistant retrieves is processed by the provider of that assistant; that falls under your own agreement with that provider.

Can a team member do more through the assistant than in the dashboard?
No. A connection belongs to the team member who connects it and can never do more than that person. If someone may only view orders, the assistant only sees the matching tools. If a team member is limited to certain events, so is the assistant. Revoke a permission and it applies to the connection straight away.

What if a laptop goes missing or a volunteer leaves?
Revoke the connection in the dashboard under AI connector; the assistant or script loses access immediately, while other connections keep running. Every connection also expires on its own after 30, 90 or 365 days, depending on what you chose when connecting. The activity log shows what was done with a connection.

What does the AI connector cost?
Nothing. The AI connector is a free module: 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.

How is this different from the public events MCP?
Every organiser already has a public MCP server on their own subdomain, which lets visitors' AI assistants find your published events, prices and availability. It is read-only, needs no sign-in or key and is included with every pricing model. The AI connector is a separate, secured server for your own team, with your dashboard data and draft work.