Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
WRITE: create an event. Needs a calendar key with add or modify permission. Give at least subcalendar_ids, start and end. Not idempotent: a repeated call creates a second event. The reply holds the new event and an undo_id; teamup_undo_event_action removes the event again within one hour. POST /{calendarKey}/events.
End, same format as start. Must not be before start.
Start, e.g. 2026-10-14T09:00:00 (calendar timezone) or with an offset such as +02:00. For an all-day event: yyyy-mm-dd.
Sub-calendar ids the event belongs to (from teamup_list_subcalendars).
The "who" field.
Notes, in markdown.
Recurrence rule (iCalendar RRULE, e.g. FREQ=WEEKLY;COUNT=10). Omit for a single event.
Event title.
Values of custom fields, keyed by field id (see teamup_get_calendar -> fields).
True for an all-day event (default false).
Maximum signups; required by Teamup when signup_enabled is true.
Let people sign up (default false).
Allow comments (default false).
Who sees the signups: all_users or users_with_modify_permission.
Who sees the comments: all_users or users_with_modify_permission.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
WRITE: create an event. Needs a calendar key with add or modify permission. Give at least subcalendar_ids, start and end. Not idempotent: a repeated call creates a second event. The reply holds the new event and an undo_id; teamup_undo_event_action removes the event again within one hour. POST /{calendarKey}/events.
| Argument | Type | Description |
|---|---|---|
| end* | string | End, same format as start. Must not be before start. |
| who | string | The "who" field. |
| notes | string | Notes, in markdown. |
| rrule | string | Recurrence rule (iCalendar RRULE, e.g. FREQ=WEEKLY;COUNT=10). Omit for a single event. |
| start* | string | Start, e.g. 2026-10-14T09:00:00 (calendar timezone) or with an offset such as +02:00. For an all-day event: yyyy-mm-dd. |
| title | string | Event title. |
| custom | object | Values of custom fields, keyed by field id (see teamup_get_calendar -> fields). |
| all_day | boolean | True for an all-day event (default false). |
| location | string | |
| signup_limit | integer | Maximum signups; required by Teamup when signup_enabled is true. |
| signup_enabled | boolean | Let people sign up (default false). |
| subcalendar_ids* | array | Sub-calendar ids the event belongs to (from teamup_list_subcalendars). |
| comments_enabled | boolean | Allow comments (default false). |
| signup_visibility | string | Who sees the signups: all_users or users_with_modify_permission. |
| comments_visibility | string | Who sees the comments: all_users or users_with_modify_permission. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"subcalendar_ids",
"start",
"end"
],
"properties": {
"end": {
"type": "string",
"description": "End, same format as start. Must not be before start."
},
"who": {
"type": "string",
"maxLength": 255,
"description": "The \"who\" field."
},
"notes": {
"type": "string",
"maxLength": 65535,
"description": "Notes, in markdown."
},
"rrule": {
"type": "string",
"maxLength": 500,
"description": "Recurrence rule (iCalendar RRULE, e.g. FREQ=WEEKLY;COUNT=10). Omit for a single event."
},
"start": {
"type": "string",
"description": "Start, e.g. 2026-10-14T09:00:00 (calendar timezone) or with an offset such as +02:00. For an all-day event: yyyy-mm-dd."
},
"title": {
"type": "string",
"maxLength": 1024,
"description": "Event title."
},
"custom": {
"type": "object",
"description": "Values of custom fields, keyed by field id (see teamup_get_calendar -> fields).",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"all_day": {
"type": "boolean",
"description": "True for an all-day event (default false)."
},
"location": {
"type": "string",
"maxLength": 255
},
"signup_limit": {
"type": "integer",
"maximum": 100000,
"minimum": 0,
"description": "Maximum signups; required by Teamup when signup_enabled is true."
},
"signup_enabled": {
"type": "boolean",
"description": "Let people sign up (default false)."
},
"subcalendar_ids": {
"type": "array",
"items": {
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
"maxItems": 100,
"minItems": 1,
"description": "Sub-calendar ids the event belongs to (from teamup_list_subcalendars)."
},
"comments_enabled": {
"type": "boolean",
"description": "Allow comments (default false)."
},
"signup_visibility": {
"enum": [
"all_users",
"users_with_modify_permission"
],
"type": "string",
"description": "Who sees the signups: all_users or users_with_modify_permission."
},
"comments_visibility": {
"enum": [
"all_users",
"users_with_modify_permission"
],
"type": "string",
"description": "Who sees the comments: all_users or users_with_modify_permission."
}
}
}WRITE: create a sub-calendar. Needs a calendar key with admin permission, and the plan may limit how many exist. Not idempotent: a repeated call creates a second one. POST /{calendarKey}/subcalendars.
| Argument | Type | Description |
|---|---|---|
| name* | string | Sub-calendar name. |
| color | integer | Color number from Teamup's palette (default 17). |
| active | boolean | Active (default true). |
| overlap | boolean | Allow overlapping events on it (default true). |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 255,
"minLength": 1,
"description": "Sub-calendar name."
},
"color": {
"type": "integer",
"maximum": 48,
"minimum": 1,
"description": "Color number from Teamup's palette (default 17)."
},
"active": {
"type": "boolean",
"description": "Active (default true)."
},
"overlap": {
"type": "boolean",
"description": "Allow overlapping events on it (default true)."
}
}
}WRITE, DESTRUCTIVE: delete an event, or for a recurring event the chosen occurrences. Needs modify permission. Not retried. The reply holds an undo_id; teamup_undo_event_action restores the event within one hour, after that the deletion is permanent. For one occurrence use the occurrence id (123-rid-<unix start>) and redit single (the default); redit all deletes the whole series. DELETE /{calendarKey}/events/{id}.
| Argument | Type | Description |
|---|---|---|
| redit | string | For a recurring event: single (default), future or all. With all the whole series is deleted. |
| version | string | The event's version (from teamup_get_event). If set, the delete is refused when the event changed since. |
| event_id* | string | Event id (occurrence id for one occurrence of a recurring event). |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"event_id"
],
"properties": {
"redit": {
"enum": [
"single",
"future",
"all"
],
"type": "string",
"description": "For a recurring event: single (default), future or all. With all the whole series is deleted."
},
"version": {
"type": "string",
"maxLength": 12,
"minLength": 1,
"description": "The event's version (from teamup_get_event). If set, the delete is refused when the event changed since."
},
"event_id": {
"type": "string",
"pattern": "^[1-9]\\d{0,17}(-rid-[1-9]\\d{0,12})?$",
"description": "Event id (occurrence id for one occurrence of a recurring event)."
}
}
}The calendar this connection points at: title, timezone and date settings, custom event fields, sub-calendars, the permission of the calendar key in use and the plan's features. Call this first to learn the sub-calendar ids and the timezone. The calendar key itself is never returned. GET /{calendarKey}/configuration.
No arguments.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {}
}One event by id: title, times, sub-calendars, location, who, notes (markdown), recurrence rule, custom fields, signups, comments, attachments (metadata), version, change history and reminders. Use the occurrence id (123-rid-<unix start>) for one occurrence of a recurring event. GET /{calendarKey}/events/{id}.
| Argument | Type | Description |
|---|---|---|
| event_id* | string | Event id. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"event_id"
],
"properties": {
"event_id": {
"type": "string",
"pattern": "^[1-9]\\d{0,17}(-rid-[1-9]\\d{0,12})?$",
"description": "Event id."
}
}
}One sub-calendar by id: name, color, overlap rule, active state and which links may use it. GET /{calendarKey}/subcalendars/{id}.
| Argument | Type | Description |
|---|---|---|
| subcalendar_id* | integer | Sub-calendar id. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"subcalendar_id"
],
"properties": {
"subcalendar_id": {
"type": "integer",
"maximum": 9007199254740991,
"description": "Sub-calendar id.",
"exclusiveMinimum": 0
}
}
}List the calendar's access keys (sharing links and user accesses) with name, role, active state and per-sub-calendar permission. Needs a key with admin permission. The secret key values are never returned (they are secrets); use the id and name to tell links apart. GET /{calendarKey}/keys.
| Argument | Type | Description |
|---|---|---|
| type | string | Only this kind of access. |
| limit | integer | Results per page, 1-200 (default 50). |
| offset | integer | Number of results to skip (default 0). Pass the previous reply's next_offset. |
| name_contains | string | Only keys whose link, user or group name matches this text. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"type": {
"enum": [
"anonymous",
"user",
"group"
],
"type": "string",
"description": "Only this kind of access."
},
"limit": {
"type": "integer",
"maximum": 200,
"description": "Results per page, 1-200 (default 50).",
"exclusiveMinimum": 0
},
"offset": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Number of results to skip (default 0). Pass the previous reply's next_offset."
},
"name_contains": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Only keys whose link, user or group name matches this text."
}
}
}Events created, changed or deleted since a Unix timestamp (at most 30 days back), for syncing. A recurring event comes back once, as its series, not as occurrences. Deleted events carry delete_dt. Pass the reply's timestamp as since_timestamp next time so nothing is missed. GET /{calendarKey}/events?modifiedSince=.
| Argument | Type | Description |
|---|---|---|
| mode | string | synchronize (default): events created and deleted after the timestamp are left out. monitor: they are returned too. |
| since_timestamp* | integer | Unix timestamp in seconds, at most 30 days in the past. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"since_timestamp"
],
"properties": {
"mode": {
"enum": [
"synchronize",
"monitor"
],
"type": "string",
"description": "synchronize (default): events created and deleted after the timestamp are left out. monitor: they are returned too."
},
"since_timestamp": {
"type": "integer",
"maximum": 4102444800,
"description": "Unix timestamp in seconds, at most 30 days in the past.",
"exclusiveMinimum": 0
}
}
}The people signed up for an event (name, email, id). Signups must be enabled on the event. GET /{calendarKey}/events/{id}/signups.
| Argument | Type | Description |
|---|---|---|
| event_id* | string | Event id. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"event_id"
],
"properties": {
"event_id": {
"type": "string",
"pattern": "^[1-9]\\d{0,17}(-rid-[1-9]\\d{0,12})?$",
"description": "Event id."
}
}
}List the events in a date range, optionally only on some sub-calendars. Recurring events are expanded: every occurrence in the range is returned with its own id (series id + -rid- + start). Notes come as markdown. Times use the calendar's timezone unless tz is set. GET /{calendarKey}/events.
| Argument | Type | Description |
|---|---|---|
| tz | string | Timezone for the times in the reply, e.g. Europe/Berlin. Default: the calendar's timezone. |
| end_date | string | Last day, inclusive, yyyy-mm-dd (default: start_date). Needs start_date; at most 366 days after it. |
| start_date | string | First day, yyyy-mm-dd (default: today). |
| subcalendar_ids | array | Only events on these sub-calendars. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"tz": {
"type": "string",
"pattern": "^[A-Za-z0-9_+\\-/]{1,64}$",
"description": "Timezone for the times in the reply, e.g. Europe/Berlin. Default: the calendar's timezone."
},
"end_date": {
"type": "string",
"pattern": "^(\\d{4})-(\\d{2})-(\\d{2})$",
"description": "Last day, inclusive, yyyy-mm-dd (default: start_date). Needs start_date; at most 366 days after it."
},
"start_date": {
"type": "string",
"pattern": "^(\\d{4})-(\\d{2})-(\\d{2})$",
"description": "First day, yyyy-mm-dd (default: today)."
},
"subcalendar_ids": {
"type": "array",
"items": {
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
"maxItems": 100,
"minItems": 1,
"description": "Only events on these sub-calendars."
}
}
}List the sub-calendars (the colored lanes that events belong to, such as people, rooms or resources). A key with admin permission also sees inactive ones. GET /{calendarKey}/subcalendars.
| Argument | Type | Description |
|---|---|---|
| limit | integer | Results per page, 1-200 (default 50). |
| offset | integer | Number of results to skip (default 0). Pass the previous reply's next_offset. |
| name_contains | string | Only sub-calendars whose name matches this text. |
| include_inactive | boolean | Include inactive sub-calendars (default false). |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"limit": {
"type": "integer",
"maximum": 200,
"description": "Results per page, 1-200 (default 50).",
"exclusiveMinimum": 0
},
"offset": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Number of results to skip (default 0). Pass the previous reply's next_offset."
},
"name_contains": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Only sub-calendars whose name matches this text."
},
"include_inactive": {
"type": "boolean",
"description": "Include inactive sub-calendars (default false)."
}
}
}Search events by keyword (2-100 characters) within a date range (default: today only, so always pass the range you mean). Recurring events are expanded. Paged with limit and offset. GET /{calendarKey}/events?query=.
| Argument | Type | Description |
|---|---|---|
| tz | string | Timezone for the times in the reply, e.g. Europe/Berlin. Default: the calendar's timezone. |
| limit | integer | Results per page, 1-200 (default 50). |
| query* | string | Search text (Teamup's search syntax applies). |
| offset | integer | Number of results to skip (default 0). Pass the previous reply's next_offset. |
| end_date | string | Last day, inclusive, yyyy-mm-dd (default: start_date). Needs start_date; at most 366 days after it. |
| start_date | string | First day, yyyy-mm-dd (default: today). |
| subcalendar_ids | array | Only events on these sub-calendars. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"query"
],
"properties": {
"tz": {
"type": "string",
"pattern": "^[A-Za-z0-9_+\\-/]{1,64}$",
"description": "Timezone for the times in the reply, e.g. Europe/Berlin. Default: the calendar's timezone."
},
"limit": {
"type": "integer",
"maximum": 200,
"description": "Results per page, 1-200 (default 50).",
"exclusiveMinimum": 0
},
"query": {
"type": "string",
"maxLength": 100,
"minLength": 2,
"description": "Search text (Teamup's search syntax applies)."
},
"offset": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Number of results to skip (default 0). Pass the previous reply's next_offset."
},
"end_date": {
"type": "string",
"pattern": "^(\\d{4})-(\\d{2})-(\\d{2})$",
"description": "Last day, inclusive, yyyy-mm-dd (default: start_date). Needs start_date; at most 366 days after it."
},
"start_date": {
"type": "string",
"pattern": "^(\\d{4})-(\\d{2})-(\\d{2})$",
"description": "First day, yyyy-mm-dd (default: today)."
},
"subcalendar_ids": {
"type": "array",
"items": {
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
"maxItems": 100,
"minItems": 1,
"description": "Only events on these sub-calendars."
}
}
}WRITE: undo a recent event creation, update or deletion with the undo_id from that call. Works for one hour only and is refused if someone else changed the event since. PUT /{calendarKey}/events/undo/{undo_id}.
| Argument | Type | Description |
|---|---|---|
| undo_id* | string | The undo_id returned by create, update or delete. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"undo_id"
],
"properties": {
"undo_id": {
"type": "string",
"pattern": "^[A-Za-z0-9_.~-]{1,200}$",
"description": "The undo_id returned by create, update or delete."
}
}
}WRITE: change fields of an event; fields you leave out keep their value (the event is read first and sent back with its version, so a concurrent edit is refused instead of overwritten; an event without a version is not changed). Needs modify permission. For a recurring event pass redit; use the occurrence id (123-rid-<unix start>) with single or future. Attachments are not touched. The reply holds the event and an undo_id for one hour (teamup_undo_event_action). PUT /{calendarKey}/events/{id}.
| Argument | Type | Description |
|---|---|---|
| end | string | New end. |
| who | string | |
| notes | string | New notes, in markdown. Replaces the old notes. |
| redit | string | Which occurrences of a recurring event: single (only this one), future (this and all later ones) or all. |
| rrule | string | New recurrence rule; with redit all or future only. An empty string removes the recurrence (the series becomes a single event). |
| start | string | New start (same formats as in teamup_create_event). |
| title | string | |
| custom | object |
WRITE: change a sub-calendar's name, color, overlap rule or active state; fields you leave out keep their value. Needs admin permission. Making a sub-calendar inactive hides it from users without admin rights. PATCH /{calendarKey}/subcalendars/{id}.
| Argument | Type | Description |
|---|---|---|
| name | string | |
| color | integer | |
| active | boolean | |
| overlap | boolean | |
| subcalendar_id* | integer | Sub-calendar id. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"subcalendar_id"
],
"properties": {
"name": {
"type": "string",
"maxLength": 255,
"minLength": 1
},
"color": {
"type": "integer",
"maximum": 48,
"minimum": 1
},
"active": {
"type": "boolean"
},
"overlap": {
"type": "boolean"
},
"subcalendar_id": {
"type": "integer",
"maximum": 9007199254740991,
"description": "Sub-calendar id.",
"exclusiveMinimum": 0
}
}
}| Custom field values to set, keyed by field id; other custom fields keep their value. |
| all_day | boolean |
| event_id* | string | Event id (occurrence id for one occurrence of a recurring event). |
| location | string |
| signup_limit | integer |
| signup_enabled | boolean |
| subcalendar_ids | array | Sub-calendar ids the event belongs to (from teamup_list_subcalendars). |
| comments_enabled | boolean |
| signup_visibility | string |
| comments_visibility | string |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"event_id"
],
"properties": {
"end": {
"type": "string",
"description": "New end."
},
"who": {
"type": "string",
"maxLength": 255
},
"notes": {
"type": "string",
"maxLength": 65535,
"description": "New notes, in markdown. Replaces the old notes."
},
"redit": {
"enum": [
"single",
"future",
"all"
],
"type": "string",
"description": "Which occurrences of a recurring event: single (only this one), future (this and all later ones) or all."
},
"rrule": {
"type": "string",
"maxLength": 500,
"description": "New recurrence rule; with redit all or future only. An empty string removes the recurrence (the series becomes a single event)."
},
"start": {
"type": "string",
"description": "New start (same formats as in teamup_create_event)."
},
"title": {
"type": "string",
"maxLength": 1024
},
"custom": {
"type": "object",
"description": "Custom field values to set, keyed by field id; other custom fields keep their value.",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
},
"all_day": {
"type": "boolean"
},
"event_id": {
"type": "string",
"pattern": "^[1-9]\\d{0,17}(-rid-[1-9]\\d{0,12})?$",
"description": "Event id (occurrence id for one occurrence of a recurring event)."
},
"location": {
"type": "string",
"maxLength": 255
},
"signup_limit": {
"type": "integer",
"maximum": 100000,
"minimum": 0
},
"signup_enabled": {
"type": "boolean"
},
"subcalendar_ids": {
"type": "array",
"items": {
"type": "integer",
"maximum": 9007199254740991,
"exclusiveMinimum": 0
},
"maxItems": 100,
"minItems": 1,
"description": "Sub-calendar ids the event belongs to (from teamup_list_subcalendars)."
},
"comments_enabled": {
"type": "boolean"
},
"signup_visibility": {
"enum": [
"all_users",
"users_with_modify_permission"
],
"type": "string"
},
"comments_visibility": {
"enum": [
"all_users",
"users_with_modify_permission"
],
"type": "string"
}
}
}