carddav-mcp
Related Servers
Alternatives to carddav-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA CardDAV MCP server that exposes contacts and address books as tools for AI assistants.12 npm1MIT
- AlicenseBqualityBmaintenanceEnables managing Infomaniak kSuite contacts, calendars, and reminders over CalDAV and CardDAV through the Model Context Protocol, with no third-party dependencies.9MIT
- AlicenseAqualityDmaintenanceEnables full CRUD operations on calendar events, free/busy queries, and availability slot finding via CalDAV, supporting Nextcloud, Radicale, iCloud, and other RFC 4791-compliant servers.8MIT
- AlicenseNot gradedqualityFmaintenanceEnables AI assistants to manage contacts with full CRUD, dedup, merge, import/export, sync with Google/Apple/CardDAV, and git-backed rollback.7 npmAGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables CRUD operations for calendar events, journal entries, and todos on any CalDAV server (like Radicale) through the Model Communication Protocol.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for the Infomaniak Contacts API, enabling listing and searching contacts across address books.67 npm3MIT
TDQS
Scored across 17 tools
Each tool has a distinct purpose: listing, searching, syncing, fetching, exporting, creating, updating, deleting, and moving contacts/groups are clearly separated. Even closely related tools like list_contacts and search_contacts differ in filtering behavior, while get_contact and get_contact_photo split parsed data from binary images.
Tool names follow a consistent verb_noun pattern: list_, get_, create_, update_, delete_, search_, export_, and move_. The object is always the second element (contacts, groups, changes, server_info, address_books), making the API predictable and easy to navigate.
At 17 tools, the set is slightly above the typical 3–15 range, but the count is justified by covering CRUD for both contacts and groups plus search, sync, export, photo retrieval, and server info. No tool feels redundant; each earns its place, though a few could theoretically be merged without major harm.
The tool surface fully covers the CardDAV contact and group lifecycle: listing address books, server capability checks, listing/searching/getting/exporting contacts, creating/updating/deleting/moving contacts, and managing groups. The inclusion of list_changes and get_server_info addresses sync and compatibility edge cases, leaving no obvious dead ends for common client workflows.