All servers / Calendar / CalDAV MCP server
CalDAV MCP server
Model Context Protocol (MCP) server for CalDAV calendars: events, tasks and journals over the open standard
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 0.2.0. Package: @ni-c/caldav-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.0 seconds including download)
- Tools offered: 22
- Last published: 2026-11-18
- Weekly downloads (npm): 1,834
- License: MIT · Direct dependencies: 8
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_calendarsno parametersEvery calendar this server may use, with the id to pass to the other tools. Always asks the server rather than answering from a cache — being current is this tool’s whole job.
get_server_infono parametersReports the DAV compliance tokens, which components each calendar accepts, and whether the optional features this server relies on actually work here. The first thing to run when something behaves differently than expected — CalDAV implementations differ more than the specification suggests.
list_events6 of 6 parameters describedEvents between two points in time, from every calendar this server may see or from the ones named. Recurring events are expanded into their individual occurrences, so each one has its own id and can be changed on its own. Defaults to the next 30 days.
get_event1 of 1 parameter describedThe complete event behind an id from a listing: the untruncated description, every reminder, every attendee, every attachment as metadata. An occurrence id answers with that one instance; a series id answers with the series and its rule.
search_events7 of 7 parameters describedFinds events whose summary, description or location contains a term. The search runs on the CalDAV server, one request per field and per calendar — the specification combines several field filters with AND, so asking for all three at once would only match entries carrying the term in every one of them.
get_free_busy4 of 4 parameters describedBusy periods in a time range — start and end only, no titles and no attendees. The datasparing way to ask "when am I free": nothing anybody else wrote comes back, so there is no untrusted content in the answer at all.
list_tasks7 of 7 parameters describedTasks with a start or due date inside a time range. Tasks with no date at all are not returned by a time-range query — the CalDAV specification defines the filter against the dates, and a task with none of them matches no window.
get_task1 of 1 parameter describedThe complete task behind an id from list_tasks, with its untruncated description and every reminder.
list_journals6 of 6 parameters describedDated notes in a calendar, inside a time range. Most calendar clients hide these; a CalDAV server stores them alongside events and tasks, and some workflows use them as a diary.
get_journal1 of 1 parameter describedThe complete note behind an id from list_journals, untruncated. This is the longest piece of somebody else’s prose this server hands over, so the text channel carries it inside an explicit untrusted fence.
create_event11 of 12 parameters describedAdds an event to a calendar. The UID and the file name are generated here, so an existing entry can never be overwritten by accident. Times without an offset are read in the timezone argument or in CALDAV_TIMEZONE.
update_event11 of 13 parameters describedChanges the fields named and leaves everything else exactly as it was — including properties this server does not model, attendees, attachments and reminders it cannot write. Pass null to clear a field. Guarded by the entry’s ETag: if it changed since it was read, nothing is written and the answer says what it is now. Changing a whole recurring series asks first.
delete_event3 of 3 parameters describedRemoves an event. An occurrence id removes just that occurrence — which iCalendar does by adding an exception date to the series, so the rest of the series is untouched. A series id removes the whole entry. A CalDAV server keeps no history: this cannot be undone.
move_event3 of 3 parameters describedCopies an event into another calendar and removes it from the first. The content survives, the address does not: every id that named this event stops working, and a listing is needed to get the new one. The destination may be a calendar other people can see.
respond_to_event3 of 3 parameters describedSets your own participation status on an event you were invited to. On a server with scheduling enabled this sends a reply to the organiser, which cannot be unsent — so it asks first. It changes only your own attendee line and never anybody else’s. This server cannot add or remove attendees at all.
create_task9 of 9 parameters describedAdds a task to a calendar that accepts them. list_calendars reports which do — a collection created for events only will refuse a task, and this server checks before writing rather than passing the server’s refusal back.
update_task8 of 10 parameters describedChanges the fields named and leaves everything else as it was. Pass null to clear a field. Guarded by the entry’s ETag. To mark a task done use complete_task, which records the completion time as well.
complete_task2 of 2 parameters describedSets the task’s status. Marking it done records the completion time and sets it to 100 %; reopening clears both. The previous state is written down in the entry, so this is reversible — which is why it does not ask first.
delete_task2 of 2 parameters describedRemoves a task. A CalDAV server keeps no history: this cannot be undone. To mark a task done instead, use complete_task.
create_journal6 of 6 parameters describedAdds a dated note to a calendar that accepts journal entries. list_calendars reports which do.
update_journal6 of 6 parameters describedReplaces the fields named. A CalDAV server keeps no version history, so the previous text of a note is gone once this succeeds — pass only the fields to change, and pass null to clear one. Guarded by the entry’s ETag, so a note changed elsewhere in the meantime is not silently overwritten.
delete_journal2 of 2 parameters describedRemoves a dated note. A CalDAV server keeps no history, and a note is somebody’s writing: this cannot be undone.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.