by PhilflowIO
Transform AI agents into orchestrating assistants managing calendars, contacts, and tasks
Provides comprehensive CalDAV, CardDAV, and VTODO protocol support for managing calendars, contacts, and tasks across any RFC-compliant server with 26 production-ready tools.
dav-mcp is a community-built MCP server published by PhilflowIO that provides AI assistants with tools and capabilities via the Model Context Protocol. Transform AI agents into orchestrating assistants managing calendars, contacts, and tasks It is categorized under auth security. This server exposes 20 tools that AI clients can invoke during conversations and coding sessions.
You can install dav-mcp in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
dav-mcp is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
We wired dav-mcp into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: dav-mcp surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Useful MCP listing: dav-mcp is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: dav-mcp surfaces stars and publisher context so we could sanity-check maintenance before adopting.
dav-mcp reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired dav-mcp into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Strong directory entry: dav-mcp surfaces stars and publisher context so we could sanity-check maintenance before adopting.
We wired dav-mcp into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
We wired dav-mcp into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
dav-mcp reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
showing 1-10 of 71
Give your AI agents the power of organization — Transform them into orchestrating assistants managing calendars, contacts, and tasks.
Built on 26 production-ready tools spanning CalDAV, CardDAV, and VTODO protocols.
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
git clone https://github.com/PhilflowIO/dav-mcp.git
cd dav-mcp
cp .env.example .env
# Edit .env with your credentials
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 (11 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 |
| Server-Side Filtering | Efficient queries | Dumps all data |
| Multi-Provider | Any CalDAV/CardDAV server | Limited provider support |
| Total Tools | 26 tools | 2-6 tools |
Works with any CalDAV/CardDAV server that follows RFC 4791 and RFC 6352:
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"
}
}
}
}
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
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.