AddCal MCP server
Manage public calendars, event collections, and subscriber analytics through an AI client.
Also known as addcal/mcp, mcp
- Stars
- 1
- Tools
- 21
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Aug 14, 2026
- License
- MIT
What is AddCal MCP?
AddCal manages public calendars, event collections, and subscriber analytics through an AI client. It exposes 21 tools, such as search, list-calendars, create-calendar.
Summary generated from the project's README
About AddCal MCP server
AddCal provides a remote MCP server designed for managing public calendars and event collections that people subscribe to. Unlike standard calendar servers that handle personal schedules, this tool focuses on published content like class timetables, conference programmes, or release schedules. It allows users to manage the events they share with an audience through an AI client.
This is a hosted HTTP server that requires no local installation or manual API key management. Instead, it uses OAuth 2.1 with PKCE for authentication. You can connect it to clients like Claude Desktop, ChatGPT, Cursor, or VS Code by providing the remote URL. It works with any client supporting streamable HTTP, including Windsurf, Goose, and Zed.
The server includes 19 tools for searching, managing calendars, creating collections, and tracking subscribers. You can use specific commands to list subscribers, get analytics on event clicks, or duplicate events. Some actions, such as deleting events or sending invites, are marked as destructive and require explicit confirmation.
What you can do with it
- 1Analyze event engagementAsk the AI to identify which published events received the highest number of add-to-calendar clicks.
- 2Manage subscriber listsRequest a list of people who have subscribed to a specific public calendar.
- 3Organize event seriesInstruct the client to create a recurring series of events for a team standup.
- 4Bundle multiple calendarsUse the AI to group several different calendars into a single public collection.
Written from the project's README. Every use case is checked against a quote from it.
How to install AddCal MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall AddCal MCP in Claude Code
$ claude mcp add --transport http mcp https://addcal.co/mcpInstall AddCal MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://addcal.co/mcp"
}
}
}Install AddCal MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://addcal.co/mcp"
}
}
}Install AddCal MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://addcal.co/mcp"}'Install AddCal MCP in Codex
$ codex mcp add mcp --url https://addcal.co/mcpInstall AddCal MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] url = "https://addcal.co/mcp"
Install AddCal MCP in Gemini CLI
$ gemini mcp add -s user --transport http mcp https://addcal.co/mcpInstall AddCal MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://addcal.co/mcp",
"type": "http"
}
}
}AddCal MCP tools 21
Detected from the READMEsearchlist-calendarscreate-calendarlist-calendar-collectionscreate-calendar-collectionlist-subscriberslist-eventsget-eventcreate-eventupdate-eventduplicate-eventdelete-event
Show all 21 toolsShow fewer tools
preview-recurring-dateslist-rsvpscreate-rsvplist-invitessend-event-inviteget-analyticsget-team-usagesend-eventdelete
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableaddcal/mcp is public and reachablegithub.com/addcal/mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-08-14github.com/addcal/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model21 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubAddCal MCP Server
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.
Claude Code
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.
{
"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
| Tool | Parameters | |
|---|---|---|
search |
RO | query*, 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
| Tool | Parameters | |
|---|---|---|
list-calendars |
RO | search, limit, team_id |
create-calendar |
name*, description, timezone, team_id |
Collections
A collection bundles several calendars behind one public page and subscribe link.
| Tool | Parameters | |
|---|---|---|
list-calendar-collections |
RO | team_id |
create-calendar-collection |
name*, calendar_ids*, description, allow_subscriber_selection, team_id |
Subscribers
| Tool | Parameters | |
|---|---|---|
list-subscribers |
RO | calendar_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
| Tool | Parameters | |
|---|---|---|
list-events |
RO | calendar_id, search, range, start_date, end_date, limit, team_id |
get-event |
RO | event_id* |
create-event |
calendar_id*, title*, date_start*, date_end*, timezone, description, location, is_all_day, is_draft, has_rsvp, recurrence_rule, series_title, reminder_before |
|
update-event |
event_id*, title, description, location, date_start, date_end, timezone, is_all_day, is_draft, has_rsvp, recurrence_rule, reminder_before |
|
duplicate-event |
event_id*, target_calendar_id, title, date_start, date_end |
|
delete-event |
destructive | event_id*, confirm*, notify_invitees |
preview-recurring-dates |
RO | recurrence_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
| Tool | Parameters | |
|---|---|---|
list-rsvps |
RO | event_id*, response_type, search, limit |
create-rsvp |
destructive | event_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
| Tool | Parameters | |
|---|---|---|
list-invites |
RO | event_id*, status, search, limit |
send-event-invite |
destructive | event_id*, email*, confirm* |
Account
| Tool | Parameters | |
|---|---|---|
get-analytics |
RO | calendar_id, event_id, start_date, end_date, timezone, unique_only, include_series, team_id |
get-team-usage |
RO | team_id |
Destructive tools
Three tools are annotated destructive, and all three require an explicit confirm parameter:
send-event-inviteandcreate-rsvpemail a real person. That cannot be recalled.delete-eventis 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
- MCP server guide
- Full tool reference
- REST API reference
- Smithery listing
- Official MCP registry entry
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.
AddCal MCP questions
How do I add AddCal MCP to Claude Code?
Run claude mcp add --transport http mcp https://addcal.co/mcp in your terminal. Add --scope user to make it available in every project.
How do I add AddCal MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does AddCal MCP provide?
It exposes 21 tools, including search, list-calendars, create-calendar, list-calendar-collections, create-calendar-collection.
How do I authenticate with the AddCal MCP server?
The server uses OAuth 2.1 with PKCE and dynamic client registration, so there is no API key to copy and paste.
Does the server require installation?
No, it is a hosted streamable HTTP server that requires no installation.
Can I see how many people are following my calendar?
Yes, you can use tools to list subscribers and get analytics on event clicks and engagement.