google-calendar-mcp and mcp
These are competitors—both provide calendar scheduling capabilities for AI agents, but A integrates with Google Calendar's existing infrastructure while B implements a standalone calendar server with advanced conflict resolution and rule expansion features.
About google-calendar-mcp
nspady/google-calendar-mcp
MCP integration for Google Calendar to manage events.
Enables multi-account and multi-calendar event management with cross-account conflict detection, recurring event modifications, and intelligent import from images/PDFs via natural language understanding. Implements an MCP server that communicates with Claude Desktop through stdio transport, supporting OAuth 2.0 authentication with automatic token refresh and account switching. Deployable via npx, local installation, or Docker with optional HTTP transport for browser-based account management.
About mcp
temporal-cortex/mcp
Calendar MCP server with atomic booking, conflict prevention, deterministic RRULE expansion, and TOON token compression for AI agents
Implements 18 tools across 5 layers using Two-Phase Commit for atomic booking and deterministic temporal computation via Truth Engine, eliminating hallucinations in scheduling tasks. Exposes capabilities via MCP, REST, A2A, and browser protocols with multi-provider support (Google Calendar, Outlook, CalDAV) and unified availability merging. Token-efficient TOON compression reduces context overhead by ~40% compared to JSON while maintaining full recurrence rule handling including DST, leap years, and complex intervals.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work