caldav-mcp and dav-mcp
The two tools are competitors, as both `dominik1001/caldav-mcp` and `PhilflowIO/dav-mcp` aim to expose CalDAV (and potentially other DAV services like CardDAV and VTODO for the latter) operations as tools for AI assistants using the Model Context Protocol (MCP).
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.
About dav-mcp
PhilflowIO/dav-mcp
Transform AI agents into orchestrating assistants managing calendars, contacts, and tasks
Implements 26 RFC-compliant tools (CalDAV, CardDAV, VTODO) with server-side filtering and field-based updates across all properties, exceeding typical MCPs by 4-10x capability depth. Deploys via MCP protocol to Claude Desktop/Cursor, n8n, and Docker with support for any standards-compliant DAV server or Google Calendar via OAuth2. Built on tsdav library with Zod validation, rate limiting, and bearer token authentication for secure HTTP transport.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work