AddEvent MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

AddEvent MCP by usefulapi is answering right now. Last checked 1 min ago. It exposes 18 tools. Last commit 12 Oct 2026.

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

Uptime history 4 hours of history

4 hours agonow

100.0%

Uptime 24h

12 of 12 checks

Tools

read from the server

135 ms

Response time

average over 24h

Stars

last commit 12 Oct 2026

Nothing serious here today

Today is the operative word: we check AddEvent 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 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

{
  "mcpServers": {
    "addevent": {
      "url": "https://addevent.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.

addevent

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.

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.

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.

addevent_get_calendar

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

addevent_get_calendar_subscriber

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

addevent_get_event

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

addevent_get_rsvp_attendee

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

addevent_list_calendar_subscribers

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.

addevent_list_calendar_templates

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.

addevent_list_calendars

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.

addevent_list_event_templates

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.

addevent_list_events

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.

addevent_list_rsvp_attendees

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.

addevent_list_rsvp_forms

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

addevent_list_timezones

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.

addevent_update_calendar

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

addevent_update_event

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

addevent_update_rsvp_attendee

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

Endpoints

URL	Transport	State	Latency	Checked
https://addevent.usefulapi.io/mcp	streamable-http	answering	173 ms	1 min ago

Alternatives to AddEvent MCP by usefulapi

same job, measured the same way

Cronofy MCP by usefulapi

by usefulapi

MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.

8 tools answering

Nylas MCP by usefulapi

by usefulapi

MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.

15 tools answering

Orb MCP by usefulapi

by usefulapi

Read Orb customers, subscriptions, invoices, usage and costs; create or update customers.

26 tools answering

Mailchimp MCP by usefulapi

by usefulapi

Read audiences, members, campaigns and reports; add, update, tag and archive subscribers.

18 tools answering

Reclaim.ai MCP by usefulapi

by usefulapi

Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits.

15 tools answering

rapidmail MCP by usefulapi

by usefulapi

Read rapidmail lists, recipients, mailings and stats; add, update or unsubscribe one recipient.

16 tools answering

SavvyCal MCP by usefulapi

by usefulapi

Read and create SavvyCal scheduling links and booked events.

8 tools answering

Aircall MCP by usefulapi

by usefulapi

Read calls, contacts, users, teams and numbers; tag calls and create or update contacts.

25 tools answering

AddEvent MCP by usefulapi — questions

Answers built from our own checks of this server.

What can AddEvent MCP by usefulapi do?

It exposes 18 tools, read directly from the server on our last check. Among them: addevent_create_calendar, addevent_create_event, addevent_create_rsvp_attendee, addevent_get_calendar, addevent_get_calendar_subscriber, addevent_get_event 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 AddEvent MCP by usefulapi working right now?

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

How do I connect AddEvent MCP by usefulapi?

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

Does AddEvent MCP by usefulapi need an API key?

No. AddEvent 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 AddEvent MCP by usefulapi?

It answers our handshake in 135 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is AddEvent MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.