Integration

Teamup Calendar integration

Teamup is a shared calendar for groups. Read and search a calendar's events in a date range, create, update, delete and undo events, read and manage sub-calendars, read the calendar configuration, post and edit event comments, manage event sign-ups and reminder settings, and duplicate a calendar. Every call names a calendar by its calendar key (the key from a calendar link), whose access rights decide what is allowed. Login tokens, access-key management, attachment uploads (the upload URL comes back only in a response header), iCalendar exports and legacy reminder routes are not exposed. Authentication is a Teamup API key sent in the Teamup-Token header.

Connect Teamup Calendar How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Teamup Calendar.Built from the 29 Teamup Calendar tools below, on the connection you add once.

What you can do with Teamup Calendar

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.

Subcalendar, 6 operations

create_subcalendarCreate subcalendarPOSTCreate a sub-calendar with a name and optional color id, active and overlap flags, type and feed settings. Returns the new sub-calendar with its id.
delete_subcalendarDelete subcalendarDELETEDelete a sub-calendar by its id, as returned by list_subcalendars.
get_subcalendarGet subcalendarGETGet one sub-calendar by its id with all its details (name, color, active, overlap, type, feed settings).
list_subcalendarsList subcalendarsGETList the sub-calendars of a calendar (id, name, color, active, overlap), optionally including inactive ones, filtered by name or paged with offset and limit.
replace_subcalendarReplace subcalendarPUTReplace a sub-calendar's settings (name is required). Differs from update_subcalendar, which changes only the fields sent.
update_subcalendarUpdate subcalendarPATCHChange some fields of a sub-calendar (name, color, active, overlap, type, feed). Fields left out keep their current value. replace_subcalendar replaces the whole sub-calendar instead.

Event, 5 operations

create_eventCreate eventPOSTCreate an event from start_dt and end_dt, assigned to sub-calendars (ids from list_subcalendars), with optional title, location, who, notes, all-day flag, recurrence rule, signups and comments settings.
delete_eventDelete eventDELETEDelete an event. For a recurring event, redit chooses single (this instance), future or all instances. The response carries an undo id usable with undo_event_action.
get_eventGet eventGETGet one event by eventId: title, times, sub-calendars, location, who, notes, recurrence rule, signup and comment settings, custom fields and version.
list_eventsList eventsGETList a calendar's events in a date range (startDate to endDate, YYYY-MM-DD, default today), optionally only some sub-calendars. Recurring events are expanded into their instances.
update_eventUpdate eventPUTUpdate an event. Send id (same as eventId), start_dt, end_dt and subcalendar_ids every time: get_event first to resend current values. version enables soft-locking against concurrent edits.

Signup, 4 operations

create_event_signupCreate event signupPOSTSign someone up for an event (name and email required). The event must have signups enabled.
delete_event_signupDelete event signupDELETERemove a signup from an event by its signup id.
list_event_signupsList event signupsGETList the signups (name, email) of an event that has signups enabled.
update_event_signupUpdate event signupPUTChange the name, email or remote id of an existing event signup.

Comment, 3 operations

create_event_commentCreate event commentPOSTPost a comment on an event (message, with optional author name and email). The event must have comments enabled.
delete_event_commentDelete event commentDELETEDelete a comment from an event by its comment id.
update_event_commentUpdate event commentPUTEdit an existing event comment's message, author name or email.

Reminder, 3 operations

get_subcalendar_default_remindersGet subcalendar default remindersGETGet the current user's default reminder subscriptions for one sub-calendar.
list_default_remindersList default remindersGETList the current user's default reminder subscriptions for every sub-calendar the calendar key can access.
update_subcalendar_default_remindersUpdate subcalendar default remindersPUTReplace the current user's default reminder subscriptions for one sub-calendar with the list sent in items.

Aux, 1 operation

get_event_auxGet event auxGETGet an event's auxiliary information: change history, comments, signups and reminders. Use it to find comment and signup ids.

Configuration, 1 operation

get_calendar_configurationGet calendar configurationGETGet a calendar's configuration: its sub-calendars with ids, custom fields, general settings and the access rights of the calendar key used.

Copy, 1 operation

copy_calendarCopy calendarPOSTDuplicate a calendar with its sub-calendars and configuration (events are not copied). Optional title, copyConfiguration and copySubcalendars control what is copied.

Events modified since modified since, 1 operation

list_changed_eventsList changed eventsGETList every event created, updated or deleted since a UNIX timestamp (at most 30 days back), deleted ones with delete_dt set. Reuse the returned timestamp as the next modifiedSince.

Events query query, 1 operation

search_eventsSearch eventsGETSearch a calendar's events by keywords (2 to 100 characters) within a date range, optionally per sub-calendar, with offset and limit paging. Recurring events are expanded into instances.

Pointer, 1 operation

get_event_page_urlGet event page urlPOSTGet the URL of an event's own web page, which can be shared with people who have no access to the calendar.

Reminder subscription, 1 operation

set_event_remindersSet event remindersPUTReplace the current user's reminder subscriptions for one event with the list sent in items, overriding the sub-calendar defaults.

Undo, 1 operation

undo_event_actionUndo event actionPUTUndo a recent event creation, update or deletion, using the undo id returned by that call.

Use Teamup Calendar from Claude Code, Cursor or Codex

Connect Teamup Calendar in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Teamup Calendar 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 Teamup Calendar

Create your workspace
Sign up free. Nothing to install.
Connect Teamup Calendar once
Add your Teamup Calendar connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
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.