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