cdeck-mcp
Related Servers
Alternatives to cdeck-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceConnects Claude to Things 3 on macOS, allowing to add to-dos and projects, search, open lists, and read Today/Upcoming/Inbox via natural language.5 npmMIT
- AlicenseNot gradedqualityBmaintenanceLets you dictate or scribble ideas on an Apple Watch that are end-to-end encrypted and relayed to a running Claude Code session, which then acts on them autonomously while you're away. Delivered notes arrive as channel events or are polled into the session, with results summarized back to disk once each task is finished.614 npmMIT
- AlicenseAqualityAmaintenanceEnables Claude to interact with Apple services including Email, Calendar, Contacts, Reminders, Notes, Messages, and Safari via AppleScript (macOS) or iCloud protocols.41107 npm69MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude or any MCP client to create and list reminders, mark reminders done, list Reminders lists, and create Apple Notes on macOS through local AppleScript, without sending data to the cloud.40 npmMIT
- AlicenseBqualityAmaintenanceConnects Claude Code to Apple Mail, Calendar, and Reminders through macOS automation APIs, enabling management of emails, events, and reminders via natural language.13324 npmMIT
- AlicenseBqualityBmaintenanceEnables Claude to interact with Apple apps on macOS including Mail, Calendar, Contacts, Reminders, Notes, and iCloud Drive for personal productivity tasks like triaging email, managing calendar, and cross-app context.768MIT
TDQS
Scored across 6 tools
Each tool targets a distinct action in the pairing/deck lifecycle: pair, list, unpair, push, status, and schema. The only potentially adjacent tools, cdeck_list and cdeck_status, are clearly separated as listing paired TVs versus inspecting deck update state and acks.
All tool names use the same cdeck_ prefix and snake_case convention. The suffixes are concise and consistently readable, even when mixing verbs (pair, push, list) and noun-like tools (schema, status).
Six tools is well-scoped for this server: pairing lifecycle, schema guidance, push, and status. No tool appears redundant or out of place.
The surface covers the core workflow: schema discovery, pairing, listing, unpairing, pushing a deck, and checking acks/status. A minor gap is the absence of a direct tool to read back the current deck, though status plus source-side ack handling may be sufficient for the intended workflow.