Eventee MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://eventee.usefulapi.io/mcp

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

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

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

https://eventee.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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) bef

• 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

• 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/registrat

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

• 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 th

• 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_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/lec

• 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 t

• 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_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_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_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_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_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

• 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 previ

• 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_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, nothi

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

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 91 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 18 个工具描述，未发现针对 AI 的隐藏指令

与“其他”中的其他服务器比较i

• 星标数多于此分类中其他 32476 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 32476 个服务器的 99% 更新
• 基础检查结果等于或优于此分类中其他 32476 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{