
Transform AI agents into orchestrating assistants managing calendars, contacts, and tasks
Transform AI agents into orchestrating assistants managing calendars, contacts, and tasks
·
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.
In Claude Code, run:
/plugin install dav-mcp --marketplace PhilflowIO/dav-mcpClaude Code then asks for your server URL, username and password. The plugin also brings a skill that teaches Claude to use the tools well. Details are in the plugin README.
dav-mcp-<version>.mcpb from the latest release. Releases from 4.1.2 on carry this file.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.
Add to your MCP config file:
{
"mcpServers": {
"dav-mcp": {
"command": "npx",
"args": ["-y", "dav-mcp"],
"env": {
"CALDAV_SERVER_URL": "https://dav.example.com",
"CALDAV_USERNAME": "your_username",
"CALDAV_PASSWORD": "your_password"
}
}
}
}Config file locations:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json~/.config/Claude/claude_desktop_config.jsonRestart Claude Desktop after adding the configuration.
Start the HTTP server:
CALDAV_SERVER_URL=https://dav.example.com \
CALDAV_USERNAME=your_username \
CALDAV_PASSWORD=your_password \
BEARER_TOKEN=your-secret-token \
npx dav-mcp --httpThen in n8n:
http://localhost:3000/mcpCustom port:
npx dav-mcp --http --port=8080Pull the published image (distroless, runs as non-root, no shell):
docker run -d --name dav-mcp -p 3000:3000 --env-file .env \
ghcr.io/philflowio/dav-mcp:latestTags: 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 upWhen 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 |
Europe/Berlin, sent as a VTIMEZONE)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.
Works with any CalDAV/CardDAV server that follows RFC 4791 and RFC 6352:
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.
For Google Calendar, use OAuth2 authentication:
{
"mcpServers": {
"dav-mcp": {
"command": "npx",
"args": ["-y", "dav-mcp"],
"env": {
"AUTH_METHOD": "OAuth",
"GOOGLE_USER": "[email protected]",
"GOOGLE_CLIENT_ID": "your-client-id",
"GOOGLE_CLIENT_SECRET": "your-client-secret",
"GOOGLE_REFRESH_TOKEN": "your-refresh-token"
}
}
}
}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.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].
Pull requests are welcome! Please read CONTRIBUTING.md for guidelines.
MIT License - see LICENSE for details
Built with:
Questions? Issues? Create a GitHub issue
Built for AI agents managing calendars, contacts, and tasks
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add dav-mcp -- npx -y dav-mcp{
"mcpServers": {
"dav-mcp": {
"env": {
"CALDAV_PASSWORD": "",
"CALDAV_USERNAME": "",
"CALDAV_SERVER_URL": ""
},
"args": [
"-y",
"dav-mcp"
],
"command": "npx"
}
}
}code --add-mcp '{"name":"dav-mcp","env":{"CALDAV_PASSWORD":"","CALDAV_USERNAME":"","CALDAV_SERVER_URL":""},"args":["-y","dav-mcp"],"command":"npx"}'[mcp_servers.dav-mcp]
command = "npx"
args = ["-y", "dav-mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/dav-mcp to learn what the "Dav Mcp" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
npx dav-mcp --http
npx dav-mcp --http --port=8080docker run -d --name dav-mcp -p 3000:3000 --env-file .envThis server runs locally, so we can't read its tool list over the web yet.
We could not run this server: its npm package has not answered in our offline sandbox, which usually means it needs an API key or other configuration to start. The four checks that need a live server are left out, and the grade tops out at B until we can read its tools.
Maintain this server? Claiming proves you own the listing and earns the last 4 points.
Claim this listingPaste this line near the top of your repository's README. The badge always renders the current score.
[](https://aiagentslisting.com/mcp/dav-mcp)Nothing comparable is listed yet.
v5.0.0Release notesv4.3.1Release notesv4.3.0Release notesv4.2.0v4.2.0 — dates keep their zone, series edited as a whole, parsed searchRelease notesv4.1.2v4.1.2 — one-click install for Claude DesktopRelease notesv4.1.1v4.1.1 — dependency security update, ETags after writesRelease notesv4.1.0v4.1.0 — Digest auth, arm64 images, honest write resultsRelease notesv4.0.1v4.0.1 — registry entry and published imagesRelease notesv4.0.0v4.0.0 — correctness releaseRelease notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "dav-mcp" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
One email a week. New agents, MCP servers and skills, and what is actually getting traction.