Read and write CalDAV calendars: events, tasks and journal entries over the open standard
CalDAV calendars is an MCP integration. Read and write CalDAV calendars: events, tasks and journal entries over the open standard.
The published npm package is @ni-c/caldav-mcp, version 0.1.5. Its declared MCP transport is stdio.
The package declares CALDAV_URL (required): Root of the CalDAV server, e.g. https://dav.example.net. A calendar collection URL also works.; CALDAV_USERNAME: Account name. Most hosted services want an app-specific password with it.; CALDAV_PASSWORD: Password or app-specific password. Deleted from the environment once read.; CALDAV_TOKEN: Bearer token, as an alternative to username and password. Not both.; CALDAV_CALENDARS: Comma-separated calendars this server may touch, by path or final path segment. Default: all of them.; CALDAV_TIMEZONE: IANA zone for timestamps that carry no offset, e.g. Europe/Berlin (default: UTC); CALDAV_USER_EMAIL: The address you are invited as, so respond_to_event can find your own attendee line; CALDAV_MAX_EVENTS: Entries a listing returns by default, 1 to 500 (default: 100); CALDAV_READ_ONLY: Set to true to register only the read tools (default: false); CALDAV_INSECURE_TLS: Set to true to accept a self-signed certificate on the configured host only (default: false); CALDAV_ALLOW_PLAINTEXT: Set to true to allow a plain http:// URL to a host that is not loopback, which sends the credentials unencrypted (default: false); CALDAV_ALLOW_TOOLS: Comma-separated tool names or list_ prefixes to register; 'essential' selects a curated preset (default: all tools); CALDAV_DENY_TOOLS: Comma-separated tool names or list_ prefixes to remove from whatever the allow list left; ELICITATION: Deliberately unprefixed, and reaches every MCP server in the environment. Set to false to make guarded tools use the two-call token instead of a dialog (default: true).
The published oci package is ghcr.io/ni-c/caldav-mcp:0.1.5. Its declared MCP transport is stdio.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.5 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related productivity & project management MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| CALDAV_URL | Root of the CalDAV server, e.g. https://dav.example.net. A calendar collection URL also works. | Yes |
| CALDAV_USERNAME | Account name. Most hosted services want an app-specific password with it. | Check documentation |
| CALDAV_PASSWORD | Password or app-specific password. Deleted from the environment once read. | Check documentation |
| CALDAV_TOKEN | Bearer token, as an alternative to username and password. Not both. | Check documentation |
| CALDAV_CALENDARS | Comma-separated calendars this server may touch, by path or final path segment. Default: all of them. | Check documentation |
| CALDAV_TIMEZONE | IANA zone for timestamps that carry no offset, e.g. Europe/Berlin (default: UTC) | Check documentation |
| CALDAV_USER_EMAIL | The address you are invited as, so respond_to_event can find your own attendee line | Check documentation |
| CALDAV_MAX_EVENTS | Entries a listing returns by default, 1 to 500 (default: 100) | Check documentation |
| CALDAV_READ_ONLY | Set to true to register only the read tools (default: false) | Check documentation |
| CALDAV_INSECURE_TLS | Set to true to accept a self-signed certificate on the configured host only (default: false) | Check documentation |
| CALDAV_ALLOW_PLAINTEXT | Set to true to allow a plain http:// URL to a host that is not loopback, which sends the credentials unencrypted (default: false) | Check documentation |
| CALDAV_ALLOW_TOOLS | Comma-separated tool names or list_ prefixes to register; 'essential' selects a curated preset (default: all tools) | Check documentation |
| CALDAV_DENY_TOOLS | Comma-separated tool names or list_ prefixes to remove from whatever the allow list left | Check documentation |
| ELICITATION | Deliberately unprefixed, and reaches every MCP server in the environment. Set to false to make guarded tools use the two-call token instead of a dialog (default: true) | Check documentation |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.