Teamup Calendar MCP by usefulapi
Read and search Teamup Calendar events and sub-calendars; create, update, delete and…
- Runs
- Remotely
- Version
- 1.27.0
- Listing updated
- 4 days ago
About Teamup Calendar MCP by usefulapi
Teamup Calendar MCP by usefulapi is an MCP server for productivity. It runs as a hosted remote server, so there is nothing to install locally.
Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.
Install
Run in a terminal
claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcpAdd to Settings → Connectors → Add custom connector
https://teamup-calendar.usefulapi.io/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"teamup-calendar": {
"url": "https://teamup-calendar.usefulapi.io/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"teamup-calendar": {
"type": "http",
"url": "https://teamup-calendar.usefulapi.io/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"teamup-calendar": {
"serverUrl": "https://teamup-calendar.usefulapi.io/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"teamup-calendar": {
"type": "http",
"url": "https://teamup-calendar.usefulapi.io/mcp"
}
}
}Tools this server provides (15)
Read directly from the server.
- teamup_get_calendar
- 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.
- teamup_list_subcalendars
- 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_get_subcalendar
- 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
- 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_events
- 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_search_events
- 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_get_event
- 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}.
- teamup_list_changed_events
- 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=.
- teamup_list_event_signups
- The people signed up for an event (name, email, id). Signups must be enabled on the event. GET /{calendarKey}/events/{id}/signups.
- teamup_create_event
- 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.
- teamup_update_event
- 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
- teamup_delete_event
- 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 /{calendar
- teamup_undo_event_action
- 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_create_subcalendar
- 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_update_subcalendar
- 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}.
Teamup Calendar MCP by usefulapi FAQ
How do I add Teamup Calendar MCP by usefulapi to Claude Code?
Run this command in your terminal: claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcp
What are the best alternatives to Teamup Calendar MCP by usefulapi?
The closest alternatives to Teamup Calendar MCP by usefulapi are Ha MCP, Concord MCP, note1, CalderFlow and nicemails.
Alternatives to Teamup Calendar MCP by usefulapi

Ha MCP
MCP serverMCP server for managing and automating Home Assistant from AI assistants
Runs locally- 8 tools
- Open source
- 7.9K GitHub stars
- Productivity

Concord MCP
MCP serverLocal-first MCP server for messaging and shared work-state between coding agents
Runs locally- Freemium
- 1.3K GitHub stars
- Developer tools

note1
MCP serverMCP server giving AI assistants search and summaries across your note1 meetings
- 4 tools
- Remote
- Free trial
- 1 GitHub star
- Productivity

CalderFlow
MCP serverTurn notes or specs into editable flowcharts, timelines and funnels from an AI assistant
- 10 tools
- Remote
- Free
- Design and media

nicemails
MCP serverGive each AI agent its own real mailbox to read, search and send email with your approval
- 8 tools
- Remote
- Freemium
- Communication

ConvertAudioToText
MCP serverTranscribe audio and video links from Claude or ChatGPT and read the results
Not checked yet- 5 tools
- Remote
- Freemium
- Design and media