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 分