Technology

Skylight MCP, Part 5: Prep Reminders That Actually Reach My Phone

The meal plan was on the kitchen frame, but the prep and start-time reminders never left it. Here's the upstream change that lets the Skylight MCP create events on a synced Google or Apple calendar.

In Part 3, the last step of planning a week was Claude dropping reminders on my calendar: a 9:30 PM prep reminder the night before each slow-cooker dinner, a start-time reminder for the afternoon, and the occasional THAW or SHOP. I described a little dance to get them onto my personal Google calendar (switch the frame's default calendar to mine, create the events, switch it back). (Those Google calendars are the same ones I mapped to Skylight profiles when we first set up the frame.)

But NOPE! That dance didn't do what I thought it did. This post is about figuring out why, and the pull request that fixed it properly.

Why the reminders matter

The whole plan hinges on two moments that happen when nobody is thinking about dinner:

  • The night before, when the pots get loaded.
  • Mid-afternoon on a sports night, when someone has to press Start. The MultiPot has no delay start and can't go on a smart plug (see Part 2), so if that moment gets missed, dinner is cereal.

A reminder that lives only on the kitchen frame is useless for the second one. The frame can't buzz my wrist while I'm at my desk. It has to land on a real calendar, the one my phone already nags me about.

What was actually happening

The reminders showed up on the Skylight just fine. They never showed up in Google Calendar. When Claude read one back right after creating it, the event had calendar_id: null and a source of skylight. I'd waved that off as sync lag. It wasn't.

skylight_create_event had no way to name a target calendar, so every event it made was Skylight-only. And the "switch the default calendar first" trick was built on a wrong assumption: the frame's default-for-new-events setting is something the app reads when it builds its request. The server doesn't apply it. An event created through the API with no calendar named stays on the frame, default or no default.

Lesson Learned: A 200 response is not the same thing as "it worked." Read the object back and check the field you actually care about.

Why not just give Claude my calendar?

There's an obvious shortcut here. Claude has a Google Calendar connector. Turn on read/write, have Claude create the reminders directly in Google, and skip Skylight entirely.

I didn't want to do that, and the reason is permissions. Read/write on the calendar connector isn't scoped to "add a reminder." It's everything: edit any event, delete any event, and delete entire calendars, not just the events on them. That's a lot of access to hand over so a pot roast can remind me to press Start.

Routing the write through the Skylight MCP gives me a much smaller footprint:

Calendar connector, read/write Skylight MCP + calendar connector, read-only
Create and remove events Yes Yes (through Skylight, on calendars linked to the frame)
Delete a whole calendar Yes No
Touch calendars not linked to the frame Yes No
Verify the event landed Yes Yes (read it back from Google directly)

So the Google Calendar connector stays read-only. The MCP does the write, and then Claude uses the read-only connector to confirm the event really showed up in Google. That's the "read the object back" lesson from above, with a second, independent source. If something goes sideways, the worst case is a few stray events on calendars I already chose to link to the kitchen frame.

It's the same least-privilege thinking I'd apply to any service account at work. It just happens to be guarding the family calendar.

Proving it before patching it

Same approach as the rewards fix in Part 4: get evidence first. I had Claude post the same test event to the calendar-events endpoint three ways and compare what came back.

Request body carries What came back
Neither field source: "skylight", calendar_id: null
calendar_id only Identical to the row above. A 200, with the field silently ignored
calendar_id + calendar_account_id source: "google", calendar_id set, and the event's uid is the Google event ID

That middle row is the nasty one. You send a calendar, you get a success, and the event quietly goes nowhere.

The third row is the answer. Seconds after that request, Claude read the event straight out of Google Calendar (through that read-only connector) with the same ID. So the API needs two values: the calendar itself and the account it belongs to.

Finding the second value took some digging. calendar_account_id isn't an attribute on anything. It only exists as a relationship on each source calendar, and (stop me if you've heard this one) the MCP server's generic JSON:API flattener throws relationships away. Same root cause as the missing reward owner in Part 4, different resource.

One more finding worth writing down: you can't fix an existing event after the fact. A PUT with both fields returns 200 and leaves a Skylight-only event exactly where it was. The calendar is a create-time decision.

The fix

PR #281 adds one optional parameter to skylight_create_event:

{
  "summary": "START: Pot Roast (both zones, Slow Cook HI 4:00)",
  "starts_at": "2026-11-17T15:15:00",
  "ends_at": "2026-11-17T15:30:00",
  "timezone": "America/New_York",
  "calendar_id": "<source_id from skylight_list_source_calendars>"
}

The design decisions I cared about:

  1. The caller never touches the account ID. You pass the calendar's source_id (for Google, that's the calendar address). The server looks up the matching source calendar and adds the account ID to the request itself. One less thing for the model to get wrong.
  2. Refuse instead of failing silently. If the calendar is unknown, read-only, or has no account behind it, the tool stops before the write and lists the calendars that do accept events. Sending it anyway would return a 200 with a Skylight-only event, which is the exact bug this parameter exists to fix.
  3. No behavior change if you don't use it. Leave calendar_id off and the server sends the same request it always did, with no extra lookup.
  4. Create only. skylight_update_event doesn't get the parameter, on purpose, since an update can't move an event.

I also decided not to fall back to the frame's default calendar when calendar_id is omitted. It would match what the app does, but it changes behavior for everyone already using the tool and adds a lookup to every create. That felt like the maintainer's call, so I flagged it in the PR as an easy follow-up rather than sneaking it in.

In fairness, I could only test against Google calendars, and I said so in the PR. The maintainer picked that up, verified it works unchanged against Apple iCloud (CalDAV) calendars, and merged it the same day. That's a good open source day.

What it looks like in the weekly plan

The config doc from Part 2 now carries one more value: the source_id of the calendar reminders should land on. The "AFTER I APPROVE" block of the weekly prompt gets a line that says to create every reminder with that calendar_id. The switch-the-default dance is gone.

A sports-night dinner now produces three things:

Where What When
Skylight meal plan PREP entry with the prep steps The night before
My calendar (synced) "PREP: Pot Roast" reminder 9:30 PM the night before
My calendar (synced) "START: Pot Roast (both zones, HI 4:00)" reminder 3:15 PM, the latest it can go in

The start time is the part I like most. It isn't a fixed time of day. It's dinner time minus the cook time from the recipe's SYNC footer, so chicken on HI 3:00 and chuck on HI 4:00 get different reminders without me doing the math. Oven nights work the same way: preheat and "in the oven" reminders come off the recipe's own timing.

And because these are real Google events now, they show up on the frame too (it syncs that calendar), on my phone, and on my watch. One write, three screens.

What's next

The remaining rough edge is cleanup. When a night changes mid-week, the old reminders have to be found and deleted before new ones get created, and right now that's a "list the week, match by title" exercise. Workable, but I can see another PR in my future.

Comments welcome!

Read More...

2026.11 Skylight MCP, Part 1: The Problem and the SetupOur recipes live in Apple Notes, our calendar lives on a Skylight, and the glue between them was me clicking buttons. Here's how an MCP server and Claude turned that into a conversation. 2026.11 Skylight MCP, Part 2: Teaching Claude How We PlanProject docs for stores, grocery rules, meal-planning rules, and a recipe format. The rules are what make the automation actually useful. 2026.11 Skylight MCP, Part 3: Planning a Real WeekOne prompt, a menu table, a few rounds of corrections, and then Claude writes the recipes, the meal plan, the prep reminders, and a sectioned grocery list.