AddEvent MCP by usefulapi

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

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

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "AddEvent MCP by usefulapi": {
      "url": "https://addevent.usefulapi.io/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (18)

• addevent_list_calendars read-only

  List the account's calendars (newest first by default) with id, title, timezone, whether it is the default calendar, landing-page links and counts of events and subscribers. GET /calendars.

  Parameters:

  • page — integer — Page number, from 1 (default 1). Pass the previous reply's next_page.
  • sort_by — string — Sort field (default created).
  • page_size — integer — Results per page, 1-20 (default 10).
  • sort_order — string — Sort direction. Needs sort_by.
  • calendar_ids — array — Only these calendar ids.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_get_calendar read-only

  One calendar by id: title, timezone, week start, template ids, subscriber and event counts, links, custom data. GET /calendars/{id}.

  Parameters:

  • calendar_id (required) — Calendar id (see addevent_list_calendars).

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_create_calendar

  WRITE: creates a new calendar in the AddEvent account (a new, empty calendar; nothing existing is changed and nobody is notified). Needs a title. POST /calendars.

  Parameters:

  • title (required) — string — Calendar title (single line).
  • timezone — string — Default timezone for events on this calendar (IANA name).
  • custom_data — object — Arbitrary key-value pairs to store on the object (snake_case keys), e.g. an external id.
  • description — string — Shown on the calendar landing page.
  • internal_name — string — Internal name, never shown publicly.
  • weekday_begin — string — First day of the week.
  • calendar_color — integer — Color 1-20 from the palette.
  • landing_page_template_id — string — Calendar landing page template id, or 'default' (see addevent_list_calendar_templates).
  • embeddable_calendar_template_id — string — Embeddable calendar template id, or 'default'.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• addevent_update_calendar destructive

  WRITE: changes fields of an existing calendar (only the fields you pass; the rest stay). Title, description and timezone changes show on its landing page and can reach people who subscribe to the calendar feed. Not reversible by this server (no previous values are kept), so read the calendar first. PATCH /calendars/{id}.

  Parameters:

  • calendar_id (required) — Calendar id to change.
  • title — string — New title (single line).
  • timezone — string — IANA timezone such as America/Los_Angeles, or 'floating' (same local time for everyone). See addevent_list_timezones.
  • custom_data — object — Key-value pairs to store on the calendar (snake_case keys).
  • description — string
  • internal_name — string — Internal name, never shown publicly.
  • weekday_begin — string
  • calendar_color — integer — Color 1-20 from the palette.
  • landing_page_template_id — string
  • embeddable_calendar_template_id — string

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• addevent_list_events read-only

  Search the account's events (newest created first; by start time when a date filter is used): title, start/end, timezone, location, RSVP settings and stats, landing-page links. Filter by calendar, event ids, text, date window or a custom_data pair. GET /events.

  Parameters:

  • page — integer — Page number, from 1 (default 1). Pass the previous reply's next_page.
  • search — string — Case-insensitive text in title, internal name, description or location.
  • sort_by — string — Sort field.
  • event_ids — array — Only these event ids.
  • page_size — integer — Results per page, 1-20 (default 10).
  • ends_after — string — Only events that end after this date-time (datetime_min; naive comparison, timezones ignored).
  • sort_order — string — Sort direction. Needs sort_by.
  • calendar_ids — array — Only events on these calendar ids.
  • starts_before — string — Only events that start before this date-time (datetime_max; naive comparison, timezones ignored).
  • custom_data_key — string — Custom data key (needs custom_data_value).
  • custom_data_value — string — Custom data value (needs custom_data_key).

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_get_event read-only

  One event by id (evt-...): all fields incl. description, organizer, reminder, recurring rule, RSVP settings and stats, custom data and share links. GET /events/{id}.

  Parameters:

  • event_id (required) — Event id, like evt-0f571af553d8437eb6a9ce22384fdcba (see addevent_list_events).

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_create_event

  WRITE: creates a new event on a calendar (the account's default calendar if calendar_id is omitted). Creates a public event landing page and share links; it does not e-mail anyone, though people subscribed to that calendar's feed will see the event on their next sync. Needs title and datetime_start. POST /events.

  Parameters:

  • title (required) — string — Event title (single line).
  • datetime_start (required) — string — Start date-time: YYYY-MM-DD, YYYY-MM-DD hh:mm or YYYY-MM-DD hh:mm:ss.
  • color — integer — Color 1-20 from the palette.
  • location — string — Address or URL (meeting link). Use either location or location_id, not both.
  • reminder — integer — Minutes before the start for a calendar-app reminder (0-10800).
  • timezone — string — IANA timezone for the start/end (default: the calendar's timezone), or 'floating'.
  • free_busy — string — How the event shows in an attendee's calendar.
  • calendar_id — Calendar to add the event to (see addevent_list_calendars); default calendar if omitted.
  • custom_data — object — Arbitrary key-value pairs to store on the object (snake_case keys), e.g. an external id.
  • description — string — Plain text or simple HTML (keep under ~500 characters for cross-browser links).
  • location_id — integer — Id of a saved location (0 = none). Not together with location.
  • datetime_end — string — End date-time (default: start + 1 hour). Same formats as the start.
  • rsvp_enabled — boolean — Require an RSVP before the event can be added to a calendar.
  • rsvp_form_id — string — RSVP form id or 'default' (see addevent_list_rsvp_forms).
  • all_day_event — boolean — All-day event: only the dates are used.
  • internal_name — string — Internal name, never shown publicly.
  • organizer_name — string — Organizer name (needs organizer_email).
  • recurring_rule — string — iCalendar recurrence rule such as FREQ=WEEKLY;COUNT=10. The start must match the rule. Omit for a one-off event; on update an empty string makes the event stop repeating.
  • organizer_email — string — Organizer e-mail (needs organizer_name).
  • landing_page_template_id — string — Event landing page template id or 'default' (see addevent_list_event_templates).

  Hints: read-only no · destructive no · idempotent no · open-world yes

• addevent_update_event destructive

  WRITE: changes fields of an existing event (only the fields you pass; the rest stay). The change goes live on its landing page and share links, and people who subscribed to the calendar or added the event with a live link are updated on their next calendar sync, so a time or location change can notify real people. No previous values are kept: read the event first. PATCH /events/{id}.

  Parameters:

  • event_id (required) — Event id (evt-...) to change.
  • color — integer — Color 1-20 from the palette.
  • title — string — New title (single line).
  • location — string — Address or URL (meeting link). Use either location or location_id, not both.
  • reminder — integer — Minutes before the start for a calendar-app reminder (0-10800).
  • timezone — string — IANA timezone for the start/end (default: the calendar's timezone), or 'floating'.
  • free_busy — string — How the event shows in an attendee's calendar.
  • calendar_id — Move the event to this calendar id.
  • custom_data — object — Arbitrary key-value pairs to store on the object (snake_case keys), e.g. an external id.
  • description — string — Plain text or simple HTML (keep under ~500 characters for cross-browser links).
  • location_id — integer — Id of a saved location (0 = none). Not together with location.
  • datetime_end — string — End date-time (default: start + 1 hour). Same formats as the start.
  • rsvp_enabled — boolean — Require an RSVP before the event can be added to a calendar.
  • rsvp_form_id — string — RSVP form id or 'default' (see addevent_list_rsvp_forms).
  • all_day_event — boolean — All-day event: only the dates are used.
  • internal_name — string — Internal name, never shown publicly.
  • datetime_start — string — New start: YYYY-MM-DD, YYYY-MM-DD hh:mm or YYYY-MM-DD hh:mm:ss.
  • organizer_name — string — Organizer name (needs organizer_email).
  • recurring_rule — string — iCalendar recurrence rule such as FREQ=WEEKLY;COUNT=10. The start must match the rule. Omit for a one-off event; on update an empty string makes the event stop repeating.
  • organizer_email — string — Organizer e-mail (needs organizer_name).
  • landing_page_template_id — string — Event landing page template id or 'default' (see addevent_list_event_templates).

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• addevent_list_rsvp_attendees read-only

  List RSVP attendees (personal data: e-mail addresses and the answers they gave on the RSVP form). Filter by calendar, event or response (going/maybe/not-going). Paged, 20 at most per page: read only what the task needs. IP address and coordinates are removed from the reply. GET /rsvps.

  Parameters:

  • page — integer — Page number, from 1 (default 1). Pass the previous reply's next_page.
  • sort_by — string
  • attending — string — Only attendees with this response.
  • event_ids — array — Only attendees of these event ids.
  • page_size — integer — Results per page, 1-20 (default 10).
  • sort_order — string — Sort direction. Needs sort_by.
  • calendar_ids — array — Only attendees of events on these calendar ids.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_get_rsvp_attendee read-only

  One RSVP attendee by id (personal data: e-mail and form answers; IP address and coordinates removed). GET /rsvps/{id}.

  Parameters:

  • attendee_id (required) — RSVP attendee id (see addevent_list_rsvp_attendees).

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_create_rsvp_attendee

  WRITE: adds ONE RSVP attendee (one e-mail address, personal data) to an event. This server never asks AddEvent to send the confirmation or organizer notification e-mails, but the event's own reminder and follow-up e-mails (if the event has them) will later go to this address, so only add someone who really RSVP'd. The e-mail must be unique per event. POST /events/{id}/rsvps.

  Parameters:

  • event_id (required) — Event id (evt-...) to RSVP to.
  • email (required) — string — Attendee e-mail address (unique per event).
  • attending — string — The attendee's response.
  • rsvp_form_data — object — Answers to the event's RSVP form as field-name -> value. The default form needs {"name": "..."}.

  Hints: read-only no · destructive no · idempotent no · open-world yes

• addevent_update_rsvp_attendee destructive

  WRITE: changes ONE RSVP attendee (email, response or form answers; only the fields you pass). The event's reminder and update e-mails go to the e-mail address stored here, so changing it redirects those e-mails to that person. This server never triggers the confirmation or organizer notification e-mails. PATCH /rsvps/{id}.

  Parameters:

  • attendee_id (required) — RSVP attendee id.
  • email — string — New e-mail address.
  • attending — string
  • rsvp_form_data — object — Answers to the event's RSVP form as field-name -> value. The default form needs {"name": "..."}.

  Hints: read-only no · destructive yes · idempotent yes · open-world yes

• addevent_list_calendar_subscribers read-only

  List people subscribed to the account's calendars (personal data: the form answers they gave, such as name and e-mail; calendar app type, sync status). Paged, 20 at most per page. IP address and coordinates are removed. GET /subscribers.

  Parameters:

  • page — integer — Page number, from 1 (default 1). Pass the previous reply's next_page.
  • status — string — active = synced in the last 30 days; inactive = not; blocked = blocked by the owner. AddEvent returns only active ones when omitted, so call once per status.
  • sort_by — string
  • page_size — integer — Results per page, 1-20 (default 10).
  • sort_order — string — Sort direction. Needs sort_by.
  • calendar_ids — array — Only subscribers of these calendar ids.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_get_calendar_subscriber read-only

  One calendar subscriber by id (personal data; IP address and coordinates removed). GET /subscribers/{id}.

  Parameters:

  • subscriber_id (required) — Subscriber id (see addevent_list_calendar_subscribers).

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_list_rsvp_forms read-only

  The account's RSVP forms (id, name), newest first. Use the id as rsvp_form_id on an event. GET /events/rsvp-forms.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_list_event_templates read-only

  The account's event landing page templates (id, name), newest first. Use the id as landing_page_template_id on an event. GET /events/templates.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_list_calendar_templates read-only

  The account's calendar landing page templates or embeddable calendar templates (id, name), newest first. Use the id as landing_page_template_id / embeddable_calendar_template_id on a calendar. GET /calendars/templates.

  Parameters:

  • type — string — calendar-landing (default) or calendar-embed (embeddable calendars).

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

• addevent_list_timezones read-only

  Timezone names AddEvent supports (use them as the timezone of events and calendars), with current UTC offset. Optional text filter on the name. GET /timezones.

  Parameters:

  • limit — integer — Most entries to return (default 100).
  • search — string — Case-insensitive part of the name, e.g. 'Prague' or 'America/'.

  Hints: read-only yes · destructive no · idempotent not declared · open-world yes

Publisher website Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.