Compared · calendar
23 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 23 have a source repository that is no longer publicly reachable.
Scope: 23 servers, mostly mirrored from the MCP registry as of 2026-08-13. 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 |
|---|---|---|---|---|---|
| Timothe's Growth Calendar | ai.timothe | no flag | REVIEW | 95 | remote endpoint |
| Apple Calendar | io.github.JonathanRReed | no flag | not screened | 95 | pypi apple-calendar-mcp |
| Consistency Calendar | io.github.olliejgooding | no flag | not screened | 95 | remote endpoint |
| PlugRail Japanese Calendar | dev.plugrail | no flag | REVIEW | 90 | remote endpoint |
| io.github.IsaiahDupree/calendar-bridge | io.github.IsaiahDupree | no flag | REVIEW | 90 | remote endpoint |
| Microsoft 365 Calendar | io.github.mindstone | no flag | REVIEW | 85 | npm @mindstone/mcp-server-microsoft-calendar |
| Calendar.app | io.github.p-l-ta | no flag | REVIEW | 85 | npm @p-l-ta/calendar-mcp |
| Apple Calendar | io.github.redpop | no flag | REVIEW | 85 | npm @redpop/apple-calendar-mcp |
| io.github.skypier-jp-works/mcp-jp-calendar | io.github.skypier-jp-works | no flag | REVIEW | 85 | npm mcp-jp-calendar |
| Mac Calendar MCP | io.github.wagamama | no flag | REVIEW | 85 | pypi mac-calendar-mcp |
| org.onekash/icloud-calendar-mcp | org.onekash | no flag | REVIEW | 85 | npm @icloud-calendar-mcp/server |
| io.github.AMMAR-62/mewcp-google-calendar | io.github.AMMAR-62 | no flag | REVIEW | 84 | docker docker.io/ammar62/mewcp-google-calendar:latest |
| Boston Calendar | io.github.pipeworx-io | no flag | REVIEW | 83 | remote endpoint |
| io.github.0xka13b/ms-calendar-mcp | io.github.0xka13b | no flag | REVIEW | 82 | npm ms-calendar-mcp |
| Outlook Calendar | io.github.pipeworx-io | no flag | REVIEW | 82 | remote endpoint |
| io.github.CSOAI-ORG/content-calendar-ai-mcp | io.github.CSOAI-ORG | no flag | REVIEW | 79 | pypi content-calendar-ai-mcp |
| Google_calendar | io.github.pipeworx-io | no flag | REVIEW | 79 | remote endpoint |
| com.pulsemcp/google-calendar | com.pulsemcp | no flag | REVIEW | 78 | npm google-calendar-workspace-mcp-server |
| io.github.CSOAI-ORG/calendar-ai-mcp | io.github.CSOAI-ORG | no flag | REVIEW | 78 | pypi calendar-ai-mcp |
| com.am-lich/vietnamese-calendar | com.am-lich | no flag | REVIEW | 69 | remote endpoint |
| com.mintmcp/outlook-calendar | com.mintmcp | no flag | REVIEW | 62 | remote endpoint |
| TrueCal | io.github.SuperboxAI | repo unreachable | REVIEW | 93 | remote endpoint |
| io.github.infoinlet-marketplace/mcp-calendar | io.github.infoinlet-marketplace | repo unreachable | REVIEW | 77 | 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.