Pod

Yes, this is on purpose. Pod is built for agents, so the default page is plain HTML.
Human? View the normal website.
Agent? You probably prefer /mcp/caldav-mcp/issues.md or /mcp/caldav-mcp/issues.json, or Pod over MCP.

Reported issues for caldav-mcp

Pod holds 9 of 9 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to caldav-mcp.

Most discussed

Second update-event on the same event fails with HTTP 412

Reporting rather than fixing, since the cause looks like it sits in ts-caldav rather than here, and I have not pinned it down far enough to propose a patch.

What happens

The second update-event on the same event fails, reliably:

create-event  → ok
update-event  (change only the location) → ok
update-event  (change only the summary)  → Error: Event with the specified uid does not match.

A freshly created event can then be updated exactly once again, so it tracks the event, not

Read the thread · 2026-08-16 · open · external user · 1 comment

[BUG] wholeDay events are stored one day early for timezones ahead of UTC (UTC date truncation after Date conversion)

Summary

When creating (or updating) an all-day event with wholeDay: true and passing local-midnight ISO datetimes with a positive UTC offset (e.g. Asia/Seoul, +09:00), the event is stored on the previous calendar day on the server. The tool description says "For a single-day all-day event, use start and end datetimes on the same calendar date", which is exactly what triggers it.

Environment

Read the thread · 2026-07-23 · open · external user · 0 comments

create-event and list-events missing description and location fields (present in update-event)

Bug / Feature Request

Two tools have incomplete field coverage compared to `update-event`:

1. `create-event` — cannot set description or location at creation time

`create-event` only accepts: `summary`, `start`, `end`, `calendarUrl`, `recurrenceRule`. The only workaround is a two-step call: `create-event` then immediately `update-event`.

2. `list-events` — silently drops description and location from results

`list-events` fetches full event objects but map

Read the thread · 2026-04-27 · closed · external user · 3 comments

Ontheia listed as compatible client — works great with caldav-mcp

Hi,

We've been testing your MCP server with Ontheia — a self-hosted, open-source AI agent platform — and it works great out of the box.

We've added it to our Compatible MCP Servers page to help our users discover it.

If you'd like to list Ontheia as a compatible client in your README, we'd be happy about that — but no obligation at all.

Thanks for building this! — Wolfgang, founder of

Read the thread · 2026-04-21 · closed · external user · 1 comment

Possibility of CardDAV

Hello Dominik,

Love to see a calendar connector MCP server that supports a proper open standard (vs existing e.g. Google Calendar specific ones).

I'd also like to wire up my address book. Since CalDAV and CardDAV are closely related, I was wondering if you could see such code living in this repo? I'd also be open to submitting PRs, but have to honestly admit that due to time constraints it would mostly be vibe coded.

Happy to hear your thoughts. David

Read the thread · 2026-03-02 · closed · external user · 2 comments

Issue: end parameter required but causes inconsistent -32602 validation errors when omitted; recommend making it optional

Summary: The list-events tool's end parameter is required by the Zod schema, but when an LLM caller omits it (passing null), the MCP gateway sometimes strips the null silently (returning []) and sometimes passes it through (triggering a -32602 validation error). Making end optional with a sensible default would eliminate the inconsistency and make the tool significantly more ergonomic for multi-calendar workflows.

Observed behaviour When calling list-events with end: null — which LLMs naturally

Read the thread · 2026-02-23 · closed · external user · 2 comments

[BUG] No events found in nextcloud calenders

Hi there,

Just tried this MCP Server and it does connect to my Nextcloud instance after correcting the path from /remote.php/dav to /remote.php/undefined However it only discovers my calender but it cannot fetch any events from there. Neither add new events to a calender. Do you have an Idea what is going on? How can i debug this issue?

Cheers!

Read the thread · 2026-01-06 · closed · external user · 3 comments

[FEATURE] Support skipping certificate validation

Hey! Could support for skipping certificate validation be added please? I am personally just using local IP addresses for connecting to CalDAV and am just using self-signed certificates since it's just my own internal infrastructure. I suspect a lot of people hosting MCP servers are doing something similar.

Logs for context 
2025-08-02 14:02:32,263 - INFO - Initiating connection for server: 'calendar'...
npm warn exec The following package was not found an
Read the thread · 2025-08-02 · open · external user · 3 comments


Most recent


list-events: 'end' parameter is unnecessarily required


list-events: end parameter is unnecessarily required


Summary


The end parameter in the list-events tool's inputSchema is defined as required, but the underlying ts-caldav library's getEvents treats end as optional. This prevents AI models from querying events without specifying end, and when null or undefined is passed, it causes unpredictable behavior.




Disclaimer: I'm not a developer, so the technical analysis below may not be entirely accurate. I investigated




Read the thread · 2026-03-01 · closed · external user · 0 comments


The remaining reports are on the project's issue tracker.