Eventee MCP by usefulapi

WRITE: check a participant in at the event (sets checked_at to now) or undo the check-in. Use the participant `id` from eventee_list_participants. Fails if the person is not a participant of the event. PATCH /public/api/v1/attendee/{attendee_id}/checkin.

WRITE: add a break (coffee, lunch...) to the event program on the day of `start` (created if missing). POST /public/api/v1/pause.

WRITE: add a hall (room, stage or virtual space) to the event. Use the returned id as hall_id for sessions. POST /public/api/v1/hall.

WRITE: add a label (track) for sessions, with a colour. Use the returned id in label_ids of a session. POST /public/api/v1/label.

WRITE: add a session (lecture or workshop) to the event program. It appears in the event app for attendees. The event day is taken from `start` and created if missing. The hall, speakers and labels must already exist (create them first and pass their ids). POST /public/api/v1/lecture.

WRITE: add a speaker profile to the event (shown in the event app). Use the returned id in speaker_ids of a session. The photo, if given, is downloaded by Eventee from the URL. POST /public/api/v1/speaker.

WRITE, IRREVERSIBLE: delete a session (lecture or workshop) together with its questions, polls, workshop bookings and ratings. Needs confirm: true (without it: a preview, nothing deleted). DELETE /public/api/v1/lecture/{session_id}.

The whole program of the event the API token belongs to: halls, event days, sessions (`lectures`, type 0), workshops (type 1, with capacity and bookings), breaks (`pauses`), speakers and labels (`tracks`). Use it to read back ids (hall_id, speaker ids, label ids, session ids) before changing anything. Replies are compact: long texts are clipped (description_max), each part is paged (limit/offset, `more` maps each part with further rows to the offset to continue from; the reply is cut to a size budget, so for big events read one part at a time with `parts`) and `parts` selects what to read. Times are in the event's time zone. GET /public/api/v1/content.

WRITE: add up to 100 people to the event as attendees, optionally with a group and tickets. People who already have an Eventee account are added directly; others get a profile that links when they sign up with the same email. With send_email=true Eventee SENDS AN INVITATION EMAIL to every person listed (default false: no email); sending needs confirm: true (without it: a preview, nothing sent or added). Invalid entries and the event's admins/moderators are skipped silently by Eventee, so re-read eventee_list_participants to confirm. The first 25 are processed immediately, the rest in the background. Tickets replace the person's existing tickets. PUT /public/api/v1/attendee/invite.

Attendee groups of the event with the app features enabled for each (agenda, questions, polling, networking, ratings, ...), the ticket names that put people into the group automatically, and which group is the default. Use the ids as group_id when inviting or registering people. GET /public/api/v1/groups.

Participants of the event (attendees, speakers, moderators, admins) with role, group, tickets, check-in time and registration time. `role`: a = admin, m = moderator, l = speaker, e = attendee. `checked_at` is null until checked in. Anonymous participants and deleted accounts have a placeholder email without '@'. The personal app link of each participant is not returned. Filters apply after the full list is read; use limit/offset for large events. GET /public/api/v1/participants.

Partners (sponsors and exhibitors) of the event with company details, contact data, code and page sections. GET /public/api/v1/partners.

Registrations of the event (people who registered or were pre-registered) with status (pending / confirmed / declined), group, contact details and registration-form answers. Filters apply after the full list is read; use limit/offset for large events. GET /public/api/v1/registrations.

Session ratings left by attendees (1-5 stars with optional comment), each with the rated session, plus a per-session summary (count and average stars; the 50 most reviewed sessions, `summary_truncated` says if more exist: use session_id for a specific one). Filters apply after the full list is read. GET /public/api/v1/reviews.

WRITE: pre-register up to 100 people for the event (an existing registration with the same email is updated, not duplicated). With send_email=true Eventee SENDS A REGISTRATION EMAIL to every person listed (default false: no email); sending needs confirm: true (without it: a preview, nothing sent or registered). Invalid entries are skipped silently by Eventee, so re-read eventee_list_registrations to confirm. PUT /public/api/v1/registration/invite.

WRITE, IRREVERSIBLE: remove the person with this email from the event: their participation, invitation and tickets for this event are deleted (their Eventee account is not). Eventee reports success even when nobody had that email. Needs confirm: true (without it: a preview, nothing removed). DELETE /public/api/v1/attendee?email=.

WRITE, IRREVERSIBLE: delete the registration with this email. Eventee reports success even when no such registration exists. Needs confirm: true (without it: a preview, nothing deleted). DELETE /public/api/v1/registration?email=.

WRITE: replace a session (full update, not a patch). Eventee RESETS what is omitted: speakers, labels, type, capacity and the Q&A / moderation / polling switches, so `type`, `speaker_ids`, `label_ids`, `capacity`, `discussion`, `moderating` and `polling` are required here; read the session first with eventee_get_program and pass its current values (an empty list removes all). The hall and live stream are kept when omitted. `start` must fall on an existing day of the event. PATCH /public/api/v1/lecture/{session_id}.