Caldav MCP
MCP server giving AI assistants read and write access to CalDAV calendars and tasks
Caldav MCP is an open-source MCP server for productivity. It runs locally on your machine and is started by your AI client.
- Pricing
- Open source
- Platforms
- CLI, API, Self-hosted
- Runs
- Locally
- Version
- 0.11.3
- Listing updated
Similar MCP servers
Install
Run in a terminal
claude mcp add caldav-mcp --env CALDAV_BASE_URL='<CALDAV_BASE_URL>' --env CALDAV_USERNAME='<CALDAV_USERNAME>' --env CALDAV_PASSWORD='<CALDAV_PASSWORD>' -- npx -y caldav-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"caldav-mcp": {
"command": "npx",
"args": [
"-y",
"caldav-mcp"
],
"env": {
"CALDAV_BASE_URL": "<CALDAV_BASE_URL>",
"CALDAV_USERNAME": "<CALDAV_USERNAME>",
"CALDAV_PASSWORD": "<CALDAV_PASSWORD>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"caldav-mcp": {
"command": "npx",
"args": [
"-y",
"caldav-mcp"
],
"env": {
"CALDAV_BASE_URL": "<CALDAV_BASE_URL>",
"CALDAV_USERNAME": "<CALDAV_USERNAME>",
"CALDAV_PASSWORD": "<CALDAV_PASSWORD>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"caldav-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"caldav-mcp"
],
"env": {
"CALDAV_BASE_URL": "<CALDAV_BASE_URL>",
"CALDAV_USERNAME": "<CALDAV_USERNAME>",
"CALDAV_PASSWORD": "<CALDAV_PASSWORD>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"caldav-mcp": {
"command": "npx",
"args": [
"-y",
"caldav-mcp"
],
"env": {
"CALDAV_BASE_URL": "<CALDAV_BASE_URL>",
"CALDAV_USERNAME": "<CALDAV_USERNAME>",
"CALDAV_PASSWORD": "<CALDAV_PASSWORD>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"caldav-mcp": {
"command": "npx",
"args": [
"-y",
"caldav-mcp"
],
"env": {
"CALDAV_BASE_URL": "<CALDAV_BASE_URL>",
"CALDAV_USERNAME": "<CALDAV_USERNAME>",
"CALDAV_PASSWORD": "<CALDAV_PASSWORD>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
CALDAV_BASE_URLBase URL of the CalDAV server (e.g. https://caldav.example.com)RequiredCALDAV_USERNAMEUsername for CalDAV authenticationRequiredCALDAV_PASSWORDPassword for CalDAV authenticationRequired
About Caldav MCP
The README describes caldav-mcp as a Model Context Protocol server that wraps a CalDAV account so an AI client can list calendars, read events in a date range, and create, change or remove events. Tasks (VTODOs) are covered too, including listing open or completed items, paging through results, and marking tasks done.
The server runs over stdio by default and is launched with npx using three environment variables: the CalDAV base URL, a username and a password. An optional Streamable HTTP mode serves POST /mcp and a health endpoint, protected by a bearer token. The README notes that each process serves a single CalDAV account and that remote use should sit behind a TLS-terminating reverse proxy.
It suits developers and power users who already keep their calendar on a CalDAV-compatible server and want an assistant to schedule, reschedule or check tasks in it.
Tools this server provides (10)
Taken from the project documentation; the running server may differ.
- list-calendars
- List all calendars returning both name and absolute URL.
- list-events
- List all events between start and end date in the calendar specified by its URL.
- create-event
- Creates an event in the calendar specified by its URL.
- update-event
- Updates an existing event in the calendar specified by its URL.
- delete-event
- Deletes an event in the calendar specified by its URL.
- list-todos
- List tasks (VTODOs) in the calendar specified by its URL.
- create-todo
- Creates a task (VTODO) in the calendar specified by its URL.
- update-todo
- Updates an existing task (VTODO) in the calendar specified by its URL.
- complete-todo
- Marks a task (VTODO) as done.
- delete-todo
- Deletes a task (VTODO) in the calendar specified by its URL.
What it does
- Calendar event management
- Lists events within a time window and creates, updates or deletes them by UID.
- Recurring event rules
- Event creation and updates accept recurrence rules with frequency, interval, weekdays and end conditions.
- Task tracking
- Lists, creates, updates, completes and deletes VTODO tasks with optional start and due dates.
- Filtered task paging
- Task listing filters by status and due window and pages results with limit and offset.
- Stdio and HTTP transports
- Runs as a local stdio process or as a bearer-token protected Streamable HTTP server.
- Docker image
- A Dockerfile is included for running the HTTP transport as a container.
Good for
- Letting an assistant check what is on the calendar for a given day or week
- Creating or moving meetings from a chat with an AI client
- Adding recurring events such as weekly standups through a recurrence rule
- Keeping a CalDAV task list up to date, such as marking items complete
- Hosting a shared calendar server for remote MCP clients behind a reverse proxy
Pricing
Open source
Free and MIT-licensed; self-hosted by the user.
Caldav MCP FAQ
Which transports does Caldav MCP support?
Stdio is the default. A Streamable HTTP mode is available with the --http flag and serves POST /mcp and GET /health.
What credentials does Caldav MCP need?
CALDAV_BASE_URL, CALDAV_USERNAME and CALDAV_PASSWORD are required environment variables. The password is marked as secret in the registry entry.
Is Caldav MCP open source?
The README states the project is licensed under MIT.
Can Caldav MCP manage tasks as well as events?
Yes. The tools cover VTODO tasks, including creating, updating, completing and deleting them.
Is Caldav MCP free?
Yes. Caldav MCP is open source, so you can use and self-host it for free.
How do I add Caldav MCP to Claude Code?
Run this command in your terminal: claude mcp add caldav-mcp --env CALDAV_BASE_URL='<CALDAV_BASE_URL>' --env CALDAV_USERNAME='<CALDAV_USERNAME>' --env CALDAV_PASSWORD='<CALDAV_PASSWORD>' -- npx -y caldav-mcp
What are the best alternatives to Caldav MCP?
The closest alternatives to Caldav MCP are Carddav MCP, To-do Calendar, Carddav MCP, Microsoft Todo MCP Server and MCP Microsoft Todo.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.
