Skip to main content
Glama
addevent-mcp-server

addevent-mcp-server

by UtahREIA

addevent-mcp-server

An MCP server that wraps the AddEvent Calendar & Events API v2, so Claude can create, search, retrieve, update, and delete events, calendars, and RSVP attendees on your AddEvent account.

Tools

Events — addevent_create_event, addevent_search_events, addevent_get_event, addevent_update_event, addevent_delete_event

Calendars — addevent_create_calendar, addevent_search_calendars, addevent_get_calendar, addevent_update_calendar, addevent_delete_calendar

RSVP attendees — addevent_create_rsvp, addevent_search_rsvps, addevent_get_rsvp, addevent_update_rsvp, addevent_delete_rsvp

Helper — addevent_list_timezones (looks up valid timezone values for events/calendars)

Related MCP server: google-calendar-mcp

1. Get your AddEvent API key

Sign in at dashboard.addevent.com, go to Settings > API, and copy the API token. This is the value the server sends as Authorization: Bearer <token> on every request.

2. Run it locally (stdio, for Claude Desktop)

npm install
cp .env.example .env    # then paste your API key into ADDEVENT_API_KEY
npm run build
npm start

To use it from Claude Desktop, add it to your MCP config (Claude Desktop settings > Developer > Edit Config):

{
  "mcpServers": {
    "addevent": {
      "command": "node",
      "args": ["/absolute/path/to/addevent-mcp-server/dist/index.js"],
      "env": {
        "ADDEVENT_API_KEY": "your-api-token-here"
      }
    }
  }
}

3. Deploy to Vercel (remote connector, works from any device)

This mirrors your existing ghl-mcp-remote setup.

npm install -g vercel   # if you don't already have it
vercel login
cd addevent-mcp-server
vercel

Then, in the Vercel project dashboard: Settings > Environment Variables, add ADDEVENT_API_KEY with your token, and redeploy so the function picks it up.

Your MCP endpoint will be:

https://<your-project-name>.vercel.app/api/mcp

Add that URL as a custom connector in Claude (claude.ai > Settings > Connectors, or wherever your workspace manages MCP connectors), the same way ghl-mcp-remote.vercel.app shows up in your tool list now.

4. Test before connecting

The MCP Inspector is the fastest way to sanity-check tool calls before wiring the server into Claude:

npx @modelcontextprotocol/inspector

Point it at node dist/index.js (stdio) or http://localhost:3000/mcp (after running TRANSPORT=http npm start locally).

Notes on the AddEvent API

  • Base URL: https://api.addevent.com/calevent/v2. Auth is a Bearer token, not an API-key header.

  • Search endpoints return up to page_size (max 20) results per call — use page to page through more.

  • The AddEvent docs list the search-calendars response's array key as calendar (singular), which is inconsistent with events and rsvps elsewhere. The client code (src/format.ts, extractArray) checks both calendar and calendars defensively so this doesn't silently return an empty list — worth confirming against a real response the first time you run addevent_search_calendars, and simplifying once confirmed.

  • Deleting an event, calendar, or RSVP attendee is permanent — there's no undo or archive endpoint in this API.

  • RSVP creation only works on events created with rsvp_enabled: true.

Extending this server

Not covered yet, but straightforward to add if you need them later: calendar subscribers, RSVP forms, and event/calendar landing page templates (all read-only list/search endpoints in the AddEvent API). Follow the pattern in src/tools/timezones.ts for a minimal read-only tool.

Available Tools

16 tools
addevent_create_calendarCreate AddEvent CalendarA

Creates a new calendar (a container that events live inside).

Args:

  • title (string, required): The calendar's title.

  • timezone, weekday_begin, description, internal_name, calendar_color, landing_page_template_id, embeddable_calendar_template_id, custom_data: optional fields.

Returns: The created calendar object as JSON, including its calendar_id.

Examples:

  • "Set up a separate calendar for the WREIA meetups" -> title: "WREIA Meetups".

  • Don't use when: you just need to add an event to an existing calendar (use addevent_create_event with calendar_id instead).

Error Handling:

  • Returns "Error: Invalid request..." (400) if title is missing.

Inputs: title (required), timezone, custom_data, description, +5 more.

addevent_create_eventCreate AddEvent EventA

Creates a new event on an AddEvent calendar.

Args:

  • title (string, required): The event's title.

  • calendar_id (string, optional): Target calendar. Defaults to the account's default calendar. Use addevent_search_calendars to find IDs.

  • datetime_start (string, required): Start date/time, e.g. "2026-09-15 18:00" or "2026-09-15" for a date-only event.

  • datetime_end (string, optional): End date/time. Defaults to datetime_start + 1 hour.

  • all_day_event, timezone, recurring_rule, description, internal_name, location, location_id, organizer_name, organizer_email, reminder, color, free_busy, landing_page_template_id, rsvp_enabled, rsvp_form_id, custom_data: optional fields, see each field's description.

Returns: The created event object as JSON, including its event_id and public landing_page_url.

Examples:

  • "Create the Main Monthly meetup for Sept 15 at 6pm at [venue]" -> title, datetime_start, location set.

  • "Make it a recurring event, third Tuesday of every month" -> recurring_rule: "FREQ=MONTHLY;BYDAY=3TU".

  • Don't use when: the event already exists (use addevent_update_event instead).

Error Handling:

  • Returns a clear message if required fields are missing, the calendar_id doesn't exist, or the API rejects the request body (400).

Inputs: title (required), datetime_start (required), color, location, +16 more.

addevent_create_rsvpCreate AddEvent RSVP AttendeeA

Registers an RSVP attendee on an event. Only works on events created with rsvp_enabled: true.

Args:

  • event_id (string, required): The event to RSVP to.

  • email (string, required): Attendee's email. Must be unique per event.

  • attending ('going' | 'maybe' | 'not-going', optional): Default 'going'.

  • notify ('active', optional): Set to send confirmation/notification emails. Omitted by default (silent creation) — useful when backfilling attendees from another system.

  • rsvp_form_data (object, optional): Values for the event's RSVP form. The default form needs { "name": "..." }.

Returns: The created RSVP attendee object as JSON, including its attendee_id.

Examples:

  • "Add jane@example.com as attending the Main Monthly meetup" -> event_id, email set.

  • "Import these 20 signups from our spreadsheet without emailing them" -> omit notify.

  • Don't use when: the event doesn't have RSVP enabled (check with addevent_get_event first).

Error Handling:

  • Returns "Error: Invalid request..." (400) if the email is already registered for this event, or rsvp_form_data is missing a required field.

Inputs: email (required), event_id (required), notify, attending, +1 more.

addevent_delete_calendarDelete AddEvent CalendarA
DestructiveIdempotent

Permanently deletes a calendar. This cannot be undone, and affects any events still on it.

Args:

  • calendar_id (string, required): The calendar to delete.

Returns: A confirmation message.

Examples:

  • Before deleting, consider calling addevent_search_events with this calendar_id to check what's still on it.

Error Handling:

  • Returns "Error: Not found..." (404) if the calendar_id doesn't exist.

Inputs: calendar_id (required).

addevent_delete_eventDelete AddEvent EventA
DestructiveIdempotent

Permanently deletes an event. This cannot be undone.

Args:

  • event_id (string, required): The event to delete.

Returns: A confirmation message.

Examples:

  • "Delete the duplicate event we just created" -> event_id set.

  • Don't use when: you want to hide an event without losing it (there's no archive/unpublish option in this API; deletion is permanent).

Error Handling:

  • Returns "Error: Not found..." (404) if the event_id doesn't exist.

Inputs: event_id (required).

addevent_delete_rsvpDelete AddEvent RSVP AttendeeA
DestructiveIdempotent

Permanently deletes an RSVP attendee. This cannot be undone.

Args:

  • attendee_id (string, required): The RSVP attendee to delete.

Returns: A confirmation message.

Error Handling:

  • Returns "Error: Not found..." (404) if the attendee_id doesn't exist.

Inputs: attendee_id (required).

addevent_get_calendarRetrieve AddEvent CalendarA
Read-onlyIdempotent

Retrieves a single calendar by its calendar_id.

Args:

  • calendar_id (string, required): The calendar to retrieve.

Returns: The full calendar object as JSON.

Error Handling:

  • Returns "Error: Not found..." (404) if the calendar_id doesn't exist.

Inputs: calendar_id (required).

addevent_get_eventRetrieve AddEvent EventA
Read-onlyIdempotent

Retrieves a single event by its event_id.

Args:

  • event_id (string, required): The event to retrieve.

Returns: The full event object as JSON.

Examples:

  • "Show me the details for event evt_abc123" -> event_id: "evt_abc123".

  • Don't use when: you don't have the event_id yet (use addevent_search_events first).

Error Handling:

  • Returns "Error: Not found..." (404) if the event_id doesn't exist.

Inputs: event_id (required).

addevent_get_rsvpRetrieve AddEvent RSVP AttendeeA
Read-onlyIdempotent

Retrieves a single RSVP attendee by attendee_id.

Args:

  • attendee_id (string, required): The RSVP attendee to retrieve.

Returns: The full RSVP attendee object as JSON.

Error Handling:

  • Returns "Error: Not found..." (404) if the attendee_id doesn't exist.

Inputs: attendee_id (required).

addevent_list_timezonesList AddEvent TimezonesA
Read-onlyIdempotent

Lists the timezone values supported by AddEvent's timezone field on events and calendars.

Args:

  • search (string, optional): Filter results to timezone names containing this text.

Returns: { "timezones": [...], "count": number }

Examples:

  • "What timezone value should I use for Salt Lake City?" -> search: "Denver" (Utah shares the America/Denver zone).

  • Use this before addevent_create_event or addevent_create_calendar if you're unsure of the exact timezone string.

Inputs: search.

addevent_search_calendarsSearch AddEvent CalendarsA
Read-onlyIdempotent

Searches calendars you've previously created. Does NOT create or modify calendars.

Args:

  • calendar_ids (string[], optional): Narrow to specific calendar IDs.

  • page (number, default 1), page_size (number, 1-20, default 10): Pagination.

  • sort_by ('created' | 'title'), sort_order ('asc' | 'desc'): Sorting.

Returns: { "calendars": [ ...calendar objects... ], "count": number, "page": number, "page_size": number } An empty "calendars" array means no matches, not an error.

Examples:

  • "What calendars do we have set up?" -> call with no filters to list them all.

  • "Find the calendar_id for the WREIA calendar" -> useful before addevent_create_event.

Error Handling:

  • Returns "Error: Invalid request..." (400) for an invalid sort combination.

Inputs: page, sort_by, page_size, sort_order, +1 more.

addevent_search_eventsSearch AddEvent EventsA
Read-onlyIdempotent

Searches events you've previously created. Does NOT create or modify events.

Args:

  • calendar_ids, event_ids (string[], optional): Narrow to specific calendars or events.

  • datetime_min, datetime_max (string, optional): Filter by date range. datetime_min matches events ending on/after that time; datetime_max matches events starting on/before it.

  • search (string, optional): Free-text match against title, internal_name, description, and location.

  • custom_data_key / custom_data_value (string, optional): Filter by a custom_data key-value pair. Both must be provided together.

  • page (number, default 1), page_size (number, 1-20, default 10): Pagination.

  • sort_by ('created' | 'title' | 'calendar_id' | 'datetime_start'), sort_order ('asc' | 'desc'): Sorting.

Returns: { "events": [ ...event objects... ], "count": number, // events in this response "page": number, "page_size": number } An empty "events" array means no matches, not an error.

Examples:

  • "What events do we have next month?" -> datetime_min/datetime_max set to that month's range.

  • "Find the Main Monthly event" -> search: "Main Monthly".

  • Don't use when: you already have the event_id (use addevent_get_event, it's cheaper).

Error Handling:

  • Returns "Error: Invalid request..." if a filter combination is invalid (e.g. custom_data_key without custom_data_value).

Inputs: page, search, sort_by, event_ids, +7 more.

addevent_search_rsvpsSearch AddEvent RSVP AttendeesA
Read-onlyIdempotent

Searches RSVP attendees you've previously created. Does NOT create or modify RSVPs.

Args:

  • calendar_ids, event_ids (string[], optional): Narrow to attendees of these calendars or events.

  • attending (array of 'going' | 'maybe' | 'not-going', optional): Filter by response.

  • page (number, default 1), page_size (number, 1-20, default 10): Pagination.

  • sort_by ('created' | 'event_id' | 'attending' | 'email'), sort_order ('asc' | 'desc'): Sorting.

Returns: { "rsvps": [ ...attendee objects... ], "count": number, "page": number, "page_size": number } An empty "rsvps" array means no matches, not an error.

Examples:

  • "Who's RSVP'd yes to the Main Monthly meetup?" -> event_ids: [that event's ID], attending: ["going"].

  • "How many people said maybe across all our events this month?" -> attending: ["maybe"], combined with an event_ids or calendar_ids filter.

  • Don't use when: you already have the attendee_id (use addevent_get_rsvp, it's cheaper).

Inputs: page, sort_by, attending, event_ids, +3 more.

addevent_update_calendarUpdate AddEvent CalendarA
Idempotent

Updates an existing calendar. Only the fields you provide are changed; everything else is left as-is.

Args:

  • calendar_id (string, required): The calendar to update.

  • Any other field from addevent_create_calendar is optional here — include only what's changing.

Returns: The updated calendar object as JSON.

Error Handling:

  • Returns "Error: Not found..." (404) if calendar_id doesn't exist.

Inputs: calendar_id (required), title, timezone, custom_data, +6 more.

addevent_update_eventUpdate AddEvent EventA
Idempotent

Updates an existing event. Only the fields you provide are changed; everything else is left as-is.

Args:

  • event_id (string, required): The event to update.

  • Any other field from addevent_create_event (title, datetime_start, datetime_end, location, description, etc.) is optional here — include only what's changing.

Returns: The updated event object as JSON.

Examples:

  • "Move the Main Monthly meetup to 7pm" -> event_id set, datetime_start updated.

  • "Change the location to the new venue" -> event_id set, location updated.

  • Don't use when: the event doesn't exist yet (use addevent_create_event).

Error Handling:

  • Returns "Error: Not found..." (404) if event_id doesn't exist, or "Error: Invalid request..." (400) if a field value fails validation.

Inputs: event_id (required), color, title, location, +17 more.

addevent_update_rsvpUpdate AddEvent RSVP AttendeeA
Idempotent

Updates an existing RSVP attendee. Only the fields you provide are changed; everything else is left as-is.

Args:

  • attendee_id (string, required): The RSVP attendee to update.

  • email, attending, rsvp_form_data: optional — include only what's changing.

Returns: The updated RSVP attendee object as JSON.

Examples:

  • "Mark jane@example.com as not going anymore" -> attendee_id set, attending: "not-going".

Error Handling:

  • Returns "Error: Not found..." (404) if attendee_id doesn't exist.

Inputs: attendee_id (required), email, attending, rsvp_form_data.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.5/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (create/search/get/update/delete for events, calendars, and RSVPs, plus list_timezones). The descriptions include explicit 'Don't use when' guidance to further prevent confusion between similar tools like search_events and get_event.

    Naming Consistency5/5

    All 16 tools follow the exact pattern `addevent_<verb>_<resource>` with verbs restricted to create, search, get, update, delete, and list. This uniform convention makes the tool's purpose immediately predictable from its name.

    Tool Count4/5

    16 tools is at the upper boundary of typical well-scoped server size, but each tool serves a clear CRUD need for one of three related resources (events, calendars, RSVPs) plus a single timezone lookup helper. Given the three independent resource lifecycles, this count is justified and not bloated.

    Completeness5/5

    The tool set provides full create, read/search, update, and delete coverage for events, calendars, and RSVPs, with no obvious dead ends. The timezone listing tool fills the only metadata gap needed to correctly create events and calendars, making the surface complete for its domain.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      B
      quality
      D
      maintenance
      MCP server for Cal.com scheduling, providing ~70 tools to manage schedules, event types, bookings, calendars, webhooks, and teams. Enables natural language control of Cal.com from Claude or any MCP-compatible client.
      68
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for Google Calendar integration with Claude Desktop. Create, update, delete, and manage calendar events with batch operations and enterprise-grade retry mechanisms.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that allows Claude and other MCP clients to interact with Google Calendar. This server enables AI assistants to manage your calendar events, check availability, and handle scheduling tasks.
      MIT