Skylight MCP Server
Related Servers
Alternatives to Skylight MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceMCP server for Skylight Calendar family hub, providing over 100 tools to manage events, lists, chores, meals, messages, albums, and device settings.41142,732 npm17MIT
- AlicenseNot gradedqualityBmaintenanceEnables a proactive household assistant to manage calendar events, pantry and meal plans, predict grocery run-outs, build consent-based simulated orders, and expose interactive MCP Apps views through tools and resources.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables mixed-schedule families to coordinate quiet hours, meals, chores, calendar events, nudges, and wake briefings through an MCP client such as a living-room Alexa+ Show simulator.7 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables households to maintain a shared, persistent family memory for tracking item locations, warranty dates, chores, and who said what and when. It exposes this memory to AI assistants and tooling through MCP-compatible endpoints.8,431 npmMIT
- AlicenseNot gradedqualityBmaintenanceUnofficial MCP server for Skylight Calendar that enables calendar, task, list, meal, and profile management through typed commands and SDK integration.36 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables MCP-compatible clients like ChatGPT and Claude to manage a household's shared food inventory, meal plans, recipes, and preferences through natural language, with atomic updates and audit logging.-
TDQS
Scored across 30 tools
Most tools target clearly distinct resources and actions, and descriptions explicitly clarify boundaries like create_task vs create_chore vs create_list_item. The main overlap is get_week_overview duplicating individual getters for calendar, chores, and lists, plus possible confusion between dedicated conflict/free-slot tools and overview features.
Names consistently use snake_case and a predictable verb_noun pattern: get_*, create_*, update_*, delete_*, plus send_message and plan_week_meals. The special verbs still fit the resource-oriented convention and do not introduce inconsistent casing or styles.
The server covers several distinct domains (calendar, chores, lists, messages, meals, profiles/devices), so many CRUD tools are justified. However, 30 tools is heavy for an MCP surface, and some metadata getters or aggregate/individual overlaps could likely be consolidated.
Calendar events, chores, lists, and list items have full CRUD coverage, and messages are well covered given the permanent-post limitation. Notable gaps remain around tasks (create only, with no standalone update/delete) and meals (planning exists, but retrieval/update/delete lifecycle is thin).