Teamup Calendar MCP by usefulapi MCP Server

by usefulapi Your server? Claim it

answering

Teamup Calendar MCP by usefulapi is answering right now. Last checked 13 min ago. It exposes 15 tools. Last commit 13 Oct 2026.

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

Uptime history 4 days of history

4 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

147 ms

Response time

average over 24h

Stars

last commit 13 Oct 2026

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 13 October 2026. No other catalogue keeps this.

13 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check Teamup Calendar MCP by usefulapi every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

teamup

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_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_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 /{calendarKey}/events/{id}.

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_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_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_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_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_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_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_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_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 the event and an undo_id for one hour (teamup_undo_event_action). PUT /{calendarKey}/events/{id}.

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}.

Endpoints

URL	Transport	State	Latency	Checked
https://teamup-calendar.usefulapi.io/mcp	streamable-http	answering	207 ms	13 min ago

Alternatives to Teamup Calendar MCP by usefulapi

same job, measured the same way

Cronofy MCP by usefulapi

by usefulapi

MCP server for Cronofy — read calendars, events and free/busy, and create, update or delete events.

8 tools answering

AddEvent MCP by usefulapi

by usefulapi

Read AddEvent calendars, events, RSVPs and subscribers; create and update calendars and events.

18 tools answering

Nylas MCP by usefulapi

by usefulapi

MCP server for Nylas — read email, calendars, events and contacts, and send email or create events.

15 tools answering

Linear MCP by usefulapi

by usefulapi

Search, read and create Linear issues, projects, teams and cycles.

8 tools answering

Reclaim.ai MCP by usefulapi

by usefulapi

Read tasks, habits, events and scheduling links; create and update Reclaim tasks and habits.

15 tools answering

Aircall MCP by usefulapi

by usefulapi

Read calls, contacts, users, teams and numbers; tag calls and create or update contacts.

25 tools answering

SavvyCal MCP by usefulapi

by usefulapi

Read and create SavvyCal scheduling links and booked events.

8 tools answering

Apple Calendar

by jonathanrreed

List, create, update, and delete events in Apple Calendar on macOS.

1 712 installs/wk local only

Teamup Calendar MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Teamup Calendar MCP by usefulapi do?

It exposes 15 tools, read directly from the server on our last check. Among them: teamup_create_event, teamup_create_subcalendar, teamup_delete_event, teamup_get_calendar, teamup_get_event, teamup_get_subcalendar and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Teamup Calendar MCP by usefulapi working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 147 ms. The bar chart above shows every period we have measured.

How do I connect Teamup Calendar MCP by usefulapi?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Teamup Calendar MCP by usefulapi need an API key?

No. Teamup Calendar MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Teamup Calendar MCP by usefulapi?

It answers our handshake in 147 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Teamup Calendar MCP by usefulapi open source?

Yes — it is published under the MIT licence, written in JavaScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.