Compared · calendar
32 Calendar MCP servers. Which one to use.
Every Calendar server we index, with whether its source is still reachable and whether we hold a screening verdict. 2 of 32 have a source repository that is no longer publicly reachable.
Scope: 32 servers, mostly mirrored from the MCP registry as of 2026-09-08. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Apple Calendar | io.github.JonathanRReed | no flag | REVIEW | 95 | pypi apple-calendar-mcp |
| Apple Calendar | io.github.mgcrea | no flag | REVIEW | 95 | npm @mgcrea/mcp-apple-calendar |
| Consistency Calendar | io.github.olliejgooding | no flag | REVIEW | 95 | remote endpoint |
| Timothe's Growth Calendar | ai.timothe | no flag | REVIEW | 94 | remote endpoint |
| Google Calendar MCP | io.github.A1-x-Tech | no flag | REVIEW | 90 | npm @a1-x-tech/mcp-google-calendar |
| io.github.IsaiahDupree/calendar-bridge | io.github.IsaiahDupree | no flag | REVIEW | 89 | remote endpoint |
| PlugRail Japanese Calendar | dev.plugrail | no flag | REVIEW | 88 | remote endpoint |
| cn.pianam.mcp/calendar-mcp | cn.pianam.mcp | no flag | REVIEW | 85 | remote endpoint |
| io.github.deciduus/calendar-mcp | io.github.deciduus | no flag | REVIEW | 85 | pypi calendar-mcp-server |
| Microsoft 365 Calendar | io.github.mindstone | no flag | REVIEW | 85 | npm @mindstone/mcp-server-microsoft-calendar |
| Apple Calendar | io.github.redpop | no flag | REVIEW | 85 | npm @redpop/apple-calendar-mcp |
| io.github.theluckystrike/calendar | io.github.theluckystrike | no flag | REVIEW | 85 | not published |
| io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts | io.github.theluckystrike | no flag | REVIEW | 85 | remote endpoint |
| org.onekash/icloud-calendar-mcp | org.onekash | no flag | REVIEW | 85 | npm @icloud-calendar-mcp/server |
| io.github.skypier-jp-works/mcp-jp-calendar | io.github.skypier-jp-works | no flag | REVIEW | 84 | npm mcp-jp-calendar |
| Calendar.app | io.github.p-l-ta | no flag | REVIEW | 83 | npm @p-l-ta/calendar-mcp |
| Mac Calendar MCP | io.github.wagamama | no flag | REVIEW | 83 | pypi mac-calendar-mcp |
| io.github.AMMAR-62/mewcp-google-calendar | io.github.AMMAR-62 | no flag | REVIEW | 82 | docker docker.io/ammar62/mewcp-google-calendar:latest |
| Boston Calendar | io.github.pipeworx-io | no flag | REVIEW | 81 | remote endpoint |
| io.github.0xka13b/ms-calendar-mcp | io.github.0xka13b | no flag | REVIEW | 80 | npm ms-calendar-mcp |
| io.github.IceyWu/icloud-calendar | io.github.IceyWu | no flag | REVIEW | 80 | npm icloud-calendar-mcp |
| Outlook Calendar | io.github.pipeworx-io | no flag | REVIEW | 80 | remote endpoint |
| io.github.CSOAI-ORG/content-calendar-ai-mcp | io.github.CSOAI-ORG | no flag | REVIEW | 77 | pypi content-calendar-ai-mcp |
| Google_calendar | io.github.pipeworx-io | no flag | REVIEW | 77 | remote endpoint |
| com.pulsemcp/google-calendar | com.pulsemcp | no flag | REVIEW | 76 | npm google-calendar-workspace-mcp-server |
| io.github.CSOAI-ORG/calendar-ai-mcp | io.github.CSOAI-ORG | no flag | REVIEW | 76 | pypi calendar-ai-mcp |
| Calendar Handoff Reader | io.github.Wxt-ai | no flag | REVIEW | 75 | remote endpoint |
| Coordination Calendar Desk | io.github.Wxt-ai | no flag | REVIEW | 75 | remote endpoint |
| com.am-lich/vietnamese-calendar | com.am-lich | no flag | REVIEW | 67 | remote endpoint |
| com.mintmcp/outlook-calendar | com.mintmcp | no flag | REVIEW | 60 | remote endpoint |
| TrueCal | io.github.SuperboxAI | repo unreachable | REVIEW | 91 | remote endpoint |
| io.github.infoinlet-marketplace/mcp-calendar | io.github.infoinlet-marketplace | repo unreachable | REVIEW | 75 | npm @infoinlet/mcp-calendar |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.