{"id":6793,"date":"2026-10-07T18:23:32","date_gmt":"2026-10-07T16:23:32","guid":{"rendered":"https:\/\/eventscase.com\/blog\/?p=6793"},"modified":"2026-10-07T18:23:32","modified_gmt":"2026-10-07T16:23:32","slug":"ai-for-events-mcp-eva-brain","status":"publish","type":"post","link":"https:\/\/eventscase.com\/blog\/ai-for-events-mcp-eva-brain","title":{"rendered":"AI for events that works inside your platform: the Eventscase MCP and EVA Brain"},"content":{"rendered":"\n

Until recently, working with AI for events<\/strong> felt rather like talking to someone very clever who had no access to anything. You pasted the programme into the chat, asked it to draft an email to the speakers, copied the response and added it to the platform yourself. AI helped, but moving information from one place to another was still your job.<\/p>\n\n\n\n

That is changing, and at Eventscase, we already have the piece that makes it possible for our platform: our own MCP. With it, the AI your team uses can work directly within your events, adding, editing and deleting agenda items, attendees and speakers. And precisely because it can do all of that, we\u2019ve decided not to release it on its own. First, we want to add one final layer: EVA Brain, which determines who can work on each project and holds the team\u2019s shared memory.<\/p>\n\n\n\n

In this article, we explain what an MCP is without getting technical, what it means for a team that organises events, and why we believe AI for events<\/strong> needs more than a connection to be genuinely useful.<\/p>\n\n\n\n

<\/p>\n\n\n\n

What is an MCP, and what does it change about AI for events?<\/strong><\/h2>\n\n\n\n

<\/p>\n\n\n\n

MCP stands for Model Context Protocol. Anthropic<\/a> introduced it in November 2024 as an open standard for connecting AI assistants to the systems that hold data: workplace tools, document repositories and business applications.<\/p>\n\n\n\n

The simplest way to understand it is to think of a universal plug. Previously, getting AI to work with a particular tool meant someone had to build a bespoke integration for that specific combination. With an MCP, the tool makes its capabilities available once, and any compatible assistant can use them.<\/p>\n\n\n\n

From AI that answers to AI that acts<\/strong><\/h3>\n\n\n\n

The practical difference is significant. AI without a connection answers questions about the information you give it. AI connected through an MCP can retrieve that information from the platform and, with permission, change it.<\/p>\n\n\n\n

Take a familiar situation. Your client sends over the final programme in a document with twenty sessions, three room changes and two new speakers. Without MCP, AI can help you organise that document, but you still have to upload everything to the platform, session by session. With the Eventscase MCP, you ask your AI to build the agenda from that document, and it does so directly within your event.<\/p>\n\n\n\n

A standard the industry already uses<\/strong><\/h3>\n\n\n\n

This is not something we invented, nor are we taking an isolated approach. OpenAI<\/a> adopted MCP in March 2025 and integrated the standard into its products, including the ChatGPT desktop application. In December 2025, Anthropic donated it to the Agentic AI Foundation, a Linux Foundation fund. This matters for a very practical reason: the Eventscase MCP works with the AI your team already uses, such as Claude or ChatGPT, without forcing you to switch tools.<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n

\n
\"-\"<\/figure><\/div>\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

What the Eventscase MCP will be able to do<\/strong><\/h2>\n\n\n\n

<\/p>\n\n\n\n

In this first phase, the Eventscase MCP brings AI for events<\/strong> into three areas of any event: the agenda, attendees and speakers. Across all three, it can add new information, edit existing information and delete it.<\/p>\n\n\n\n

For the agenda, that means building or updating the programme from the document your client sends, changing a session\u2019s time or moving it to another room. These are tasks that currently take hours of copying and pasting, and where a mistake becomes visible as soon as the first attendee opens the event app.<\/p>\n\n\n\n

For attendees, it means uploading a list, correcting details or removing someone who has cancelled. For speakers, it means adding biographies, updating job titles or removing someone who is no longer taking part. This information keeps changing until the last day and usually arrives by email, in a different format each time.<\/p>\n\n\n\n

If you already use AI in your day-to-day work, as we discussed in AI for events:<\/em><\/strong> 8 practical applications<\/em><\/a>, the shift here is that it stops being a separate tool and starts working with your event\u2019s actual data.<\/p>\n\n\n\n

<\/p>\n\n\n\n

The problem is not the connection \u2014 it is the team<\/strong><\/h2>\n\n\n\n

<\/p>\n\n\n\n

When we built the MCP and saw it working, we asked ourselves an uncomfortable question: do we really want anyone to be able to connect AI to an event, give it permission to delete attendees and walk away? The answer brought us to two problems that have less to do with technology than with how events teams work.<\/p>\n\n\n\n

Who can change what<\/strong><\/h3>\n\n\n\n

An MCP connects, but it does not make decisions. If AI can read an event\u2019s data, it can also delete it; if it can change a session, it can also change the wrong one. And it acts on behalf of the person giving it instructions.<\/p>\n\n\n\n

For an events team, that is no small detail. In the weeks before a conference, extra staff join, people from the agency and the client work together, and each person needs access to a different part of the project. It is the same principle as event access passes: nobody gives every member of staff a pass that opens every door in the venue. AI needs to work in the same way, which is why every project needs clear rules about who can view information and who can add or change it.<\/p>\n\n\n\n

Where does the team\u2019s knowledge live?<\/strong><\/h3>\n\n\n\n

The second problem is less visible and, for many teams, even more significant. Today, when someone uses AI to prepare an event, everything that AI learns lives in that person\u2019s individual account: agreements with the client, why a supplier was ruled out, what changed in the last meeting. It is like a notebook everyone takes home at night.<\/p>\n\n\n\n

While that person stays on the project, it works. But people move in and out of events teams all the time. Someone switches projects, extra help arrives three weeks before the event, or the next edition begins with a different person in charge, and what the AI knew is not available to anyone else. Everything has to be explained again. Or worse, decisions are made without knowing what has already been agreed.<\/p>\n\n\n\n

Connecting AI for events<\/strong> to the platform without addressing these two issues speeds up the work, but it also speeds up the mistakes.<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n

\n
\"-\"<\/figure><\/div>\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

EVA Brain: the layer we\u2019re finishing<\/strong><\/h2>\n\n\n\n

<\/p>\n\n\n\n

EVA Brain is our response to those two problems, and the reason the Eventscase MCP has not been released yet. Think of it as the team\u2019s shared brain: a place in the cloud that holds each project\u2019s context and controls who can work with it.<\/p>\n\n\n\n

A shared memory for each project<\/strong><\/h3>\n\n\n\n

EVA Brain gathers project information, remembers it and makes it available to the people working on that project. It stores each event\u2019s agreements, changes and background in one place, without relying on any one person. It is also designed to allow an agent to join meetings, transcribe them and add what was discussed to the project, so a decision made on a call does not remain solely in the memories of the people who attended.<\/p>\n\n\n\n

Each project retains its own context, separate from the others, so information about one conference does not get mixed up with another event for the same client. When someone joins or takes over, they can get up to speed with what is already known rather than starting from scratch.<\/p>\n\n\n\n

Permissions and change history<\/strong><\/h3>\n\n\n\n

EVA Brain\u2019s second function is control. It determines who can view each project and who can add or change information. It also keeps a history of changes, so the team can review how its knowledge has developed.<\/p>\n\n\n\n

This is where it fits together with the MCP. An AI that can delete attendees needs someone to decide what it is allowed to touch, and that is the layer we are finishing before launching the Eventscase MCP.<\/p>\n\n\n\n

Working with your usual AI<\/strong><\/h3>\n\n\n\n

From the user\u2019s perspective, the process is straightforward. You connect EVA Brain to your usual AI, such as Claude or ChatGPT, through MCP. From then on, when you ask it to prepare a brief, proposal or report, it works with the project\u2019s context and what the team has agreed along the way, rather than just what you tell it at that moment. It is a way to stop AI for events<\/strong> from starting from scratch in every conversation.<\/p>\n\n\n\n

<\/p>\n\n\n\n

What changes for an events team<\/strong><\/h2>\n\n\n\n

<\/p>\n\n\n\n

AI agents for events are often presented with a broad promise: AI will do things for you. We prefer to look at situations any team will recognise.<\/p>\n\n\n\n

The first is bringing in extra staff during busy periods. Someone joins three weeks before the conference, and there is no time to explain everything that has already been decided. With EVA Brain, the AI that person uses works with the project\u2019s context, but only the parts they have permission to access.<\/p>\n\n\n\n

The second is the next edition. The team starts preparing next year\u2019s event and wants to revisit what worked with suppliers, what problems arose, and what was decided and why. If that information was added to the project, it is still there, even if the person who contributed it has moved on.<\/p>\n\n\n\n

The third is a change of project lead. When someone leaves a project halfway through, the project\u2019s knowledge remains available to authorised team members, without relying on anyone\u2019s memory.<\/p>\n\n\n\n

In each case, the MCP enables AI to move from answering questions to taking action within Eventscase, while EVA Brain gives that action context and boundaries. It is the difference between AI agents for events that work on their own and those that work as part of the team.<\/p>\n\n\n\n

<\/p>\n\n\n\n

Why AI in events needs time to become useful<\/strong><\/h2>\n\n\n\n

<\/p>\n\n\n\n

We could have launched the Eventscase MCP as soon as it worked. It would have been quicker, and we could have said we got there before anyone else. But AI in events is only useful if the team can trust it, and that trust depends on two things a connection alone cannot provide: knowing what each person is allowed to do and holding on to what the team already knows.<\/p>\n\n\n\n

AI for events<\/strong> will increasingly work inside the tools you already use, rather than alongside them. The question that sets teams apart will no longer be whether they use AI, but whether their AI knows what the team knows and respects what each person is authorised to decide.<\/p>\n\n\n\n

That is where we want to be.<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

The Eventscase MCP is ready: it lets your team\u2019s AI add, edit and delete agenda items, attendees and speakers in your events. We explain what that means and why we\u2019ve decided not to launch it until EVA Brain is ready.<\/p>\n","protected":false},"author":3,"featured_media":6796,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"pgc_meta":"","footnotes":""},"categories":[1],"tags":[388,6,22],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/posts\/6793"}],"collection":[{"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/comments?post=6793"}],"version-history":[{"count":1,"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/posts\/6793\/revisions"}],"predecessor-version":[{"id":6797,"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/posts\/6793\/revisions\/6797"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/media\/6796"}],"wp:attachment":[{"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/media?parent=6793"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/categories?post=6793"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/eventscase.com\/blog\/wp-json\/wp\/v2\/tags?post=6793"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}