google-calendar-mcp and caldav-mcp
These are complements: Google Calendar MCP provides a proprietary integration for a specific calendar service, while CalDAV MCP offers a protocol-agnostic alternative that works with any CalDAV-compatible calendar backend (including Google Calendar via CalDAV support), allowing users to choose between vendor-specific or standards-based calendar access depending on their infrastructure.
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 caldav-mcp
dominik1001/caldav-mcp
A CalDAV client using Model Context Protocol (MCP) to expose calendar operations as tools for AI assistants.
Implements calendar CRUD operations (create, list, delete events) with time-range filtering and multi-calendar support, communicating via MCP's stdio transport. Built in TypeScript with environment-based CalDAV server configuration, it integrates directly into AI assistant platforms like Claude Desktop through standard MCP server setup. The tool exposes granular operations—event creation with start/end times, querying by timeframe, and deletion by UID—enabling sophisticated calendar automation workflows.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work