Skip to main content
Glama
Skylight MCP Server

Skylight MCP Server

by samabenie1

Fork notice. This is a modified copy of TheEagleByte/skylight-mcp. All documentation below this notice is upstream's work unless marked otherwise. See What's different in this fork for changes made here, and CHANGELOG.md for the commit-level record.

Skylight MCP Server

An MCP (Model Context Protocol) server for the Skylight Calendar API. Enables AI assistants like Claude to interact with your Skylight family calendar, chores, lists, and more.

What's different in this fork

This fork patches the chore create/update/delete endpoints to match how the Skylight API actually behaves, and adds a manual override for Plus-only tools when using token auth.

The bugs surfaced through direct testing against a real Skylight account — including one early fix that turned out to be wrong on re-verification, corrected below rather than left standing. Chore creation goes through a bulk endpoint (POST /chores/create_multiple) with a flat, non-JSON:API body and requires an assignee (up_for_grabs is rejected outright on this API version). Chore updates are the more involved case: the original code PUT a JSON:API-wrapped body, the shape every other endpoint here uses, and against a recurring chore that returns 200 while silently changing nothing. A first fix switched to a flat body and assumed pairing it with an apply_to field would update an existing series in place. It doesn't: a flat PUT on a dated occurrence works, but always splits the series into a new chore id from that date forward, apply_to or not. The actual fix — PATCH against the series' base template id, which updates the whole series without splitting it — was identified in fergbrain/skylight-mcp, an actively maintained fork of the same upstream project, and re-verified here (including a template-id-derivation edge case their version doesn't handle) rather than taken on faith. Deleting a recurring occurrence needs apply_to or the API 400s, which was right from the start; testing it surfaced an unrelated bug where a successful delete's empty response body crashed the client's JSON parser and reported the delete as failed.

That's now fixed too, alongside create_multiple for creation, the template PATCH for whole-series updates, and a per-occurrence PUT — which reports a new chore id when it splits a series — for everything else. Separately, create_meal_sitting accepts a freeform summary for meals without a recipe, and SKYLIGHT_HAS_PLUS lets token-auth users unlock Plus-gated tools, since token auth can't read subscription status the way email/password login does.

SETUP-MAC.md is new: this fork is built and run with Bun rather than npm, and email/password login is rejected outright by Skylight's backend as of this writing, so setup here only documents the token-auth path.

A PR for the original (since-corrected) fixes was opened against TheEagleByte/skylight-mcp, then closed once it became clear that repo has had no activity in months and fergbrain's fork is where the active users are. A corrected PR — the template-PATCH mechanism and the DELETE parsing fix, both credited to where they were found or identified — is prepared in PR-DRAFT.md against fergbrain/skylight-mcp instead.

Related MCP server: Google Calendar MCP

Features

  • Calendar: Query calendar events ("What's on my calendar today?")

  • Chores: View and create chores ("Add emptying dishwasher to chores")

  • Lists: View grocery and to-do lists ("What's on the grocery list?")

  • Tasks: Add items to the task box ("Add XYZ to my task list")

  • Family: View family members and devices

  • Rewards: Check reward points and available rewards

Quick Start

Installation

mcp.json:

{
  "mcpServers": {
    "skylight": {
      "command": "npx",
      "args": ["@eaglebyte/skylight-mcp"],
      "env": {
        "SKYLIGHT_EMAIL": "your_email@example.com",
        "SKYLIGHT_PASSWORD": "your_password",
        "SKYLIGHT_FRAME_ID": "your_frame_id"
      }
    }
  }
}

Claude Code:

claude mcp add skylight npx @eaglebyte/skylight-mcp \
  -e SKYLIGHT_EMAIL=your_email@example.com \
  -e SKYLIGHT_PASSWORD=your_password \
  -e SKYLIGHT_FRAME_ID=your_frame_id

Option 2: From source

git clone https://github.com/samabenie1/skylight-mcp-fork.git
cd skylight-mcp-fork && npm install && npm run build

Then use in mcp.json:

{
  "mcpServers": {
    "skylight": {
      "command": "node",
      "args": ["/path/to/skylight-mcp/dist/index.js"],
      "env": {
        "SKYLIGHT_EMAIL": "your_email@example.com",
        "SKYLIGHT_PASSWORD": "your_password",
        "SKYLIGHT_FRAME_ID": "your_frame_id"
      }
    }
  }
}

Instructions for AI

Copy this into your AI's custom instructions or system prompt:

You have access to the Skylight MCP server. Skylight is a smart family calendar display that shows calendars, chores, grocery lists, meals, and rewards. Use the Skylight tools to help manage family schedules and organization.

Tips:

  • Call get_family_members before assigning chores to get member names

  • Grocery items default to the main grocery list if no list specified

  • Dates accept "today", "tomorrow", day names, or YYYY-MM-DD format

  • Some tools (rewards, meals, photos) require Skylight Plus subscription

Prerequisites

  • Node.js 18+

  • A Skylight account with an active subscription

  • Your Skylight Frame ID (see Finding your Frame ID)

Authentication

The MCP server supports two authentication methods:

Use your Skylight account credentials. The server will automatically log in and manage tokens.

SKYLIGHT_EMAIL=your_email@example.com
SKYLIGHT_PASSWORD=your_password
SKYLIGHT_FRAME_ID=your_frame_id

Option 2: Manual Token (Legacy)

Capture a token from the Skylight app using a proxy tool.

SKYLIGHT_TOKEN=your_token_here
SKYLIGHT_FRAME_ID=your_frame_id
SKYLIGHT_AUTH_TYPE=bearer

Finding your Frame ID

You still need to find your frame ID (the household identifier):

  1. Use a proxy tool (Proxyman, Charles, or mitmproxy)

  2. Capture any API request from the Skylight app

  3. Look at the URL path: /api/frames/{frameId}/...

  4. Example: /api/frames/abc123/chores → frame ID is abc123

Configuration

Variable

Required

Description

SKYLIGHT_EMAIL

Option 1

Your Skylight account email

SKYLIGHT_PASSWORD

Option 1

Your Skylight account password

SKYLIGHT_TOKEN

Option 2

Your API token (if not using email/password)

SKYLIGHT_AUTH_TYPE

No

bearer (default) or basic (for manual token)

SKYLIGHT_FRAME_ID

Yes

Your household frame ID

SKYLIGHT_TIMEZONE

No

Default timezone (default: America/New_York)

Example .env file:

# Email/password auth (recommended)
SKYLIGHT_EMAIL=your_email@example.com
SKYLIGHT_PASSWORD=your_password
SKYLIGHT_FRAME_ID=your_frame_id
SKYLIGHT_TIMEZONE=America/New_York

Available Tools

Calendar Tools

Tool

Description

get_calendar_events

Get calendar events for a date range

get_source_calendars

List connected calendar sources (Google, iCloud, etc.)

Chore Tools

Tool

Description

get_chores

Get chores with optional filters (date, assignee, status)

create_chore

Create a new chore with optional recurrence

List Tools

Tool

Description

get_lists

Get all available lists

get_list_items

Get items from a specific list

Task Tools

Tool

Description

create_task

Add a task to the task box

Family Tools

Tool

Description

get_family_members

Get family member profiles

get_frame_info

Get household/frame information

get_devices

List Skylight devices

Reward Tools

Tool

Description

get_rewards

Get available rewards

get_reward_points

Get reward points balance

Example Queries

Once configured, you can ask Claude things like:

  • "What's on my calendar today?"

  • "What chores do I need to do this week?"

  • "Add 'take out trash' to my chores for tomorrow"

  • "What's on the grocery list?"

  • "Add milk to my task list"

  • "Who are the family members on Skylight?"

  • "How many reward points does each person have?"

Development

# Run in development mode (with hot reload)
npm run dev

# Build
npm run build

# Run tests
npm test

# Type check
npm run typecheck

Documentation

  • SETUP-MAC.md — macOS + Claude Desktop setup for this fork, using Bun and manual-token auth.

  • CHANGELOG.md — commit-level record of what changed, upstream releases and this fork's patches both included.

API Documentation

This MCP server is built on top of the reverse-engineered Skylight API. The API endpoints were documented using the skylight-api project, which converts browser network traffic (HAR files) into an OpenAPI specification.

API Resources:

If you discover new API endpoints or find issues with the current documentation, please contribute to the skylight-api repository.

Contributing

Contributions are welcome! Here's how you can help:

  1. Fork the repository and create a feature branch

  2. Make your changes with clear, descriptive commits

  3. Run tests (npm test) and linting (npm run lint) before submitting

  4. Open a pull request with a description of your changes

Development Setup

git clone https://github.com/samabenie1/skylight-mcp-fork.git
cd skylight-mcp-fork
npm install
npm run dev  # Start with hot reload

Areas for Contribution

  • Adding support for new Skylight API endpoints

  • Improving error handling and edge cases

  • Enhancing documentation

  • Writing additional tests

Issues & Support

For issues with the changes made in this fork (chore/meal endpoints, Plus override, macOS/Bun setup):

For anything else — the base functionality this fork inherited from upstream — use upstream's issue tracker instead.

Please include relevant details like your Node.js version, error messages, and configuration (with sensitive values redacted).

License

MIT

Disclaimer

This is an unofficial integration. The Skylight API is reverse-engineered and may change without notice. Use at your own risk.

Available Tools

23 tools
create_calendar_eventA

Create a new calendar event in Skylight.

Use this when:

  • Scheduling a new event: "Add a dentist appointment on Friday at 2pm"

  • Creating family activities: "Schedule soccer practice every Saturday at 10am"

  • Adding reminders: "Put Mom's birthday on the calendar"

Parameters:

  • summary (required): Event title (e.g., "Dentist Appointment")

  • startsAt (required): Start time in ISO format or natural language

  • endsAt (required): End time in ISO format or natural language

  • allDay: Set to true for all-day events

  • description: Additional notes for the event

  • location: Where the event takes place

  • categoryIds: Family member IDs to associate with the event

Returns: The created event details.

Related: Use get_family_members to get category IDs for assignments.

Inputs: endsAt (required), summary (required), startsAt (required), allDay, +3 more.

create_choreA

Add a new chore to Skylight.

Use this when the user wants to:

  • Add a new task like "empty the dishwasher"

  • Assign chores to family members

  • Create recurring chores

The chore will appear on the Skylight display. An assignee is required — this account's Skylight API version rejects unassigned ("up for grabs") chores outright, so there is no way to create one without an assignee.

Inputs: summary (required), assignee (required), date, time, +3 more.

create_listA

Create a new list in Skylight.

Use this when:

  • Creating a new shopping/grocery list

  • Creating a new to-do list

Parameters:

  • label (required): Name of the list (e.g., "Vacation Packing", "Weekly Groceries")

  • kind (required): "shopping" for grocery/shopping lists, "to_do" for task lists

  • color: Optional color for the list

Returns: The created list details.

Inputs: kind (required), label (required), color.

create_list_itemA

Add an item to a Skylight list.

Use this when:

  • Adding something to the grocery list: "Add milk to the shopping list"

  • Creating a to-do item: "Put 'call doctor' on my to-do list"

  • Adding items to any list

Parameters:

  • label (required): The item text (e.g., "Milk", "Call doctor")

  • listId: ID of the list to add to

  • listName: Name of the list to add to (e.g., "Grocery List")

  • section: Category within the list (e.g., "Dairy", "Produce")

If no list is specified, adds to the default grocery list.

Returns: Confirmation of the added item.

Related: Use get_lists to see available lists and their IDs.

Inputs: label (required), listId, section, listName.

create_taskA

Add a task to the Skylight task box.

The task box holds unscheduled tasks that can later be assigned to specific dates.

Use this when the user says:

  • "Add XYZ to my task list"

  • "Remind me to do ABC" (without a specific date)

  • "Put 'clean garage' on the task box"

The task will appear on the Skylight display in the task box.

Inputs: summary (required), emoji, routine, rewardPoints.

delete_calendar_eventA

Delete a calendar event from Skylight.

Use this when:

  • Canceling an event: "Remove the dentist appointment"

  • Deleting old events: "Delete the meeting from yesterday"

Parameters:

  • eventId (required): ID of the event to delete (from get_calendar_events)

Note: This permanently removes the event. For recurring events, this may only delete one instance.

Inputs: eventId (required).

delete_choreA

Delete a chore from Skylight.

Use this when:

  • Removing an old or irrelevant chore

  • Deleting a chore that was added by mistake

  • Removing a recurring chore series, or ending it from a given date onward

Parameters:

  • choreId (required): ID of the chore to delete (from get_chores)

  • applyTo: Required for recurring chores, ignored for one-off chores.

    • "all": delete every occurrence of the recurring series

    • "future": delete this occurrence and every later one, keeping past occurrences intact There is no way to delete a single recurring occurrence while leaving later ones in place — the Skylight API only supports "all" or "future" for recurring chores.

Note: This permanently removes the chore(s). Deleting a recurring chore without applyTo will fail with an error asking for one.

Inputs: choreId (required), applyTo.

delete_listA

Delete a list from Skylight.

Use this when:

  • Removing an old or unused list

  • Deleting a temporary list

Parameters:

  • listId: ID of the list to delete (use get_lists to find IDs)

  • listName: Name of the list to delete (alternative to listId)

Note: This permanently deletes the list and all its items.

Inputs: listId, listName.

delete_list_itemA

Remove an item from a list.

Use this when:

  • Removing an item that was added by mistake

  • Deleting an item instead of marking it complete

Parameters:

  • itemId (required): ID of the item to delete

  • listId (required): ID of the list containing the item

Note: This permanently removes the item. Use update_list_item with status="completed" to check it off instead.

Inputs: itemId (required), listId (required).

get_avatarsA

Get available avatar options for Skylight profiles.

Use this when:

  • Setting up a new family member profile

  • Changing someone's profile picture

  • Exploring available avatar options

Returns: List of available avatars with their IDs and details.

Inputs: no named parameters.

get_calendar_eventsA

Get calendar events from Skylight.

Use this to answer questions like:

  • "What's on my calendar today?"

  • "What do we have scheduled this weekend?"

  • "Are there any events on Friday?"

Returns a list of events with their titles, times, and details.

Inputs: date, dateEnd.

get_choresA

Get chores from Skylight.

Use this to answer:

  • "What chores do I need to do today?"

  • "Show me this week's chores"

  • "What's on the chore chart?"

  • "What chores does [name] have?"

Returns chores with their IDs (needed for update_chore/delete_chore), assignees, due dates, and completion status.

Inputs: date, status, dateEnd, assignee, +1 more.

get_colorsA

Get available color options for Skylight profiles and lists.

Use this when:

  • Choosing a color for a family member profile

  • Setting a list color

  • Exploring available color options

Returns: List of available colors with their IDs and hex values.

Inputs: no named parameters.

get_devicesA

List Skylight devices in the household.

Use this to answer:

  • "What Skylight devices do we have?"

  • "How many Skylight frames are connected?"

Inputs: no named parameters.

get_family_membersA

Get family members/profiles from Skylight.

Shows who can be assigned chores and their profile details.

Use this to answer:

  • "Who's in our family on Skylight?"

  • "What family members are set up?"

  • "Who can I assign chores to?"

Inputs: no named parameters.

get_frame_infoA

Get Skylight household/frame information.

Useful for setup verification and debugging.

Use this to answer:

  • "Show Skylight household info"

  • "What's my frame ID?"

Inputs: no named parameters.

get_list_itemsA

Get items from a specific Skylight list.

Use this to answer:

  • "What's on the grocery list?"

  • "Show me my to-do list"

  • "What items are on [list name]?"

Returns items organized by section with their completion status.

Inputs: listName, listType, includeCompleted.

get_listsA

Get all lists from Skylight (grocery lists, to-do lists, etc.).

Use this to see what lists are available before adding items. Returns list names, types (shopping/to_do), and item counts.

Inputs: no named parameters.

get_source_calendarsA

Get connected calendar sources synced to Skylight.

Use this to answer:

  • "Which calendars are synced to Skylight?"

  • "What calendar accounts are connected?"

Returns a list of connected calendar sources (Google, iCloud, etc.).

Inputs: no named parameters.

update_calendar_eventA

Update an existing calendar event.

Use this when:

  • Changing event time: "Move the dentist appointment to 3pm"

  • Updating event details: "Add location to the meeting"

  • Renaming an event: "Change 'Doctor' to 'Dr. Smith checkup'"

Parameters:

  • eventId (required): ID of the event to update (from get_calendar_events)

  • summary: New title for the event

  • startsAt: New start time (ISO format)

  • endsAt: New end time (ISO format)

  • description: Updated notes

  • location: Updated location

  • categoryIds: Updated family member assignments

Returns: The updated event details.

Inputs: eventId (required), allDay, endsAt, summary, +4 more.

update_choreA

Update an existing chore in Skylight.

Use this when:

  • Marking a chore as complete: "Mark 'dishes' as done"

  • Changing chore assignment: "Reassign the trash to Dad"

  • Updating chore details: "Change the time for the homework chore"

  • Shifting which day(s) a recurring chore falls on: "Move trash day to Wednesday"

Parameters:

  • choreId (required): ID of the chore (from get_chores)

  • summary: New description for the chore

  • status: "completed" to mark done, "pending" to mark incomplete

  • date: New due date. IMPORTANT: for a recurring chore, changing date alone does NOT shift which day(s) it recurs on — the API keeps generating occurrences on the old RRULE weekday regardless of the new date. To actually move a recurring chore's day, also pass recurrencePattern with a matching RRULE (e.g. date="2026-08-26" + recurrencePattern="RRULE:FREQ=WEEKLY;BYDAY=WE" to move it to Wednesdays), and pass applyTo.

  • recurrencePattern: New recurrence rule for a recurring chore ('daily', 'weekly', 'weekdays', or a raw RRULE string like 'RRULE:FREQ=WEEKLY;BYDAY=WE'). Use this to actually change a recurring chore's day(s) — date alone won't do it.

  • applyTo: Required for any change to a recurring chore, or the API silently ignores the whole update (200 response, nothing actually changes, no error). Not needed for one-off chores.

    • "all": apply to every occurrence of the series

    • "future": apply to this occurrence and every later one, past occurrences untouched

  • time: New due time

  • assignee: New family member assignment. There is no way to unassign a chore on this account (up_for_grabs is rejected by the API) — assignee can only be reassigned to another family member, never cleared.

Returns: The updated chore details. If any requested field didn't actually change (most commonly: a recurring chore updated without applyTo), this returns an error instead of a false "Updated" success, listing exactly which fields didn't take.

Inputs: choreId (required), date, time, status, +5 more.

update_listA

Update an existing list's name or settings.

Use this when:

  • Renaming a list

  • Changing a list's type or color

Parameters:

  • listId: ID of the list to update (use get_lists to find IDs)

  • listName: Name of the list to update (alternative to listId)

  • label: New name for the list

  • kind: New type ("shopping" or "to_do")

  • color: New color for the list

Returns: The updated list details.

Inputs: kind, color, label, listId, +1 more.

update_list_itemA

Update a list item (mark complete, rename, move to section).

Use this when:

  • Marking an item as complete: "Check off milk from the list"

  • Renaming an item: "Change 'milk' to '2% milk'"

  • Moving an item to a different section

Parameters:

  • itemId (required): ID of the item to update

  • listId (required): ID of the list containing the item

  • label: New text for the item

  • status: "completed" to check off, "pending" to uncheck

  • section: Move to a different section

Returns: The updated item details.

Inputs: itemId (required), listId (required), label, status, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool maps cleanly to a distinct resource-action pair, such as calendar events, chores, lists, list items, family members, and devices. The few conceptually similar tools like create_task, create_chore, and create_list_item are separated by clear descriptions about where each item belongs.

    Naming Consistency5/5

    All tool names consistently follow the snake_case verb_noun pattern, with get_/create_/update_/delete_ prefixes applied predictably across resources. Even auxiliary tools like get_frame_info, get_devices, get_avatars, and get_colors fit the same naming style without deviation.

    Tool Count4/5

    At 23 tools, this is above the typical 3-15 range and feels somewhat heavy for a single server. However, the server spans multiple distinct domains—calendar, chores, lists, task box, family profiles, and devices—so most tools have a clear purpose and the breadth is largely justified.

    Completeness2/5

    Calendar, chores, and lists have solid CRUD coverage, but the task box has only create_task with no way to read, update, or delete tasks, creating a dead end. Family member/profile management is also read-only despite get_avatars and get_colors being positioned as setup tools.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers