dav

This MCP server, dav-mcp, exposes a comprehensive suite of CalDAV/CardDAV and VTODO tools to manage calendars, address books, and tasks through the Model Context Protocol. It bundles 26 tools across three protocol families: CalDAV for calendars (11 tools), CardDAV for contacts (8 tools), and VTODO for tasks (7 tools). You can run the server locally via npx or expose it over HTTP for integration with n8n or other MCP clients. Typical usage paths include integrating with Claude Desktop for local orchestration or using HTTP mode (npx dav-mcp --http) for remote automation workflows. When used with HTTP, the server serves an MCP endpoint at /mcp and supports Bearer Token authentication for secure access.

Prerequisites:

• Node.js (and npm/yarn) installed on your system
• Access to the internet to fetch npm packages

Installation steps:

1. Install and run locally with npx (no global install required):

   • Prepare a configuration snippet (see mcp_config example below)
   • Place the snippet in your Claude config file or the target MCP config location
   • Start via your MCP runner that supports npx, e.g. npx dav-mcp

2. Docker-based setup (alternative):

   • git clone https://github.com/PhilflowIO/dav-mcp.git
   • cd dav-mcp
   • cp .env.example .env # edit with your credentials
   • docker-compose up

3. HTTP mode for integrations (optional):

   • Run: CALDAV_SERVER_URL=https://dav.example.com CALDAV_USERNAME=your_username CALDAV_PASSWORD=your_password BEARER_TOKEN=your-secret-token npx dav-mcp --http

4. For Google Calendar integration (optional):

   • Use the additional environment variables shown in the Google Calendar section of the README to configure OAuth-based access if needed.

Prerequisites summary: ensure you can reach your CalDAV/CardDAV server from your host, and that the credentials have sufficient permissions for the intended operations.

Tips and notes:

• The mcp_config example uses npx to fetch and run the dav-mcp package on demand. Adjust env vars to point at your CalDAV/CardDAV server.
• If running HTTP mode, protect your endpoint with a Bearer token and configure CORS as needed.
• The server supports a broad range of operations across calendars, address books, and todos; consider using calendar_query, addressbook_query, and todo_query for efficient filtered searches.
• When integrating with Claude Desktop or n8n, keep in mind the MCP endpoint is typically http://localhost:3000/mcp unless you customize the port.
• For production use, rotate credentials regularly and avoid logging sensitive data.