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. |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/UtahREIA/addevent-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server