addevent-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRANSPORT | No | Optional transport mode. Set to 'http' to run as an HTTP server (default is stdio). | |
| ADDEVENT_API_KEY | Yes | Your AddEvent API token. Obtain it from dashboard.addevent.com under Settings > API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| addevent_create_eventA | Creates a new event on an AddEvent calendar. Args:
Returns: The created event object as JSON, including its event_id and public landing_page_url. Examples:
Error Handling:
|
| addevent_search_eventsA | Searches events you've previously created. Does NOT create or modify events. Args:
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:
Error Handling:
|
| addevent_get_eventA | Retrieves a single event by its event_id. Args:
Returns: The full event object as JSON. Examples:
Error Handling:
|
| addevent_update_eventA | Updates an existing event. Only the fields you provide are changed; everything else is left as-is. Args:
Returns: The updated event object as JSON. Examples:
Error Handling:
|
| addevent_delete_eventA | Permanently deletes an event. This cannot be undone. Args:
Returns: A confirmation message. Examples:
Error Handling:
|
| addevent_create_calendarA | Creates a new calendar (a container that events live inside). Args:
Returns: The created calendar object as JSON, including its calendar_id. Examples:
Error Handling:
|
| addevent_search_calendarsA | Searches calendars you've previously created. Does NOT create or modify calendars. Args:
Returns: { "calendars": [ ...calendar objects... ], "count": number, "page": number, "page_size": number } An empty "calendars" array means no matches, not an error. Examples:
Error Handling:
|
| addevent_get_calendarA | Retrieves a single calendar by its calendar_id. Args:
Returns: The full calendar object as JSON. Error Handling:
|
| addevent_update_calendarA | Updates an existing calendar. Only the fields you provide are changed; everything else is left as-is. Args:
Returns: The updated calendar object as JSON. Error Handling:
|
| addevent_delete_calendarA | Permanently deletes a calendar. This cannot be undone, and affects any events still on it. Args:
Returns: A confirmation message. Examples:
Error Handling:
|
| addevent_create_rsvpA | Registers an RSVP attendee on an event. Only works on events created with rsvp_enabled: true. Args:
Returns: The created RSVP attendee object as JSON, including its attendee_id. Examples:
Error Handling:
|
| addevent_search_rsvpsA | Searches RSVP attendees you've previously created. Does NOT create or modify RSVPs. Args:
Returns: { "rsvps": [ ...attendee objects... ], "count": number, "page": number, "page_size": number } An empty "rsvps" array means no matches, not an error. Examples:
|
| addevent_get_rsvpA | Retrieves a single RSVP attendee by attendee_id. Args:
Returns: The full RSVP attendee object as JSON. Error Handling:
|
| addevent_update_rsvpA | Updates an existing RSVP attendee. Only the fields you provide are changed; everything else is left as-is. Args:
Returns: The updated RSVP attendee object as JSON. Examples:
Error Handling:
|
| addevent_delete_rsvpA | Permanently deletes an RSVP attendee. This cannot be undone. Args:
Returns: A confirmation message. Error Handling:
|
| addevent_list_timezonesA | Lists the timezone values supported by AddEvent's timezone field on events and calendars. Args:
Returns: { "timezones": [...], "count": number } Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
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.
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.
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.
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.