skylight-mcp
Related Servers
Alternatives to skylight-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceUnofficial MCP server for Skylight Calendar that enables calendar, task, list, meal, and profile management through typed commands and SDK integration.57 npm1MIT
- AlicenseNot gradedqualityFmaintenanceA comprehensive MCP server that provides AI assistants with natural language access to Apple Calendar, enabling reading, searching, creating, and managing calendar events.3MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that seamlessly interacts with your Google Calendar, Gmail, Drive and so on.30MIT
- AlicenseAqualityDmaintenanceMCP server for privacy-gated local Apple data access including Mail, Messages, Notes, Calendar, Contacts, Photos, Reminders, Voice Memos, and iCloud Drive.301MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Apple Calendar, Mail, Reminders, and Files on macOS using native frameworks.16 npm21MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for Google Calendar that enables listing, creating, updating, and deleting events, quick-add from natural language, responding to invitations, and checking availability across multiple accounts.MIT
TDQS
Scored across 114 tools
Most tools target a clearly distinct resource+action, and the descriptions do unusually heavy lifting to separate near-pairs (delete_message vs delete_messages, list_auto_creation_drafts vs list_auto_creation_items, complete_chore vs complete_chore_instance). However, with 114 tools there are several genuinely confusable clusters — update_category vs update_family_member, list_calendars vs list_source_calendars vs list_events, and frame vs profile vs household updates — so an agent can still misfire occasionally.
Every tool uses the same skylight_ prefix followed by a predictable verb_noun pattern (list_, get_, create_, update_, delete_, complete_, set_, add_, remove_). The handful of non-CRUD verbs (healthcheck, resolve_member, rename_frame) still fit the convention. No mixed casing or stray styles.
114 tools is far beyond any reasonable ceiling for a single server, even one covering a family hub's calendar, chores, rewards, meals, photos, lists, devices and AI generation. The broad domain justifies many tools, but this surface is heavy enough that discovery and selection become burdensome.
Coverage is exhaustive: full CRUD plus lifecycle operations across frames, users, categories/members, chores (incl. recurrences and completion), rewards and points, meals/recipes, messages/albums, tasks, lists, events, source calendars, devices, config, and AI generation with draft review/approval. Even edge operations like redeeming, unredeeming, undoing AI intents, and a diagnostic healthcheck are present.