Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
AI-orchestrated calendars, contacts & tasks across any DAV platform. 27 tools, field-agnostic.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CALDAV_SERVER_URL, CALDAV_USERNAME, CALDAV_PASSWORD, AUTH_METHOD, GOOGLE_SERVER_URL, GOOGLE_USER, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN, GOOGLE_TOKEN_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"dav": {
"command": "npx",
"args": [
"-y",
"dav-mcp"
],
"env": {
"CALDAV_SERVER_URL": "your-value",
"CALDAV_USERNAME": "your-value",
"CALDAV_PASSWORD": "your-value",
"AUTH_METHOD": "your-value",
"GOOGLE_SERVER_URL": "your-value",
"GOOGLE_USER": "your-value",
"GOOGLE_CLIENT_ID": "your-value",
"GOOGLE_CLIENT_SECRET": "your-value",
"GOOGLE_REFRESH_TOKEN": "your-value",
"GOOGLE_TOKEN_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add dav --env CALDAV_SERVER_URL=your-value --env CALDAV_USERNAME=your-value --env CALDAV_PASSWORD=your-value --env AUTH_METHOD=your-value --env GOOGLE_SERVER_URL=your-value --env GOOGLE_USER=your-value --env GOOGLE_CLIENT_ID=your-value --env GOOGLE_CLIENT_SECRET=your-value --env GOOGLE_REFRESH_TOKEN=your-value --env GOOGLE_TOKEN_URL=your-value -- npx -y dav-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"dav": {
"command": "npx",
"args": [
"-y",
"dav-mcp"
],
"env": {
"CALDAV_SERVER_URL": "your-value",
"CALDAV_USERNAME": "your-value",
"CALDAV_PASSWORD": "your-value",
"AUTH_METHOD": "your-value",
"GOOGLE_SERVER_URL": "your-value",
"GOOGLE_USER": "your-value",
"GOOGLE_CLIENT_ID": "your-value",
"GOOGLE_CLIENT_SECRET": "your-value",
"GOOGLE_REFRESH_TOKEN": "your-value",
"GOOGLE_TOKEN_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"dav": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"dav-mcp"
],
"env": {
"CALDAV_SERVER_URL": "your-value",
"CALDAV_USERNAME": "your-value",
"CALDAV_PASSWORD": "your-value",
"AUTH_METHOD": "your-value",
"GOOGLE_SERVER_URL": "your-value",
"GOOGLE_USER": "your-value",
"GOOGLE_CLIENT_ID": "your-value",
"GOOGLE_CLIENT_SECRET": "your-value",
"GOOGLE_REFRESH_TOKEN": "your-value",
"GOOGLE_TOKEN_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
AUTH_METHOD envGOOGLE_SERVER_URL envGOOGLE_USER envGOOGLE_CLIENT_ID envGOOGLE_TOKEN_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account PhilflowIO, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: CALDAV_SERVER_URL, CALDAV_USERNAME, CALDAV_PASSWORD, GOOGLE_CLIENT_SECRET, GOOGLE_REFRESH_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (5.0.0) reached the registry 28 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
dav-mcp- .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 --http
Then in n8n:
http://localhost:3000/mcpCustom port:
npx dav-mcp --http --port=8080
Pull 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:latest
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
docker-compose up
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 |
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": "your@gmail.com", "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: hello@philflow.io.
Pull requests are welcome! Please read CONTRIBUTING.md for guidelines.
MIT License - see LICENSE for details
Built with:
Only the beginning is shown; read the rest in the repo