AddCal

co.addcal由 addcal.co 發布官方發布者v1.0.1更新於 Oct 24, 2026

Publish public calendars and events others subscribe to: RSVPs, feeds and add-to-calendar links.

已驗證Streamable HTTP可網頁執行效率與工作流溝通與協作資料與分析

概覽

AI 產生的概覽

AddCal 遠端 MCP 伺服器，用來發布供他人訂閱的公開行事曆與活動，支援報名、邀請、訂閱來源與數據分析。

可以做什麼
  • 在行事曆、合集、活動與報名中統一搜尋，取得其他工具所需的 ID
  • 列出並建立行事曆，把多個行事曆打包成一個附訂閱連結的公開合集
  • 列出、建立、更新、複製與刪除活動（含重複系列），建立前可預覽重複日期
  • 查看訂閱者與報名狀況、記錄報名，並以電子郵件寄送活動邀請
  • 查看加入行事曆點擊數與團隊用量等統計資料
適用情境
適合需要維護面向受眾的公開行事曆（例如課表、賽程、發布計畫、會議議程），並讓助理管理活動、訂閱者與報名的情境。它不用來讀寫你自己的個人行程。
執行需求
遠端 streamable HTTP 端點，無需安裝，也沒有 API 金鑰。使用 OAuth 2.1（PKCE 與動態用戶端註冊）：用戶端自行註冊，你在瀏覽器中授權後取得限定於團隊的權杖。部分用戶端需付費方案才能新增自訂連接器。合集、邀請與統計等功能取決於你的 AddCal 方案。
安裝前請注意
有三個工具標示為破壞性操作且需明確的 confirm 參數：send-event-invite 與 create-rsvp 會寄信給真人且無法收回，delete-event 為永久刪除，刪除重複活動會移除整個系列的所有場次。訂閱者與報名清單會回傳姓名、電子郵件等個人資料。權杖權限與你本人相同，可在設定中撤銷已連線的用戶端。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 AddCal，將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存，絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/co.addcal%2Faddcal/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "addcal": {
      "type": "http",
      "url": "https://addcal.co/mcp"
    }
  }
}

README

AddCal MCP Server

[smithery badge] [MCP Registry]

A remote Model Context Protocol server for AddCal. Connect Claude, ChatGPT, Cursor or any MCP client and manage the calendars other people subscribe to.

https://addcal.co/mcp

No install, no API key. It is a hosted streamable HTTP server and authentication is OAuth.

This is not a Google Calendar MCP

Almost every calendar MCP server does the same job: it reads and writes your own schedule. Useful, and well covered already.

AddCal is the other side of the calendar. It manages the events you publish for an audience: a class timetable, a fixture list, a release schedule, a conference programme. The people receiving those events never get an invite. They subscribe to a feed, or they click an add-to-calendar link, and the event lands in whichever calendar app they already use.

That difference shows up in the tools. There is no accept-invite, because nobody is invited. There is list-subscribers, get-analytics and create-calendar-collection, because the questions you ask about a published calendar are how many people follow it and whether anyone actually added the event.

Use a Google Calendar MCP to run your day. Use this one to run a calendar other people follow.

Quick start

Pick your client. Cursor and VS Code install in one click.

[Add to Cursor] [Add to VS Code]

Claude Code

bash
claude mcp add --transport http addcal https://addcal.co/mcp

Then run /mcp inside Claude Code to sign in.

Claude Desktop and claude.ai

Settings, Connectors, Add custom connector, then paste https://addcal.co/mcp. Custom connectors need a paid plan.

ChatGPT

Settings, Apps & Connectors, Advanced, turn on Developer mode, then add https://addcal.co/mcp as a connector. Requires a paid plan on the web app.

Anything else

Any client that speaks streamable HTTP with OAuth. Windsurf, Goose, Zed and the JetBrains AI Assistant all take a remote MCP URL.

json
{  "mcpServers": {    "addcal": {      "type": "http",      "url": "https://addcal.co/mcp"    }  }}

Authentication

OAuth 2.1 with PKCE and dynamic client registration. There is no API key to copy and paste.

Your client registers itself, you approve it in a browser, and it receives a token scoped to your team. It can reach exactly what you can reach, no more. Revoke any connected client from Settings, API.

What you can ask for

What have I got on next week?Create a team standup every weekday at 9am and show me the dates first.Who has RSVPed yes to the launch party?Duplicate last month's workshop into March.Which of my events got the most add-to-calendar clicks?

Tools

19 tools. RO is read only. Required parameters are marked *.

Search

ToolParameters
searchROquery*, limit, team_id

One call across calendars, collections, events and RSVPs, returning the ids every other tool needs. Start here whenever something is named rather than identified.

Calendars

ToolParameters
list-calendarsROsearch, limit, team_id
create-calendarname*, description, timezone, team_id

Collections

A collection bundles several calendars behind one public page and subscribe link.

ToolParameters
list-calendar-collectionsROteam_id
create-calendar-collectionname*, calendar_ids*, description, allow_subscriber_selection, team_id

Subscribers

ToolParameters
list-subscribersROcalendar_id*, status, search, limit

Returns personal data. Names and emails exist only for calendars that ask subscribers for details, so many rows are anonymous.

Events

ToolParameters
list-eventsROcalendar_id, search, range, start_date, end_date, limit, team_id
get-eventROevent_id*
create-eventcalendar_id*, title*, date_start*, date_end*, timezone, description, location, is_all_day, is_draft, has_rsvp, recurrence_rule, series_title, reminder_before
update-eventevent_id*, title, description, location, date_start, date_end, timezone, is_all_day, is_draft, has_rsvp, recurrence_rule, reminder_before
duplicate-eventevent_id*, target_calendar_id, title, date_start, date_end
delete-eventdestructiveevent_id*, confirm*, notify_invitees
preview-recurring-datesROrecurrence_rule*, date_start*, date_end*, timezone, is_all_day, count

Recurrence uses RFC 5545 rules without the RRULE: prefix, such as FREQ=WEEKLY;BYDAY=MO;COUNT=10. Run preview-recurring-dates before creating a series to check the dates land where you expect.

RSVPs

ToolParameters
list-rsvpsROevent_id*, response_type, search, limit
create-rsvpdestructiveevent_id*, name*, email*, response_type*, confirm*, custom_fields, send_confirmation

create-rsvp emails the attendee by default. Set send_confirmation to false to record an RSVP silently.

Invites

ToolParameters
list-invitesROevent_id*, status, search, limit
send-event-invitedestructiveevent_id*, email*, confirm*

Account

ToolParameters
get-analyticsROcalendar_id, event_id, start_date, end_date, timezone, unique_only, include_series, team_id
get-team-usageROteam_id

Destructive tools

Three tools are annotated destructive, and all three require an explicit confirm parameter:

  • send-event-invite and create-rsvp email a real person. That cannot be recalled.
  • delete-event is permanent, and deleting a recurring event removes every instance in the series.

A well-behaved client surfaces these for approval before running them. Check the name and address when your assistant asks.

Plans and limits

The server is included on every plan, and the tools respect whatever your plan already allows. Collections, calendar invites and analytics stay gated to the plans that include them. When a tool hits a limit it explains why rather than retrying.

Links

About this repository

AddCal's MCP server is hosted, so there is nothing here to install or run. This repository holds the published server.json manifest and the documentation for the remote endpoint. The implementation lives in the main AddCal application.

Found a problem with a tool, or want one that does not exist yet? Open an issue.

來源：README.md，提交 9fd4f59

工具

0
該伺服器需要登入，因此 SourceWeft 無法在沒有帳號的情況下讀取其工具，也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.1最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分