Productivity · Local MCP server
Dav MCP
AI-orchestrated calendars, contacts & tasks across any DAV platform. 27 tools, field-agnostic.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.PhilflowIO/dav-mcp- Version
- 4.1.2
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- PhilflowIO (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/PhilflowIO) · how
- Listed under
- Calendar MCP servers
- Repository
- github.com/PhilflowIO/dav-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | dav-mcp | 4.1.2 | stdio |
How to connect Dav MCP
Dav MCP runs locally from a Node.js package published to the npm registry: dav-mcp version 4.1.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y dav-mcp@4.1.2. It reads these environment variables: CALDAV_SERVER_URL (required), CALDAV_USERNAME (required), CALDAV_PASSWORD (required, secret), AUTH_METHOD, GOOGLE_SERVER_URL, GOOGLE_USER, GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET (secret), GOOGLE_REFRESH_TOKEN (secret) and GOOGLE_TOKEN_URL; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"dav-mcp": {
"command": "npx",
"args": [
"-y",
"dav-mcp@4.1.2"
],
"env": {
"CALDAV_SERVER_URL": "<value>",
"CALDAV_USERNAME": "<value>",
"CALDAV_PASSWORD": "<secret>",
"AUTH_METHOD": "<value>",
"GOOGLE_SERVER_URL": "<value>",
"GOOGLE_USER": "<value>",
"GOOGLE_CLIENT_ID": "<value>",
"GOOGLE_CLIENT_SECRET": "<secret>",
"GOOGLE_REFRESH_TOKEN": "<secret>",
"GOOGLE_TOKEN_URL": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| DatabasinExplore Databasin data, run read-only queries, and manage your support tickets with secure sign-in. | Local · stdio |
| DatanemTurn PDFs, scans and photos into a queryable database. Invoices, CVs, receipts, in bulk. | Remote · HTTPLive check: sign-in required |
| DataQuollAustralian public data as MCP tools: incidents, gauges, declarations, industry calendars, archive. | Remote · HTTPLive check: ✗ no handshake |
| DatoQA - Official Public HolidaysGovernment and OpenHolidays calendars: regional scope, multilingual names, dated sources and gaps. | Remote · HTTPLive check: ✓ handshake |
| daybag.ioBookings for outdoor outfitters: check availability and book classes, appointments and rentals. | Remote · HTTPLive check: sign-in required |
| DayOneLeadFind newly registered businesses, manage prospects, and run approval-gated email outreach. | Remote · HTTPLive check: sign-in required |
| DazbenchTask management your AI agents can actually run. One line becomes a context-ready task over MCP. | Remote · HTTPLive check: sign-in required |
| Dead Simple EmailGive an agent its own inbox: send, receive, and pull signup codes from real email. | Remote & Local · HTTP, stdioLive check: sign-in required |