Hermes CalDAV MCP
Related Servers
Alternatives to Hermes CalDAV MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables full CRUD operations on calendar events, free/busy queries, and availability slot finding via CalDAV, supporting Nextcloud, Radicale, iCloud, and other RFC 4791-compliant servers.8MIT
- FlicenseNot gradedqualityBmaintenanceEnables interacting with CalDAV calendars (like iCloud) through natural language, supporting reading and writing events.1-
- FlicenseNot gradedqualityFmaintenanceEnables interaction with any CalDAV-compatible calendar server (Yandex, Google, Nextcloud, iCloud, etc.) to list calendars, create/manage events with reminders and attendees, search events, and handle recurring events through natural language.15-
- AlicenseNot gradedqualityAmaintenanceConnects AI assistants to CalDAV servers so they can list calendars, browse events within a timeframe, and create, update, delete, or complete events and tasks (VTODOs) through natural language. Supports recurring events, all-day entries, and todo filtering by status or due date with pagination.331 npmMIT
- AlicenseNot gradedqualityAmaintenanceConnects AI assistants to CalDAV servers so they can list calendars and browse, create, update, or delete events and to-do tasks within a chosen timeframe. Supports scheduling of recurring and all-day events, task filtering and pagination, and completion tracking through natural language.331 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables CRUD operations for calendar events, journal entries, and todos on any CalDAV server (like Radicale) through the Model Communication Protocol.MIT
TDQS
Scored across 5 tools
Each tool has a distinct resource+action: list_calendars, list_events, get_event, create_event, update_event. The descriptions clearly differentiate summary reads (list_events) from detailed reads (get_event) and create from update, leaving no realistic confusion.
All tool names follow a strict verb_noun snake_case pattern: list_calendars, list_events, get_event, create_event, update_event. There are no deviations or mixed conventions.
Five tools is reasonable for a focused CalDAV surface covering listing, reading, creating, and updating. It is slightly lean given the absence of any deletion or bulk operations, but each tool clearly earns its place.
The set covers create, read, and update for events plus calendar listing, but there is no delete_event, which is a notable lifecycle gap. Recurring events can only be updated at the series level, and create_event explicitly supports only non-recurring events, further limiting the surface.