dav-mcp
Related Servers
Alternatives to dav-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceTransform AI agents into orchestrating assistants managing calendars, contacts, and tasks via CalDAV, CardDAV, and VTODO protocols.162 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to manage personal tasks, calendar events, and projects through 12 tools covering CRUD operations, cross-entity search, daily analysis, and multi-step action planning. Supports natural-language requests that are orchestrated into real actions with real-time streaming updates.78 npmMIT
- FlicenseNot gradedqualityDmaintenanceA privacy-first, local-first MCP server that provides 15 ADHD/second-brain tools for capturing, prioritizing, and resurfacing tasks with context from calendar, mail, and messages.1-
- FlicenseNot gradedqualityCmaintenanceEnables LLM agents to read, schedule, update, and delete calendar events and tasks on a self-hosted CalDAV server, and to query availability for free/busy slots.-
- AlicenseAqualityAmaintenanceEnables AI agents to list, create, update, upsert, and delete calendar events that are stored as notes in a self-hosted Trilium instance, exposing tool names and arguments interchangeable with the Nextcloud Calendar MCP. Events carry stable UIDs, timezone-aware start/end and inclusive all-day semantics, tags, locations and recurrence, and the same notes can be served to standard calendar clients over CalDAV.9MIT
- AlicenseNot gradedqualityFmaintenanceProvider-agnostic CalDAV calendar MCP server that connects any CalDAV calendar to AI assistants, enabling calendar operations like listing, creating, updating, and deleting events.34 PyPIAGPL 3.0
TDQS
Scored across 27 tools
Tools are cleanly partitioned by resource (calendar/event/contact/todo) and descriptions explicitly disambiguate list vs query vs multi_get and update vs update_raw, with PREFERRED/WARNING markers guiding selection. There is genuine overlap among the three read paths for each resource (e.g. list_events vs calendar_query vs calendar_multi_get), but descriptions make the boundaries clear.
Most tools follow a verb_noun pattern (list_events, create_contact, update_todo, delete_calendar) consistently. Deviations are systematic rather than chaotic: the noun-first *_query and *_multi_get families, the *_raw suffix variants, and make_calendar instead of create_calendar. Readable overall but not a single uniform convention.
27 tools is on the heavy side, but it reflects a broad CalDAV/CardDAV domain spanning calendars, events, todos, contacts, and addressbooks, each with its own CRUD lifecycle. The count is inflated somewhat by per-resource *_raw and list/query/multi_get variants, but each tool serves a defensible purpose.
Full lifecycle coverage (list/query/create/update/delete) exists for events, todos, and contacts, plus calendar management and freebusy queries. Minor gaps remain: addressbooks can only be listed (no create/update/delete), and there is no dedicated attendee/RSVP handling for events.