Eventee MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Eventee MCP by usefulapi is answering right now. Last checked 5 min ago. It exposes 18 tools. Last commit 25 Oct 2026.

Read an Eventee event's program, participants and reviews; create sessions, speakers; invite.

Uptime history 25 hours of history

25 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

289 ms

Response time

average over 24h

Stars

last commit 25 Oct 2026

What changed 4

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.

25 Oct a tool changed version4 times that day

and 3 more, back to 25 October 2026

Nothing serious here today

Today is the operative word: we check Eventee MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add eventee --transport http https://eventee.usefulapi.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://eventee.usefulapi.io/mcp

~/.codex/config.toml

[mcp_servers.eventee]
url = "https://eventee.usefulapi.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "eventee": {
      "url": "https://eventee.usefulapi.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "eventee": {
      "type": "http",
      "url": "https://eventee.usefulapi.io/mcp"
    }
  }
}

Available tools 18

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

eventee

eventee_check_in_attendee

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.

eventee_create_break

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

eventee_create_hall

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.

eventee_create_label

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.

eventee_create_session

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.

eventee_create_speaker

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.

eventee_delete_session

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

eventee_get_program

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.

eventee_invite_attendees

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.

eventee_list_groups

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.

eventee_list_participants

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.

eventee_list_partners

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

eventee_list_registrations

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.

eventee_list_reviews

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.

eventee_register_people

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.

eventee_remove_attendee

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

eventee_remove_registration

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

eventee_update_session

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

Endpoints

URL	Transport	State	Latency	Checked
https://eventee.usefulapi.io/mcp	streamable-http	answering	203 ms	5 min ago

Alternatives to Eventee MCP by usefulapi

same job, measured the same way

WaiverFile MCP by usefulapi

by usefulapi

Read WaiverFile waivers, events, forms and SMS opt-ins; create and update events, invite managers.

17 tools answering

AddEvent MCP by usefulapi

by usefulapi

Read AddEvent calendars, events, RSVPs and subscribers; create and update calendars and events.

18 tools answering

Order Desk MCP by usefulapi

by usefulapi

Search Order Desk orders and inventory; read order items and shipments; create or update orders.

15 tools answering

e-Boekhouden MCP by usefulapi

by usefulapi

Read e-Boekhouden relations, invoices, ledgers, bookings and products; create relations, invoices.

25 tools answering

Pirsch Analytics MCP by usefulapi

by usefulapi

Read Pirsch web analytics: visitors, pages, referrers, UTM, events, funnels and sessions.

27 tools answering

Lago MCP by usefulapi

by usefulapi

Read Lago customers, subscriptions, invoices, usage and revenue analytics; write events.

24 tools answering

Bind ERP MCP by usefulapi

by usefulapi

Read Bind ERP clients, products, inventory, invoices, orders; create prospects, clients, orders.

26 tools answering

REVIEWS.io MCP by usefulapi

by usefulapi

Read REVIEWS.io product and company reviews, ratings, UGC, surveys; tag reviews; invite one buyer.

16 tools answering

Eventee MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Eventee MCP by usefulapi do?

It exposes 18 tools, read directly from the server on our last check. Among them: eventee_check_in_attendee, eventee_create_break, eventee_create_hall, eventee_create_label, eventee_create_session, eventee_create_speaker and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Eventee MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 289 ms. The bar chart above shows every period we have measured.

How do I connect Eventee MCP by usefulapi?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Eventee MCP by usefulapi need an API key?

No. Eventee MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Eventee MCP by usefulapi?

It answers our handshake in 289 ms on average, which is faster than 57% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Eventee MCP by usefulapi open source?

The code is open source: it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at eventee.usefulapi.io, which runs on its operator's own terms.