# 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. Source: https://elaichi.ai/connectors/eventee/ ## Facts | | | | --- | --- | | Application | Eventee | | Category | Event Management | | AI tools | 31 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once Eventee is connected - 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 ## Connect Eventee in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Eventee. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Eventee tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Eventee MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Eventee to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Eventee tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Eventee through Elaichi ### Build the agenda from a spreadsheet Events. 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. ### Fix a speaker bio before doors open Program. 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. ### Keep sponsor listings current Partnerships. Add new partners as contracts close and update logos, tiers and descriptions across every sponsor in one pass. Remove a partner that pulled out. ### Invite the waitlist in one go Registration. Send Eventee invitations to everyone on the waitlist once seats free up, then check who has registered and who has not. ### Pull the lineup for the announcement Marketing. Ask for the full list of Eventee speakers and their lectures, grouped by track, ready to drop into the newsletter or the website. ### Move participants after a room change Operations. 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. ## 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 my team share one Eventee connection? Yes. One organizer connects Eventee in Elaichi and shares the connection with the events team, and nobody else ever sees or handles the Eventee API key. Each teammate still signs in to Elaichi as themselves, so the audit log records who invited a participant or changed a lecture, not just which connection was used. ### 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. ## All 31 Eventee tools Every tool below is callable through https://api.elaichi.ai/mcp once Eventee is connected, subject to the toolbox it is in and the restrictions on the caller. - **Eventee event bulk delete** (Delete). Clear all test content from an eventee event. Destructively deletes every hall, lecture, track, pause, speaker, and workshop from the event in one call. Returns an empty 204 response on success. - **List all Eventee groups** (List). List all groups configured for your Eventee event. Returns: success, data, meta. - **Create a Eventee lecture** (Create). Create a new lecture (session) in your Eventee event. Returns the created lecture record including id, name, start, end, hall_id, speakers, tracks, and type. Required: name, start, end, hall_id, speakers, type, tracks. - **Update a Eventee lecture by ID** (Update). Update an existing lecture (session) in your Eventee event by id. Returns the updated lecture record including id, name, start, end, hall_id, speakers, tracks, and type. Required: id, name, start, end, hall_id, speakers, type, tracks. - **Delete a Eventee lecture by ID** (Delete). Delete an existing lecture from your Eventee event by id. Returns an empty 204 response on success. Required: id. - **List all Eventee participants** (List). List all participants (attendees) in an Eventee event with basic info. Returns: id, name, email, firstName, lastName, groupId, checkedAt, registeredAt, company, position, role, success, data, meta. - **Eventee participants invite** (Invite). Invite attendees to an Eventee event. Returns the invitation result per attendee: qr_code and url. - **Eventee participants bulk delete** (Delete). Remove an invited attendee from an Eventee event; the attendee is identified in the request body, and if they have already entered, event access is revoked and linked information is removed. Returns a success envelope (success, data, meta) whose data mirrors the native Eventee API response. - **Eventee participants bulk update** (Update). Update an attendee's check-in in Eventee. Returns the attendee record: id, name, email, checked_at, registered_at, group_id, first_name, last_name, company, position, role. Required: attendee_id. - **Create a Eventee partner** (Create). Create a new partner (a partner, sponsor, or exhibitor profile) for an Eventee event. Returns the created partner record including id, company, email, phone, address, description, web, sponsor_info, and exhibitor_info. Requires company. - **List all Eventee partners** (List). List all partners created in an Eventee event. Returns partner records including id, company, email, phone, address, description, web, sponsor_info, and exhibitor_info. - **Update a Eventee partner by ID** (Update). Update an existing partner in an Eventee event. Returns the updated partner record including id, company, email, phone, address, description, web, sponsor_info, and exhibitor_info. Requires id and company. - **Delete a Eventee partner by ID** (Delete). Delete a partner from an Eventee event by id. Returns an empty 204 response on success. Required: id. - **Eventee partners bulk update** (Update). Replace all sections of an Eventee partner's profile — sections without an id are created, sections with an id are updated, sections missing from the array are deleted, and final order matches the request. Returns the partner record including id, company, email, phone, address, description, web, sponsor_info, and exhibitor_info. Required: partner_id and all sections. - **Create a Eventee pause** (Create). Create a new pause (break) in the eventee event agenda. Returns the created pause record with its id, name, start, end, description, created_at, and updated_at. Required: name, start, end. - **Update a Eventee pause by ID** (Update). Update an existing pause (break) in the eventee event agenda by id. Returns the updated pause record with its id, name, start, end, description, created_at, and updated_at. Required: id, name, start, end. - **Delete a Eventee pause by ID** (Delete). Delete a pause (break) from the eventee event agenda by id. Returns the pause record with its id, name, start, end, description, created_at, and updated_at. Required: id. - **List all Eventee registrations** (List). List all registrations for your Eventee event. Returns registration records with id, firstName, lastName, email, groupId, and status. - **Eventee registrations invite** (Invite). Invite one or more registrants to your Eventee event. Returns the registration records with id, firstName, lastName, email, groupId, and status. - **Eventee registrations bulk delete** (Delete). Remove an invited registrant from your Eventee event. Returns the removed registration record with id, firstName, lastName, email, groupId, and status. Required: email. - **Create a Eventee speaker** (Create). Create a speaker in an Eventee event. Returns the created speaker object including id, name, email, phone, company, and position. Required: name, phone. - **Update a Eventee speaker by ID** (Update). Update an existing speaker in an Eventee event by id. Returns the updated speaker object including id, name, email, phone, company, and position. Required: id, name, phone. - **Delete a Eventee speaker by ID** (Delete). Delete a speaker from an Eventee event by id. Returns an empty 204 response on success. Required: id. - **List all Eventee speakers** (List). List all speakers of an Eventee event. Returns: id, name, bio, company, country, email, event_id, facebook, language, linkedIn, phone, photo, position, thumbnail, twitter, web. - **Create a Eventee track** (Create). Create a track (label) for your Eventee event. Returns the created track's id, name, and color. - **Update a Eventee track by ID** (Update). Update an existing track (label) in your Eventee event by id. Returns the updated track's id, name, and color. Required: id. - **Delete a Eventee track by ID** (Delete). Delete a track (label) from your Eventee event by id. Returns the deleted track's id, name, and color. Required: id. - **List all Eventee reviews** (List). List all Eventee reviews (session ratings submitted by attendees). Returns: id, comment, stars, username, userId, userphoto, lectureId, lecture, device, OS, createdAt, updatedAt, success, data, meta. - **Create a Eventee hall** (Create). Create a new hall in eventee. Returns the created hall record including its id, name, created_at, and updated_at. Requires name. - **Update a Eventee hall by ID** (Update). Update an existing hall in eventee by id, e.g. to rename it. Returns the updated hall record including its id, name, created_at, and updated_at. Required: id, name. - **Delete a Eventee hall by ID** (Delete). Delete a hall in eventee by id. Returns an empty 204 response on success. Required: id.