Caldav MCP vs Site
A side-by-side look at the Caldav MCP and Site MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SiteWorkplace & ProductivityEmployeeDeskHQ: the site's own MCP server — dataset; every answer cites the site.43FairAuth: no auth requiredVerdict: choose Caldav MCP for workplace & productivity work as a local process; choose Site for workplace & productivity. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Caldav MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You have the keys it needs:
CALDAV_BASE_URL, CALDAV_USERNAME, CALDAV_PASSWORD. - You want tools like
start, end, calendarUrl.
SChoose Site when
- You need dedicated capabilities in the Workplace & Productivity domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S Site | |
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 63/100 · Good | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | other | No auth required |
| Pricing | Free | Free |
| Required env vars | CALDAV_BASE_URLCALDAV_USERNAMECALDAV_PASSWORD | None listed |
Tools & capabilities
Caldav MCP tools 22
startstring — Start date (ISO 8601)endstring — End date (ISO 8601)calendarUrlstringsummarystringwholeDayboolean (optional) — Create as a whole-day eventdescriptionstring (optional)locationstring (optional)recurrenceRuleobject (optional)freqenum (`DAILY` | `WEEKLY` | `MONTHLY` | `YEARLY`) (optional)intervalnumber (optional)countnumber (optional)untilstring (optional)- +10 more on the listing page
Site tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Caldav MCP
{
"mcpServers": {
"caldav-mcp": {
"command": "npx",
"args": [
"caldav-mcp"
],
"env": {
"CALDAV_BASE_URL": "YOUR_CALDAV_BASE_URL_HERE",
"CALDAV_USERNAME": "YOUR_CALDAV_USERNAME_HERE",
"CALDAV_PASSWORD": "YOUR_CALDAV_PASSWORD_HERE"
}
}
}
}
Site
No confirmed install command for Site yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Caldav MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Site belongs to Workplace & Productivity and uses an install path we have not confirmed yet. Pick Caldav MCP for workplace & productivity work and Site for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Site has no confirmed install command yet — follow its own setup instructions.
Caldav MCP is listed as free. Auth: other. Site is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add caldav-mcp and site-83 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Caldav MCP has a quality signal of 63/100 (Good) with 2 views, 0 installs and 103 GitHub stars. Site has 43/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.