Eventee MCP connector
The Eventee connector brings your event's lectures, speakers, partners, participants and registrations into Elaichi, so Claude, ChatGPT, Cursor or the Elaichi Agent can read and update them as the person who signed in.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Eventee to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Eventee once
-
Open Connections, choose Add connection, and pick Eventee.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Eventee API key. One person generates a token in Eventee and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Eventee MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Eventee MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Eventee MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Eventee to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Eventee through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Events
Build the agenda from a spreadsheet
Paste in the session plan and have the lectures and coffee breaks created in Eventee with the right times and rooms. Shift a whole afternoon when a keynote runs long.
-
Program
Fix a speaker bio before doors open
Update a speaker's title, photo or bio in Eventee from the correction they emailed at 7am. Swap a speaker on a lecture without opening the admin console.
-
Partnerships
Keep sponsor listings current
Add new partners as contracts close and update logos, tiers and descriptions across every sponsor in one pass. Remove a partner that pulled out.
-
Registration
Invite the waitlist in one go
Send Eventee invitations to everyone on the waitlist once seats free up, then check who has registered and who has not.
-
Marketing
Pull the lineup for the announcement
Ask for the full list of Eventee speakers and their lectures, grouped by track, ready to drop into the newsletter or the website.
-
Operations
Move participants after a room change
See which Eventee groups exist and reassign a batch of participants when a workshop moves, or clear out test registrations before the event goes live.
Try asking
- “List tomorrow's lectures and who is speaking at each”
- “Invite the ten people on this list as participants”
- “Update Acme's partner description with this new copy”
AI tools
Eventee tools for your AI agents
31 tools are ready to call through Elaichi's MCP endpoint the moment you connect Eventee, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Eventee gets you
6 screens from the product, each doing one job for your Eventee account.
The agent
Ask about your Eventee agenda in plain language.
Answers come from live Eventee lectures, speakers and registrations, not a stale export.
- lectures
- speakers
- partners
- participants
Ask Elaichi to work across your apps.
List tomorrow's lectures and who is speaking at each
Invite the ten people on this list as participants
Update Acme's partner description with this new copy
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Eventee in every AI client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Copy the endpoint
Tool catalog
31 Eventee tools, ready without writing code.
Create, update, list and remove lectures, speakers, partners, pauses, participants and registrations.
- Eventee event bulk delete
- List all Eventee groups
- Create a Eventee lecture
- Update a Eventee lecture by ID
Toolboxes
Every team gets its own Eventee toolbox.
The program team edits lectures while registration staff handle invites, each in its own scope.
- Events
- Program
- Partnerships
- Registration
Shared connections
Share one Eventee connection without sharing the key.
Teammates invite participants and update speakers through a connection whose credential they never see.
- Annual Summit
- Regional Roadshow
- Program
- Partnerships
Audit log
Every Eventee change is logged with a name.
See who deleted a lecture or invited a participant, when, and on which record.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Eventee registrations into finished work.
New registrations are fetched, grouped, drafted into a digest, approved by a person, then posted back.
Eventee digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch lectures
Eventee
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Eventee
Queued
Collections and dashboards
Eventee registration numbers refresh on a schedule.
Four metrics, 14 days of registrations created and a team breakdown, computed without a model.
Eventee health
Refreshed 4 minutes ago · every 15 minutes · from the lectures collection
Lectures
1,284 ↓ 12%
Speakers
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Lectures created
Last 14 days
By team
Share of activity
Annual Summit 34%
Regional Roadshow 27%
Program 21%
Partnerships 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Eventee to Claude?
First connect Eventee in Elaichi by pasting your Eventee API key, which takes about a minute. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and Eventee appears in Claude the next time you open it.
Does Eventee work with ChatGPT and Cursor as well as Claude?
Yes. Once Eventee is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Eventee once and every client you use picks it up.
What can an AI agent actually do with my Eventee data?
With Eventee connected, an agent can list your lectures, speakers, partners, participants and registrations, create or update lectures and breaks, add or edit speakers and sponsors, invite people, and update or remove participants in bulk. Short, concrete asks work best, such as "list tomorrow's lectures with their speakers" rather than a long paragraph. It works from the live Eventee event, so what it tells you is what your attendees would see.
Does connecting Eventee give the AI everything in my event?
No. Every call to Eventee runs as the person who signed in, so the agent can only reach the events and records that person's Eventee API key already allows. Elaichi can narrow that further, for example to read-only or to speakers and partners only, and it can never widen access beyond what the person has in Eventee.
Can I stop an agent from deleting or changing things in Eventee?
Yes. Restrictions in Elaichi apply per action, so you can allow reading and updating Eventee lectures while blocking deletion of lectures, speakers or registrations entirely. A restricted action is never advertised to Claude, ChatGPT or any other client, so no prompt, however worded, can reach it.
What happens to a Eventee connection when someone leaves?
When you offboard someone in Elaichi, their access to Eventee through every AI client ends at once. If they had shared a Eventee connection with the team, it keeps working for everyone else. If you ever want Eventee gone altogether, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Eventee MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Eventee is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Put Eventee in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.