Skip to content

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.

1

In Elaichi

Connect Eventee once

  1. Open Connections, choose Add connection, and pick Eventee.

  2. Optionally set Share with to give a team access, 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.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

eventee
Eventee
1Password
360learning
7shifts
Acquire
Active Ants
2

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. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 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. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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”

See all 31 Eventee tools below

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

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
ElaichiTools
Tool Action Description
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.

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
ElaichiToolboxes
Name Source template Tools Created

Events toolbox

Eventee · agenda and breaks

Eventee starter 18 Mar 4, 2026

Program toolbox

Eventee · lectures and speakers

— 9 Mar 2, 2026

Partnerships toolbox

Eventee · sponsors and partner listings

— 24 Feb 27, 2026

Registration toolbox

Eventee · invites and participants

Eventee starter 6 Feb 19, 2026

Marketing toolbox

Eventee · lineup and announcements

— 31 Jan 30, 2026

Operations toolbox

Eventee · groups and bulk changes

— 12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
EV

Eventee (Annual Summit)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
EV

Eventee (Regional Roadshow)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
EV

Eventee (Program)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
EV

Eventee (Partnerships)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
EV

Eventee (Registration desk)

Connected by Clara Nowak

Personal • Active Not shared
EV

Eventee (Marketing)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Eventee Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Eventee Lectures Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Eventee Lectures List Toolbox

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

  1. ✓

    Schedule

    Every weekday at 08:00

    0.2s
  2. ✓

    Fetch lectures

    Eventee

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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%

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 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.

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
Claude ChatGPT Cursor 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.