Eventee MCP server
31 operations0 webhooks
Manage an Eventee event program, partners, attendees, registrations, groups and session reviews through the public REST API.
Try Eventee with your agent
Connect Eventee, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.
Using Corsair, show me what you can do in Eventee on my account, then run one read-only example and show me the result.
Eventee tools and triggers
Tools are what your agent can do in Eventee through Corsair's MCP server. Triggers are the Eventee events a routine can start from.
Partner
- DeleteDestructive
Delete a partner and all of its detail page sections
partner.delete
- GetRead-only
List all event partners with sponsor and exhibitor details
partner.get
- PatchWrite
Replace a partner profile and sponsor or exhibitor media
partner.patch
- PostWrite
Create an event sponsor or exhibitor partner profile
partner.post
Hall
- DeleteDestructive
Delete a hall and every session placed in it
hall.delete
- PatchWrite
Update a hall and its live stream assignment
hall.patch
- PostWrite
Create a hall for sessions in the event program
hall.post
Label
- DeleteDestructive
Delete a label and remove it from all sessions
label.delete
- PatchWrite
Update an event program label
label.patch
- PostWrite
Create a colored label for categorizing sessions
label.post
Pause
- DeleteDestructive
Remove a break from the event program
pause.delete
- PatchWrite
Update a break in the event program
pause.patch
- PostWrite
Add a break to the event program
pause.post
Session
- DeleteDestructive
Delete a session including its questions, polls, bookings and ratings
session.delete
- PatchWrite
Update a lecture or workshop and its scheduling details
session.patch
- PostWrite
Create a lecture or bookable workshop in the event program
session.post
Speaker
- DeleteDestructive
Delete a speaker and remove them from all sessions
speaker.delete
- PatchWrite
Update fields on an event speaker profile
speaker.patch
- PostWrite
Create a speaker profile for the event
speaker.post
Attendees
- DeleteDestructive
Remove an attendee, their event participation, invitation and tickets
attendees.delete
- GetRead-only
List event participants with roles, groups and check-in details
attendees.get
Registrations
- DeleteDestructive
Delete an event registration by email address
registrations.delete
- GetRead-only
List event registrations with statuses and profile details
registrations.get
Attendee Check In
- PatchWrite
Check in an attendee or undo their event check-in
attendeeCheckIn.patch
Attendee Invite
- PutDestructive
Invite attendees by email with optional profile details and tickets
attendeeInvite.put
Content
- GetRead-only
Read the complete event program, speakers, halls, breaks and labels
content.get
Content Reset
- DeleteDestructive
Irreversibly delete all program content, halls, speakers and labels
contentReset.delete
Groups
- GetRead-only
List attendee groups and their enabled app features
groups.get
Partner Sections
- PatchDestructive
Replace a partner detail page sections list
partnerSections.patch
Registration Invite
- PutDestructive
Create or update event registrations by email
registrationInvite.put
Reviews
- GetRead-only
List attendee ratings and comments for event sessions
reviews.get
Connect Eventee to Claude, ChatGPT or Cursor
- 1
Connect Eventee in Corsair
Add your Eventee API key once in Corsair. Corsair stores the credential encrypted and makes the Eventee API calls for your agent, so it never goes into a prompt or a config file. Connect Eventee
If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Eventee. On a ChatGPT personal plan, connect Eventee here first.
- 2
Add Corsair's MCP server to your agent
Every client uses the same address:
https://mcp.corsair.dev/mcpOpen Customize → Connectors → Add custom connector, paste the address, then select Connect.Add a custom MCP server with the address and choose OAuth. Personal plans get read tools only.Add to CursorOr add this to~/.cursor/mcp.json. Cursor opens Corsair to sign in the first time it connects.{ "mcpServers": { "corsair": { "url": "https://mcp.corsair.dev/mcp" } } }Run this, then run/mcpin Claude Code to sign in.claude mcp add --transport http corsair https://mcp.corsair.dev/mcpCodex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client
- 3
Sign in and choose what needs your approval
Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Eventee's read and write operations run right away and its 12 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.
FAQ
Install corsair and @corsair-dev/eventee, add the Eventee plugin, and connect with an API key. Then call methods like corsair.eventee.api.attendeeCheckIn.patch() from your app. Corsair keeps each tenant isolated.
Yes. Eventee requires an API key from your Eventee account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Eventee, GitHub, Notion, Stripe, and the rest. Trigger Eventee from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for manage an Eventee event program, partners, attendees, registrations, groups and session reviews through the public REST API. Common builds include sync jobs, admin tooling, and agents that call Eventee APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Eventee API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/eventee in the open repo. When Eventee ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Eventee data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Eventee data on your behalf.
Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.
Yes. Put Eventee on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 12 destructive Eventee operations. You can change a link's mode at hub.corsair.dev/me.