io.usefulapi由 usefulapi.io 發布官方發布者v1.23.3更新於 Nov 7, 2026
Read and search Teamup Calendar events and sub-calendars; create, update, delete and undo events.
發布方自己的服務：Ably MCP by usefulapi
託管式 Teamup Calendar MCP 伺服器：讓 AI 助理讀取、搜尋並管理共用行事曆的事件、子行事曆與報名資訊。
Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.usefulapi%2Fteamup-calendar/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"teamup-calendar-by-usefulapi": {
"type": "http",
"url": "https://teamup-calendar.usefulapi.io/mcp"
}
}
}Use Teamup Calendar from Claude, Cursor, or any MCP client — calendar configuration, sub-calendars and access keys, list, search and read events (also changes since a time and signups), and create, update, delete and undo events and create or edit sub-calendars. Hosted, no local install: connect with your own Teamup Calendar credentials.
Live endpoint: https://teamup-calendar.usefulapi.io/mcp · Homepage: https://usefulapi.io/teamup-calendar
https://teamup-calendar.usefulapi.io/mcp.claude mcp add --transport http teamup-calendar https://teamup-calendar.usefulapi.io/mcp, then run /mcp to log in.Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Teamup Calendar credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/teamup-calendar/
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this server only. Subscribe with teamup_upgrade (it returns a Stripe Checkout link). Cancel any time with teamup_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running teamup_upgrade before then undoes the cancel. Or write to [email protected].
MIT © usefulapi. Not affiliated with or endorsed by Teamup Calendar.
來源：servers/teamup-calendar/README.md，提交 4046075
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.
無需輸入參數。
List 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.
limitoffsetname_containsinclude_inactiveGet sub-calendar
One sub-calendar by id: name, color, overlap rule, active state and which links may use it. GET /{calendarKey}/subcalendars/{id}.
subcalendar_id必填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.
typelimitoffsetname_containsList 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.
tzend_datestart_datesubcalendar_idsSearch 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=.
tzlimitquery必填offsetend_datestart_datesubcalendar_idsGet 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}.
event_id必填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=.
modesince_timestamp必填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.
event_id必填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.
end必填whonotesrrulestart必填titlecustomall_daylocationsignup_limitsignup_enabledsubcalendar_ids必填另有 3 個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}.
endwhonotesreditrrulestarttitlecustomall_dayevent_id必填locationsignup_limit另有 5 個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}.
reditversionevent_id必填Undo event change
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}.
undo_id必填Create sub-calendar
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.
name必填coloractiveoverlapUpdate sub-calendar
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}.
namecoloractiveoverlapsubcalendar_id必填已滿足適用檢查項的 100%
該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。
io.usefulapi官方發布者
面向 Ably 即時訊息的託管 MCP 伺服器：檢視頻道歷史、線上狀態與佔用情形，發布訊息，並查看應用程式用量與設定。
io.usefulapi官方發布者
託管式唯讀 MCP 伺服器，讓助理查詢 Woffu 公司的使用者、勞動契約、部門與辦公地點。
io.usefulapi官方發布者
託管的 White Label Loyalty MCP 伺服器：瀏覽獎勵、查看客戶點數錢包與等級進度，並以點數購買獎勵。
io.usefulapi官方發布者
託管的 Weekdone 連接器，讓助理讀取週報、團隊、目標與 KPI，並新增報告項目、留言和 KPI 數值。
io.usefulapi官方發布者
託管式唯讀 MCP 伺服器，讓助理列出 WebinarKit 的網路研討會、場次時間、系列、會議以及白標子帳戶。
{ "mcpServers": { "teamup-calendar": { "url": "https://teamup-calendar.usefulapi.io/mcp" } }}