MCP server

Teamup Calendar MCP by usefulapi

io.usefulapi/teamup-calendar

Checked 26 Oct 2026, 08:29 UTC · Connected to it and listed its tools

Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.

Website Source

At a glance

Type

MCP server

Publisher

usefulapi.io (verified by the MCP Registry)

Status

Working at last check

Tools

15

Token cost

About 4,261 tokens per request

Sets up in

Claude Code, Claude Desktop, Codex, Gemini CLI, Cursor, VS Code, Antigravity, ChatGPT, OpenAI API, Grok

Last checked

26 Oct 2026, 08:29 UTC

Connect it to your agent

Add to CursorAdd to VS CodeVS Code Insiders

Opens the app, which shows the server and asks you to confirm. For other apps, copy the setup below.

Claude Code

claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcp

Claude Desktop

Settings → Connectors → Add custom connector, and paste the URL.

Codex (config.toml)

[mcp_servers.teamup-calendar]
url = "https://teamup-calendar.usefulapi.io/mcp"

Gemini CLI

{"mcpServers":{"teamup-calendar":{"httpUrl":"https://teamup-calendar.usefulapi.io/mcp"}}}

Cursor

{"mcpServers":{"teamup-calendar":{"url":"https://teamup-calendar.usefulapi.io/mcp"}}}

VS Code

{"servers":{"teamup-calendar":{"type":"http","url":"https://teamup-calendar.usefulapi.io/mcp"}}}

Antigravity

agy mcp add teamup-calendar https://teamup-calendar.usefulapi.io/mcp

ChatGPT

Settings → Apps & Connectors → Advanced settings: turn on Developer mode, then Create a connector and paste the URL. Which plans can do this varies.

OpenAI API (Responses tools)

{"type":"mcp","server_label":"teamup-calendar","server_url":"https://teamup-calendar.usefulapi.io/mcp","require_approval":"always"}

Grok (xAI API tools)

{"type":"mcp","server_label":"teamup-calendar","server_url":"https://teamup-calendar.usefulapi.io/mcp"}

Tools

• teamup_create_event ~670 tokens
  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 /{cal
• teamup_create_subcalendar ~213 tokens
  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.
• teamup_delete_event Deletes data · ~315 tokens
  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
• teamup_get_calendar ~135 tokens
  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 /{calendarK
• teamup_get_event ~169 tokens
  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}/ev
• teamup_get_subcalendar ~124 tokens
  One sub-calendar by id: name, color, overlap rule, active state and which links may use it. GET /{calendarKey}/subcalendars/{id}.
• teamup_list_access_keys ~274 tokens
  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.
• teamup_list_changed_events ~242 tokens
  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
• teamup_list_event_signups ~120 tokens
  The people signed up for an event (name, email, id). Signups must be enabled on the event. GET /{calendarKey}/events/{id}/signups.
• teamup_list_events ~319 tokens
  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.
• teamup_list_subcalendars ~241 tokens
  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.
• teamup_search_events ~414 tokens
  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=.
• teamup_undo_event_action ~149 tokens
  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}.
• teamup_update_event ~670 tokens
  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 occu
• teamup_update_subcalendar ~206 tokens
  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}.

Browse

• Converting to Markdown
• Email
• Calendars
• To-do lists

Related MCP servers

• Cronofy MCP by usefulapi
  MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.
• AddEvent MCP by usefulapi
  Read AddEvent calendars, events, RSVPs and subscribers; create and update calendars and events.
• CentralStationCRM MCP by usefulapi
  Read CentralStationCRM people, companies, deals, tasks; create and update people, companies, deals.
• TeamUp MCP by usefulapi
  Check classes, attendance, customers, memberships and invoices in TeamUp and register customers.
• Reclaim.ai MCP by usefulapi
  Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits.
• Applystead
  Search open jobs from employers' own career sites: roles, companies and posting status.
• Bookingmood MCP by usefulapi
  Read Bookingmood bookings, availability, guests, payments and invoices; update bookings, contacts.
• Nylas MCP by usefulapi
  MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/io.usefulapi/teamup-calendar.svg)](https://aptlynx.net/servers/io.usefulapi/teamup-calendar)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents