Give your AI agents the power of organization — Transform them into orchestrating assistants managing calendars, contacts, and tasks.
Built on 27 production-ready tools spanning CalDAV, CardDAV, and VTODO protocols.
Complete DAV integration for AI - Calendar (CalDAV), Contacts (CardDAV), and Tasks (VTODO) management via MCP protocol
2026-11-13
星标
—
工具
—
可用率
—
Quick Start
One-click install (Claude Desktop)
Download dav-mcp-<version>.mcpb from the latest release. Releases from 4.1.2 on carry this file.
Open it with Claude Desktop (macOS or Windows). Claude shows an install dialog.
Enter your server URL, username and password. The password is stored as a secret. Leave the authentication method at Basic unless your server needs Digest.
The .mcpb file is an MCP Bundle: the server with its dependencies, so neither Node.js nor npx needs to be installed.
Tags: latest, the exact release (5.0.0) and the minor line (5.0).
Set PORT to serve on a different port; the healthcheck follows it.
Or build from source:
git clone https://github.com/PhilflowIO/dav-mcp.git
cd dav-mcp
cp .env.example .env
# Edit .env with your credentials
docker-compose up
The Orchestration
When partial tools force your AI to improvise, complete tools let it execute precise operations across all components.
Capability
dav-mcp
Most MCPs
Calendar Management
Full CRUD (12 tools)
Create + list only (2-3 tools)
Contact Management
Complete CardDAV (8 tools)
Often missing entirely
Task Management
Full VTODO support (7 tools)
Rarely included
Field-Based Updates
All RFC properties + custom fields
Rarely available
Free/Busy
Works on every server (client-side)
Native REPORT, unsupported by most
Server-Side Filtering
Efficient queries
Dumps all data
Multi-Provider
Any CalDAV/CardDAV server
Limited provider support
Total Tools
27 tools
2-6 tools
Available Tools (27 Total)
CalDAV Tools (12 tools)
list_calendars - List all available calendars
list_events - List ALL events (use calendar_query for filtered searches)
create_event - Create a new calendar event
update_event - PREFERRED: Update any event field (SUMMARY, LOCATION, STATUS, custom X-* properties); move or convert an event with start_date/end_date/all_day
update_event_raw - Update event with raw iCal data (advanced)
delete_event - Delete an event permanently
calendar_query - PREFERRED: Search and filter events efficiently by text, date range, or location
make_calendar - Create a new calendar collection, optionally with a time zone (an IANA name such as Europe/Berlin, sent as a VTIMEZONE)
delete_calendar - Delete a calendar and all its events
calendar_multi_get - Batch fetch multiple specific events by URLs
freebusy_query - Find free and busy time in a range ("when am I free?"), calculated client-side
CardDAV Tools (8 tools)
list_addressbooks - List all available address books
list_contacts - List ALL contacts (use addressbook_query for filtered searches)
create_contact - Create a new contact (vCard)
update_contact - PREFERRED: Update any contact field (FN, EMAIL, TEL, ORG, ADR, custom X-* properties)
update_contact_raw - Update contact with raw vCard data (advanced)
delete_contact - Delete a contact permanently
addressbook_query - PREFERRED: Search and filter contacts efficiently by name, email, or organization
addressbook_multi_get - Batch fetch multiple specific contacts by URLs
VTODO Tools (7 tools)
list_todos - List ALL todos/tasks (use todo_query for filtered searches)
create_todo - Create a new todo/task with optional due date, priority, status
update_todo - PREFERRED: Update any todo field (SUMMARY, STATUS, PRIORITY, DUE, PERCENT-COMPLETE, custom X-* properties)
update_todo_raw - Update todo with raw VTODO iCal data (advanced)
delete_todo - Delete a todo/task permanently
todo_query - PREFERRED: Search and filter todos efficiently by status/due date
todo_multi_get - Batch fetch multiple specific todos by URLs
Time zones
An event or todo written without a time zone (a "floating" time such as
DTSTART:20261010T090000, or an all-day date) is read in its calendar's time
zone, as CalDAV specifies (RFC 4791 §9.9): the zone set with make_calendar /
update_calendar, which list_calendars shows. A calendar without one is read
in the zone dav-mcp runs in: the TZ environment variable (for example
TZ=Europe/Berlin in Docker or an HTTP deployment), else the system's. A time
without a zone given to the create and update tools is read the same way, and
an event stored without a zone stays without one when it is moved.
freebusy_query prints its slots in the calendar's zone and names it.
Real-World Applications
n8n Automation Workflows
Meeting Management: "Show me all Friday meetings" → calendar_query with date filter returns only relevant events
Contact Search: "Find everyone at Google" → addressbook_query with org filter finds matches efficiently
Task Reporting: "Show overdue high-priority tasks" → todo_query with filters returns specific results
Contact Lookup: "What's Sarah's email?" → addressbook_query with name filter finds contact
Calendar Overview: "What's on my calendar next week?" → calendar_query with date range shows events
Calendar Management: "Create a new calendar called Project Luna" → make_calendar creates collection
Works Across All Major Providers
Works with any CalDAV/CardDAV server that follows RFC 4791 and RFC 6352:
Nextcloud - Full support
Baikal - Full support
Radicale - Full support
iCloud - Works with app-specific password
Any RFC-compliant server - Standard protocol support
Authentication
AUTH_METHOD selects how dav-mcp logs in (case-insensitive):
AUTH_METHOD
Credentials
Use for
Basic (default)
CALDAV_USERNAME, CALDAV_PASSWORD
Almost every server. If the server only offers Digest (for example Baikal set to Digest), dav-mcp switches to Digest by itself — no setting needed.
Digest
CALDAV_USERNAME, CALDAV_PASSWORD
Servers that only accept Digest (RFC 7616). Unlike the automatic switch under Basic, which first sends the password once Basic-encoded and is then rejected, Digest never sends the password — use it when the connection is not HTTPS.
OAuth (or OAuth2)
GOOGLE_*, see below
Google Calendar
dav-mcp needs Node.js 22 or newer. A wrong configuration — an unknown
AUTH_METHOD value, or missing credentials for the chosen method — stops the
server at startup instead of falling back to Basic.
Input Validation: All inputs validated with Zod schemas before execution
Rate Limiting (HTTP mode): 100 requests per 15 minutes per client address, counted before the bearer token is checked. Clients on loopback or a private network (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) — another container on the same Docker network, for example — get 10,000. Limitation: dav-mcp sees the address of whatever connects to it. Behind a Docker port mapping or a reverse proxy that is the bridge gateway or the proxy, so all outside clients share that one address, its one counter and its raised limit. Rate-limit per client at the proxy if you expose the HTTP transport.
Bearer Auth: Token authentication for HTTP transport
No Credential Storage: Pass-through only, never logged or cached
Structured Logging: Audit trail with request IDs, no PII exposure
Tool-Call Log Off by Default: LOG_TOOL_CALLS=true records every tool call with its arguments, for debugging — to ~/.local/state/dav-mcp/tool-calls.jsonl (or $XDG_STATE_HOME, %LOCALAPPDATA% on Windows, or TOOL_CALL_LOG_FILE), readable by you only. TOOL_CALL_LOG_MODE=console sends it to stderr instead.
CORS Protection: Whitelist origins, block cross-site attacks
Privacy Policy
dav-mcp runs on your machine (or your own server) and talks only to the DAV server you configure. It has no telemetry and shares nothing with its maintainers or third parties. Tool results go to the AI assistant that called the tool. Credentials and calendar data are not stored by dav-mcp; the optional tool-call log is off by default. Full policy: PRIVACY.md. Contact: [email protected].
