MCP

The Model Context Protocol (MCP) lets you connect an AI assistant — Claude, ChatGPT, Copilot in VS Code, or any other compatible client — directly to your Eveos data. Once connected, you can ask it to look up your events, find participants, check attendance, or even create and update data, all in plain language.

What you can ask it to do

Once your assistant is connected, talk to it the way you would to a colleague:

• “How many participants are registered for the Paris Tech Fair session?”
• “Find John Smith’s record in my event.”
• “Add this new participant to tomorrow’s session.”
• “Which exhibitors haven’t confirmed their booth yet?”

The assistant can only see and change what your Eveos account is already allowed to access — it never has more rights than you do.

Connect it

Server address

Enter this address in your MCP client’s configuration:

https://backend.eveos.com/mcp

With an API key

To connect a tool or a script rather than a personal assistant, use an API key, the same way you would for the public API. Never share this key in a chat, an email, or a public URL.

With your Eveos account

For personal use (Claude, ChatGPT, etc.), simply sign in with your usual Eveos account. The assistant will only see the organizers and data that account can already access.

Good to know before you start

Name the event when it matters

If you manage several organizers, events, or sessions, name the one you mean (“for my Paris Tech Fair event” rather than just “my event”). If a request stays ambiguous, the assistant will ask you to clarify before doing anything.

Creating something twice is safe

If a create request seems to have failed (error, dropped connection), you can safely ask again: Eveos will not create the same record twice for the same attempt.

Double-check look-alike results

If a name search returns several close matches (say, a participant and an exhibitor with the same name), confirm which one you mean before continuing.

Keep your access safe

• Never share your API key or your login credentials.
• Scope an API key used for automation to only what it needs (role, projects).
• Always review what an assistant is about to delete or change before confirming.

Limits

An assistant connected through MCP follows the same permissions and security rules as the rest of Eveos: it cannot bypass your access rights or act outside what your account allows. For any sensitive action (deletion, bulk changes), always check the result the assistant reports before treating it as done.