A
licenseD
qualityD
maintenanceA Model Context Protocol server that allows users to interact with their CalDAV, CardDAV, and WebDAV services (calendars, contacts, and files) from Fastmail and Apple iCloud accounts.
6
56 npm
3
MIT
infomaniak-mcp
Related Servers
Alternatives to infomaniak-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables CRUD operations for calendar events, journal entries, and todos on any CalDAV server (like Radicale) through the Model Communication Protocol.MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables direct integration with macOS Calendar application using AppleScript, allowing users to create, list, and search calendar events without requiring OAuth setup.86MIT
- AlicenseNot gradedqualityDmaintenanceAn HTTP Model Context Protocol (MCP) server exposing iCloud Calendar (CalDAV) tools so MCP-aware clients can list calendars, read events, and create/update/delete events using an iCloud app-specific password.3MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server for managing iCloud Calendar events, supporting multiple alarms and both stdio and Streamable HTTP transports.6295 npm3MIT
- AlicenseNot gradedqualityAmaintenanceProvides native integration with Apple Reminders and Calendar on macOS, enabling full CRUD operations and smart task management through the Model Context Protocol. It allows users to search, create, and organize reminders and calendar events using natural language via the macOS EventKit framework.271 npm208MIT
TDQS
B3.3/5.0
Scored across 9 tools
Disambiguation5/5
Each tool targets a distinct resource and action: collections, contacts, events, and tasks are cleanly separated. There is no meaningful overlap between search_contacts and the calendar/task operations.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern such as list_events, create_contact, delete_event. The naming is predictable and uniform across the entire surface.
Tool Count5/5
Nine tools is well scoped for a contacts and calendar server. Each tool covers a clear need without unnecessary duplication or bloat.
Completeness3/5
The domain is covered for basic listing, creating, and in some cases deleting, but notable lifecycle gaps exist: contacts have no update or delete, events have no update, and tasks have no delete. Agents can accomplish core workflows but will hit dead ends when trying to modify existing contacts or rearrange events.
Maintenance
ActivityMaintained
ResponsivenessNo issues