Integration

Add to Calendar PRO integration

Add to Calendar PRO hosts "add to calendar" buttons, event landing pages and RSVP forms. Create, read, update and delete events (single, multi-date or recurring) and the groups they belong to, plus the RSVP, call to action and landing page templates and the button styles events use; read RSVP answers, an event's ics file content, custom domains and email templates; read an event's tracked landing page views, calendar saves and RSVP attendance; and manage webhooks. The polling "latest" routes of groups, styles and templates (no documented answer) are not exposed. Authentication is an API key from the organization settings, sent as it is in the Authorization header (keys can be read-only or read and write).

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Add to Calendar PRO.Built from the 47 Add to Calendar PRO tools below, on the connection you add once.

What you can do with Add to Calendar PRO

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

All, 8 operations

  • list_cta_templatesList cta templatesGETLists the call to action templates, with their ids for an event's or group's cta_block.
  • list_email_templatesList email templatesGETLists the email templates with their id, name and type, for the email_rsvp_* fields of RSVP templates.
  • list_eventsList eventsGETLists the events (id, ProKey and label), at most 800 per page; filter by time window and group, and add each event's dates with dates=true.
  • list_groupsList groupsGETLists the event groups, at most 800 per page; each group's ProKey is used by get_group, list_events and create_event.
  • list_landing_page_templatesList landing page templatesGETLists the landing page templates, with their ids for an event's or group's landingpage.
  • list_rsvp_templatesList rsvp templatesGETLists the RSVP templates (the form blocks events use for sign-ups), with their ids for an event's rsvp_block.
  • list_stylesList stylesGETLists the styles (button layouts), with their ids for an event's or group's layout.
  • list_webhooksList webhooksGETLists the webhooks with their ids.

Cta block, 4 operations

  • create_cta_templateCreate cta templatePOSTCreates a call to action template (name and type required; type none, text, link, share or form). Returns its id for cta_block.
  • delete_cta_templateDelete cta templateDELETEDeletes a call to action template; events and groups using it stay active without their call to action.
  • get_cta_templateGet cta templateGETReturns one call to action template, its type, headline, text, form fields, URL and button label.
  • update_cta_templateUpdate cta templatePATCHUpdates a call to action template; only the fields sent change, a field set to null is cleared, and fields replaces the whole form.

Event, 4 operations

  • create_eventCreate eventPOSTCreates an event in a group (event_group) or a new group (new_event_group_name) with at least one date; it is published at once. Returns its ProKey; its landing page is https://caldn.net/<prokey>.
  • delete_eventDelete eventDELETEDeletes an event permanently by its ProKey.
  • get_eventGet eventGETReturns everything about one event by its ProKey, its dates, recurrence, templates in use, RSVP and call to action settings, group and timestamps.
  • update_eventUpdate eventPATCHUpdates an event; only the fields sent change and a field set to null is cleared. Every 5th update uses one event credit. event_group cannot be changed.

Group, 4 operations

  • create_groupCreate groupPOSTCreates an event group (name required); events are linked to it when they are created. Returns the group's ProKey.
  • delete_groupDelete groupDELETEDeletes a group by ProKey together with all of its events.
  • get_groupGet groupGETReturns one event group by ProKey, its name, status, calendar subscription settings, templates in use and the ProKeys of its events.
  • update_groupUpdate groupPATCHUpdates a group; only the fields sent change and a field set to null is cleared. Switching to subscription children is refused when an event of the group uses RSVP or non-literal dates.

Landingpage, 4 operations

  • create_landing_page_templateCreate landing page templatePOSTCreates a landing page template (name required) with title, texts, colors, background and meta overrides. Returns its id for landingpage.
  • delete_landing_page_templateDelete landing page templateDELETEDeletes a landing page template; events and groups using it fall back to the default landing page.
  • get_landing_page_templateGet landing page templateGETReturns one landing page template, its title, texts, colors, background, images, meta overrides and custom domain.
  • update_landing_page_templateUpdate landing page templatePATCHUpdates a landing page template; only the fields sent change and a field set to null is cleared.

Rsvp block, 4 operations

  • create_rsvp_templateCreate rsvp templatePOSTCreates an RSVP template (name required) with seat limits, options, texts, form fields and email templates. Returns its id for an event's rsvp_block.
  • delete_rsvp_templateDelete rsvp templateDELETEDeletes an RSVP template; events using it stay active but become regular Add to Calendar buttons.
  • get_rsvp_templateGet rsvp templateGETReturns one RSVP template, its seat limits, expiry, options, headline, text, form fields and the email templates it uses.
  • update_rsvp_templateUpdate rsvp templatePATCHUpdates an RSVP template; only the fields sent change, a field set to null is cleared, and fields replaces the whole form.

Style, 4 operations

  • create_styleCreate stylePOSTCreates a style (button layout); name and options (the calendars offered) are required. Returns its id for an event's or group's layout.
  • delete_styleDelete styleDELETEDeletes a style; events and groups using it fall back to the default style.
  • get_styleGet styleGETReturns one style (button layout), its calendar options, button and list style, theme, language, size and behavior settings.
  • update_styleUpdate stylePATCHUpdates a style; only the fields sent change and a field set to null is cleared.

Webhook, 4 operations

  • create_webhookCreate webhookPOSTCreates a webhook that calls payload_url when an element (RSVP answer, event, group, style or template) is created, updated or deleted. Only prokey_filter, header and body are optional.
  • delete_webhookDelete webhookDELETEDeletes a webhook; it stops firing at once.
  • get_webhookGet webhookGETReturns one webhook, its name, active flag, method, target URL, trigger, element and ProKey filter, and when it last fired.
  • update_webhookUpdate webhookPATCHUpdates a webhook; only the fields sent change and a field set to null is cleared.

Latest, 3 operations

  • get_latest_eventGet latest eventGETReturns the most recently created event (id, ProKey and label; its dates too with dates=true).
  • get_latest_rsvp_answerGet latest rsvp answerGETReturns the most recent RSVP answer across all events.
  • get_latest_rsvp_answer_of_eventGet latest rsvp answer of eventGETReturns the most recent RSVP answer of one event.

Custom domain, 1 operation

  • list_custom_domainsList custom domainsGETLists the custom domains set up for landing pages and RSVP forms, with their status, fallback URL and DNS settings, and the default one.

Email template, 1 operation

  • list_email_templates_of_typeList email templates of typeGETLists the email templates of one type with their id and name.

Ic, 1 operation

  • get_ics_dataGet ics dataGETReturns the ics file content of an event, so you can build the file yourself, with its name and, unless the event has dynamic dates, the URL of the hosted ics file.

Rsvp, 1 operation

  • get_event_rsvp_statisticsGet event rsvp statisticsGETReturns the current RSVP attendance of an event, entries and people by status, pending ones, and capacity with remaining seats. Answers 404 for a non-RSVP event.

Rsvp answer, 1 operation

  • list_rsvp_answersList rsvp answersGETLists the RSVP answers (sign-ups) of an event, at most 2,000 per page, with status, email, number of seats and the form values.

Save, 1 operation

  • get_event_savesGet event savesGETCounts tracked clicks on an event's calendar options (saves started) over a UTC window, as a total and a series, optionally broken down by calendar type.

Upload image, 1 operation

  • upload_landing_page_imageUpload landing page imagePOSTUploads one image (webp, gif, png or jpeg, at most 1,048,570 bytes) for landing pages and returns its id for header_image or image. Needs a Read & Write key.

View, 1 operation

  • get_event_viewsGet event viewsGETCounts tracked visits to an event's landing page over a UTC window, as a total and a daily or monthly series, optionally broken down by country, referrer or UTM field.

Use Add to Calendar PRO from Claude Code, Cursor or Codex

Connect Add to Calendar PRO in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Add to Calendar PRO operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Add to Calendar PRO

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Add to Calendar PRO once

    Add your Add to Calendar PRO connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Add to Calendar PRO integration FAQ

What can you do with the Add to Calendar PRO integration?

LiveContext exposes 47 operations on Add to Calendar PRO, covering all, cta block, event and group.

Popular integrations

Browse the whole catalog