skylight-mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
skylight-mcp
What it is
skylight-mcp is a local MCP server that lets an AI assistant such as Claude Desktop manage chores, routines, rewards, lists, calendar events, the meal plan and recipes, photos and albums, devices, frame settings and sharing on a Skylight Calendar. It runs on your Mac over stdio and talks to Skylight's web API. The same tools can also run as a shared server on Cloudflare Workers for Claude, ChatGPT and Gemini on any device (see "Use from Claude, ChatGPT and Gemini on any device").
To set it up, follow the step-by-step setup guide. It goes from git clone to a working assistant and shows what each command prints along the way.
It runs on macOS only, because the login credential is stored with the macOS Keychain and the sign-in step reads Google Chrome's history.
Related MCP server: skylight-mcp
Use at your own risk
This is an unofficial project. It is not affiliated with, endorsed by or supported by Skylight.
It uses Skylight's private API, which is undocumented. Skylight can change or block it at any time without notice, and every tool here can stop working the same day.
Using a private API this way may be against Skylight's terms of service. Skylight could suspend or close an account that uses it. Read their terms and decide for yourself.
The tools change real family data. Deleting events, chores, lists, recipes, profiles and photos is permanent, and deleted photos are gone for everyone who shares the frame. The confirm gates reduce accidents; they do not undo them.
An AI assistant decides which tools to call. It can misread a request and change the wrong thing. Review what it proposes before you approve it.
You run it yourself. There is no hosted service: the Mac server runs on your Mac, and the shared server runs in your own Cloudflare account with your own Google sign-in client. You are responsible for its secrets, its costs and who you let in.
There is no support and no promise of fixes. The software is provided as is, with no warranty of any kind, under the MIT licence (see
LICENSE).
Safety
The tool set is deliberate, not complete. Profiles (Skylight categories) can be created, updated and deleted; rewards, lists and calendar events (phase 2) can be created, changed and deleted; and phase 3 adds the meal plan and recipes, photos and albums, devices, frame settings and sharing, and the plan and marketing flag. Every destructive action is confirm-gated. Never exposed: account delete or export, email or password change, frame transfer, alarms and sleep schedules, device config, renaming or hiding the frame, push-notification preferences, and who can see the family's photos (
open_to_publicandmessage_viewability: their values are unverified and a wrong one could publish photos).Photo files and links (
asset_url,thumbnail_url), share links, the frame's notification email and the account's email, phone, birthday and name are never returned by any tool.skylight_list_photosreturns ids, dates, captions and who sent each photo, nothing that opens the file.fromis"you"for photos the frame owner sent (the owner's own email is never returned) and the sender's email for everyone else, which is how Skylight identifies people outside the household; if the owner cannot be identified,fromis null.Deleting photos is permanent and removes them for everyone who shares the frame.
skylight_delete_photosneedsconfirm: true; its preview lists each photo's date and caption and refuses ids that are not on the frame. Deleting an album keeps its photos on the frame.Resetting or removing a device is the most disruptive thing the server can do (a reset wipes the screen; a removed device leaves the frame).
skylight_reset_deviceandskylight_remove_deviceneed BOTHconfirm: trueandconfirmName, the device's exact current name (case-sensitive); anything less returns a preview and changes nothing, and a wrong name is refused with the expected one.Some actions send real email to people outside the family, so they are confirm-gated too:
skylight_invite_frame_user(confirm: true) and an event'sinvitedEmails(confirmInvites: true, onskylight_create_eventandskylight_update_event). Without the flag you get a preview of the addresses and nothing is created, changed or sent.skylight_block_frame_useris confirm-gated and refuses the frame owner.Meals and recipes:
skylight_delete_mealneedsconfirm: trueand names the date and scope in its preview; a repeating meal always needs an explicitapplyTo.skylight_delete_recipeneedsconfirm: true; its preview counts the distinct meals planned with the recipe in the next 60 days (and the dates they cover, e.g. "2 meals (61 dates)") and says whether they would be deleted (alsoDeletePlannedMeals, default false). WithalsoDeletePlannedMeals: trueit also warns that meals planned further out with the recipe would be deleted too.Calendar events synced from Google or another calendar are read-only here:
skylight_update_eventandskylight_delete_eventrefuse them (sourceother thanskylight) before sending any request.Deleting a chore requires
confirm: true. Without it,skylight_delete_chorechanges nothing and returns a preview of what would be deleted.Deleting a reward, a list, list items or a calendar event works the same way: the delete tools need
confirm: trueand otherwise return a preview (reward and list details, the titles of the items, or the scope and a warning when a whole recurring series would go). Deleting a list deletes its items. A recurring event deleted by its plain id, or withapplyTo: "all", removes the whole series.skylight_redeem_rewardspends points, so it is confirm-gated too and its preview shows the current balance.Deleting a profile works the same way:
skylight_delete_profileneedsconfirm: true, and its preview shows the upcoming chore count and where chores and events would go. To retire a person without losing their events, useskylight_update_profilewithkind: "label"(Skylight's "Convert to Label").Bulk create validates every item before sending any request, supports
dryRun: true, and stops early if Skylight rejects the login or rate limits the requests.Tokens are stored encrypted with AES-256-GCM. The encryption key lives in the macOS Keychain. Any process running as your user can read that key through
/usr/bin/securitywithout a prompt, so the encryption protects backups and the file at rest, not against malware on the Mac.On the shared server (Claude, ChatGPT and Gemini over the internet), every call of a tool that can change something is logged with the family member who made it (ids only, 90 days); see "Use from Claude, ChatGPT and Gemini on any device".
Tokens, codes and keys are never written to logs and never returned in tool results.
statusanddoctorprint no token values.The OAuth token Skylight issues has full-account scope. The tool layer here is narrow, but the token itself is not. Treat the stored credential as sensitive, and run
skylight-mcp logoutto remove it.
Setup guide
If this is your first time, use the step-by-step guide instead of the shorter sections below. It lists what you need, gives every command in order, shows the output to expect, and has a table of error messages with what to do about each.
docs/setup-guide.md reads right here on GitHub.
docs/setup-guide.html is the same guide as a web page, with copy buttons, a checklist that remembers where you stopped, and a field that fills your server's address into every command. GitHub shows HTML files as source code, so open it from your clone instead:
open docs/setup-guide.html.
The short version, for one Mac and Claude Desktop:
Clone the repository, install and build it: Install.
Sign in to Skylight with
skylight-mcp login: Login.Run
skylight-mcp doctorand paste the config it prints into Claude Desktop: Claude Desktop setup.Quit and reopen Claude Desktop, then ask it what chores are on your Skylight.
The shared server for the rest of the family is Part 2 of the guide and is described under Use from Claude, ChatGPT and Gemini on any device.
Install
The package is named @jordanlawson/skylight-mcp but it is not published to npm. Install from source. Node 20 or newer is required.
git clone https://github.com/jordanlawson1988/skylight-mcp-public skylight-mcp
cd skylight-mcp
npm install
npm run build
npm linknpm link makes the skylight-mcp command available on your PATH. Commands: login, logout, status, doctor. Without linking, node dist/cli.js <command> does the same thing.
Step by step, with the output to expect: Steps 1 to 3 of the setup guide (Markdown, or docs/setup-guide.html#step-1 in the web page).
Login
skylight-mcp loginThe command prints a link to Skylight's authorize page. Open it in Chrome and sign in. The page needs Skylight's own server-side sign-in, not the session from the Skylight web app, so you may be asked to sign in even if the web app is already open.
After sign-in, Skylight sends the browser to https://ourskylight.com/welcome?code=... and then immediately redirects to its home page, so you usually cannot copy the callback address from the address bar. That is fine. Go back to the terminal and press Enter. The CLI then looks in Chrome's local history for that one URL and finishes the login. If nothing is found yet, it says so and asks again: press Enter to check again, paste the callback address, or type q to quit. The pending login stays valid for 10 minutes across retries.
What that lookup does: it reads only history entries whose URL starts with https://ourskylight.com/welcome?code= and that were visited after the login started. It copies Chrome's History database to a private temp directory (mode 0700), queries the copy with the macOS /usr/bin/sqlite3 in read-only mode, and deletes the copy afterwards. Nothing else in your history is read, and the URL is never printed or logged. This only works with Google Chrome.
If you would rather paste the address (or you use another browser), paste the full https://ourskylight.com/welcome?code=... address at the prompt instead of pressing Enter. If a login was started earlier and you have the final URL, run skylight-mcp login --complete <url> to finish it. --pkce S256|plain selects the PKCE method (default S256).
Check the result with skylight-mcp status. It shows whether you are logged in, the API host, the token expiry and the frame in use.
Step by step: Step 4 of the setup guide (Markdown, or docs/setup-guide.html#step-4 in the web page).
Claude Desktop setup
skylight-mcp doctordoctor prints your login status, the profiles it can see, and a ready-made config block with the absolute paths to your node binary and to dist/server.js. Paste that block into ~/Library/Application Support/Claude/claude_desktop_config.json, merging it with any existing mcpServers entries, then restart Claude Desktop. It looks like this:
{
"mcpServers": {
"skylight": {
"command": "/absolute/path/to/node",
"args": ["/absolute/path/to/skylight-mcp/dist/server.js"]
}
}
}If your account has more than one frame, set SKYLIGHT_FRAME_ID in the env block of that entry. doctor includes it when it is set in your environment, and does the same for SKYLIGHT_TIMEZONE and SKYLIGHT_TOOLSETS.
Step by step, including how to merge the block into a config file that already has other servers: Steps 5 to 7 of the setup guide (Markdown, or docs/setup-guide.html#step-5 in the web page). If Claude Desktop does not show the server afterwards, see When something goes wrong.
Use from Claude, ChatGPT and Gemini on any device
The same tools can also run as a shared server, so the family can use them from Claude (web, Desktop, iPhone), ChatGPT Business and Gemini (web and phone), each signed in as themselves, on the family's one Skylight frame. It is a Cloudflare Worker (free tier): Claude, ChatGPT and Gemini connect to it over OAuth, family members sign in with Google, and only the emails on the family list get in. The server holds its own Skylight sign-in (Skylight rotates refresh tokens, so it never shares the Mac's), encrypted in a Durable Object, and logs every change with the family member who made it. The Mac setup above keeps working unchanged.
Run these from your clone of this repository (the commands use its wrangler.jsonc). Do staging first, try it, then repeat with --env production and npm run remote:deploy:production.
The same steps with more explanation, the output to expect and the usual error messages are Part 2 of the setup guide: Steps 8 to 15 (Markdown, or docs/setup-guide.html#step-8 in the web page). In the web page you type your workers.dev subdomain once and it fills that into every command.
Sign in to Cloudflare:
npx wrangler login.Deploy once to get the address:
npm run remote:deploy:staging. It printshttps://skylight-mcp-staging.<your-subdomain>.workers.dev(production:https://skylight-mcp.<your-subdomain>.workers.dev). The KV namespace is created on this first deploy.Create the server's two internal secrets:
skylight-mcp remote setup --env staging --url https://skylight-mcp-staging.<your-subdomain>.workers.dev. It saves the address in~/Library/Application Support/skylight-mcp/remote.json, generatesSKYLIGHT_TOKEN_KEY(encrypts the stored Skylight sign-in) andADMIN_TOKEN(for the commands below), uploads both withwrangler secret putand keeps the admin token in your Keychain. Neither is printed or written to a file. Running setup again replaces both, after which you runremote loginagain.Create a Google sign-in client: Google Cloud console > APIs & Services > Credentials > Create credentials > OAuth client ID > Web application. Authorized redirect URIs:
https://skylight-mcp-staging.<your-subdomain>.workers.dev/callbackandhttps://skylight-mcp.<your-subdomain>.workers.dev/callback. If the OAuth consent screen is in Testing, add both family emails as test users (Google Auth Platform > Audience > Test users, not IAM).Give the Worker the Google client and the family list (each command asks for the value; the CLI never sees the Google secret):
npx wrangler secret put GOOGLE_CLIENT_ID --env staging npx wrangler secret put GOOGLE_CLIENT_SECRET --env staging npx wrangler secret put ALLOWED_EMAILS --env staging # comma-separated, e.g. you@gmail.com,spouse@example.comALLOWED_EMAILSis replaced as a whole each time you set it, so always enter the complete list. Then deploy again, as the checklist printed byremote setupasks:npm run remote:deploy:staging.Sign the server in to Skylight:
skylight-mcp remote login --env staging. It is the same Chrome sign-in asskylight-mcp login, but the result goes to the server, not to this Mac's store.skylight-mcp remote status --env stagingshows the server's sign-in.Claude (web, Desktop and iPhone share connectors): Customize > Connectors > Add custom connector, URL
https://skylight-mcp-staging.<your-subdomain>.workers.dev/mcp. Leave the OAuth client fields empty; Claude registers itself. Connect, approve the consent page, then choose your Google account. Claude Free allows one custom connector.ChatGPT Business: the workspace owner turns on Developer mode for apps in the workspace settings; then, in ChatGPT, Settings > Apps, add a custom MCP server with the same
/mcpURL and OAuth authentication. If the workspace belongs to an employer, its policy or admin may not allow a personal connector.Gemini (personal Google account, 18 or older, in the US, English): on gemini.google.com, Settings > Connected Apps (or Personal Intelligence > Connected Apps) > Custom apps, add the same
/mcpURL. Gemini registers itself, so leave Advanced features empty. Connect, approve the consent page, then choose your Google account. Custom apps can only be added on the web, then they work in the Gemini phone apps too. Gemini requires Keep Activity to be on, so those chats (with family calendar, chore and photo details) are saved to the Google account.
What the sign-in shows: a consent page that names the app by where access will be sent (Claude, ChatGPT, Gemini, or Claude Code on this computer), never by the name the app gives itself; says "This connects to the family Skylight" (or "the Rivera family Skylight" if you set SKYLIGHT_FAMILY_NAME to Rivera); and warns "Only continue if you just started connecting from Claude, ChatGPT or Gemini." Then comes Google's account chooser. A Google account that is not on ALLOWED_EMAILS gets "This Google account is not on the family list." and no access. The list is checked again on every call, so removing an email takes effect immediately. Emails must be plain ASCII (look-alike characters are refused). The first successful sign-in for each email also records that Google account's permanent id; a different Google account presenting the same email later is refused the same way. An app's connection lasts up to 30 days, then it asks you to connect again.
If a family member's address is a Google Workspace account (an employer's or a school's, not plain Gmail), that Workspace's administrators control the account and can sign in as that person, so they could reach the family Skylight too. Prefer personal Gmail addresses on ALLOWED_EMAILS.
What is logged:
The activity log: every call of a tool that can change something records when, who (the Google email), which tool, the ids it touched, and whether it worked or was only a preview. No other argument values, no tokens. It keeps 90 days. Ask for it with
skylight_recent_activity.Cloudflare's logs: one line per request with method, path, status and duration. Request headers, bodies and query strings are not logged.
To take access away:
One person:
skylight-mcp remote revoke <email> --env productiondisconnects every app they connected and forgets which Google account that email was bound to (so their next sign-in binds again, for example after they change Google accounts); remove them fromALLOWED_EMAILS(npx wrangler secret put ALLOWED_EMAILS --env production) to keep them out.If a server ever ran without the app allowlist (Claude, ChatGPT and Gemini redirect addresses only), clear out what it may have handed to other apps: start with a fresh
OAUTH_KVnamespace, or runskylight-mcp remote revoke <email>for each family member. Apps registered back then can no longer get new access, because/authorizere-checks every redirect address.The server's Skylight access:
skylight-mcp remote logout --env production(asks first). Tools then answer that the server owner needs to runskylight-mcp remote login.
Limits and notes:
The same confirm gates, previews and tool annotations apply, and Claude, ChatGPT and Gemini add their own approval prompts for tools that change things. ChatGPT sometimes blocks write calls with its own safety checks, and whether ChatGPT's phone app can use custom connectors is up to OpenAI.
300 calls per person every 10 minutes; past that the server answers 429. The sign-in endpoints are also limited per client address per minute (an IPv4 address, or an IPv6 /64):
/register5,/authorizeand/callback20 each,/token60; and/registerhas one shared budget of 20 a minute across all addresses.Only Claude, ChatGPT and Gemini can connect: app registration accepts only their redirect addresses (
claude.aiandclaude.com/api/mcp/auth_callback, ChatGPT's connector callbacks, Gemini custom apps'https://oauth-redirect.googleusercontent.com/r/user_bound_custom-mcp-<id>(not the rest of that Google host, which other Google products share), andhttp://localhost:<port>/callbackfor Claude Code), and metadata-document clients must come from claude.ai, claude.com, chatgpt.com or openai.com. Anything else gets "This app cannot connect to the family Skylight."Workers Free has a ceiling of about 1,000 KV writes a day, and an attacker can use it up on purpose: sign-ins, token refreshes and app registrations all write to KV. Once it is spent, sign-ins and token refreshes fail until it resets at midnight UTC. Run production on Workers Paid ($5 a month), which removes the ceiling; staging on Free is fine.
SKYLIGHT_TOOLSETS(a Worker var inwrangler.jsonc) trims the tool list per environment if a client struggles with many tools.SKYLIGHT_FAMILY_NAME(optional) puts your family's name on the consent page. Add it to an environment'svarsinwrangler.jsonc, or keep it out of the file withnpx wrangler secret put SKYLIGHT_FAMILY_NAME --env staging.The
workers.devaddress is public. Security rests on OAuth with a consent page per app, the Google allowlist and the admin token. Anyone with access to the Cloudflare account can read the Worker's secrets.
Toolsets
By default the server registers every tool (more than sixty), which some assistants handle poorly. Set SKYLIGHT_TOOLSETS to a comma list to trim the tool list to the groups you use:
Toolset | Tools |
| list, create, update and delete profiles and labels |
| chores and routine steps |
| reward points and rewards |
| lists and list items |
| calendar events |
| the meal plan, meal categories and recipes |
| photos, captions and albums |
| device settings, sleep, reset and remove |
| frame settings and who shares the frame |
| the plan and the marketing-email flag |
skylight_auth_status is always registered. Names are case-insensitive. An unknown name stops the server with an error that names it and lists the valid ones. Example for the env block of the Claude Desktop entry: "SKYLIGHT_TOOLSETS": "chores,lists,calendar,meals". skylight-mcp doctor prints the enabled toolsets.
Tools
Tool | What it does |
| Reports login state, API host, frame and token expiry. Never returns secrets. |
| Lists family profiles and their ids. Chores and points are assigned by profile id. |
| Creates a profile ( |
| Changes a profile's |
| Deletes a profile or label. Returns a preview and changes nothing unless |
| Lists chores and routine steps in a date range (default today through 14 days ahead), sorted by |
| Creates one chore or routine step for one or more profiles (people only; labels such as Birthdays are rejected). Routine steps need |
| Creates up to 50 chores in one call. Validates all items first and supports |
| Changes fields on an existing chore. Only the fields you pass change. Pass |
| Deletes a chore. Returns a preview and changes nothing unless |
| Marks a chore done, or reverts it with |
| Shows the point balance per profile as |
| Adds or subtracts points for one or more profiles. Negative values subtract. |
| Lists the rewards as |
| Creates a reward for one or more people ( |
| Changes a reward's |
| Spends the profile's points on a reward. Returns a preview (cost, current points, whether the balance covers it) and changes nothing unless |
| Undoes a redemption: refunds the points and clears the redeemed state. |
| Deletes a reward. Returns a preview and changes nothing unless |
| Moves a routine step before ( |
| Lists the lists as |
| Items of a list as |
| Creates a list ( |
| Changes a list's |
| Deletes a list and its items. Preview (title and item count) unless |
| Adds 1-100 items ( |
| Renames an item ( |
| Places an item after another item ( |
| Deletes 1-100 items in one request. Preview lists their titles unless |
| Lists calendar events between two dates (default today through 7 days ahead, at most 92 days) with |
| Creates an event. Timed events take |
| Changes fields on an event created in Skylight (the whole series for a recurring one, with |
| Deletes an event. Preview unless |
| Lists the meal slots (Breakfast, Lunch, Dinner, Snack) as |
| Renames a meal slot, changes its |
| Lists planned meals between two dates (default today through 7 days ahead, at most 62 days apart), one row per date: |
| Plans a meal for a |
| Changes a planned meal on one of its dates ( |
| Deletes a planned meal on one date (same |
| Lists recipes as |
| One recipe with |
| Creates a recipe: |
| Changes a recipe's title, category, description, ingredients or instructions. It reads the recipe first and merges, because Skylight needs all three fields on every update. |
| Deletes a recipe. Preview (the distinct meals and dates in the next 60 days that use it) unless |
| Asks Skylight to add the recipe's ingredients to the default grocery list; they appear a few seconds later. Not idempotent: calling twice adds them twice. |
| Lists photos and videos, newest first, one page at a time: |
| Sets a photo's caption (up to 200 characters); an empty caption clears it. |
| PERMANENTLY deletes 1-50 photos for everyone. Preview (each photo's date and caption) unless |
| Lists albums as |
| Creates an empty album. |
| Renames an album (built-in albums are refused). |
| Deletes an album; its photos stay on the frame. Preview unless |
| Adds 1-100 photos to an album. |
| Takes 1-100 photos out of an album (they stay on the frame). |
| Lists devices with their name, brightness, sleep window, slideshow settings and |
| Changes only the settings you pass: |
| Puts the screen to sleep ( |
| Resets a device (the screen is wiped and must be set up again). Needs |
| Removes a device from the frame. Needs |
| The frame's name, time zone, household name, locale, photo-sharing setting, enabled |
| Changes the household name ( |
| Lists who shares the frame: |
| Invites a person by email. Skylight emails them, so it previews unless |
| Blocks someone from the frame (never the owner). Preview unless |
| Gives a blocked person access again, or approves one who is waiting. |
| The plan, subscriptions ( |
| Turns Skylight's marketing emails on or off. |
| Shared server only: the latest changes made through it (when, who, tool, ids, ok or preview), newest first; |
Example prompts
"Show me the profiles on our Skylight, then do a dry run of a weekly chore schedule: Ellie empties the dishwasher every Monday, Wednesday and Friday, and Sam takes out the trash every Tuesday. Don't create anything yet."
"Create these chores starting next Monday: make bed (daily, 5 points) for Ellie and Sam, feed the dog (daily, morning) for Sam, and set the table (weekdays) for Ellie."
"Add milk, eggs and bread to the grocery list, with milk and eggs under Dairy, then move bread to the top."
"Create a reward for Sam called Movie night for 50 points, then redeem it. Show me his balance first."
"Put the dentist on Monday at 4:30 pm Eastern for Ellie, repeating every week."
"Plan tacos for Tuesday dinner and every Tuesday after, then add the ingredients to the grocery list."
"Create a recipe called Sheet-pan chicken for dinner with these ingredients and steps, then put it on Thursday."
"Show me the newest photos, caption the first one 'First day of school', and make an album called School 2026 with it."
"Dim the Skylight to 40% and put it to sleep at 9:30 pm."
"Add a morning routine for Ellie starting tomorrow with three steps: brush teeth, get dressed, pack backpack. Run it as a dry run first and show me the payloads."
Routine steps are chores with routine: true and a timeOfDay of morning, afternoon or evening (Skylight's only three routine slots). They take no times: a step's startTime is derived by Skylight from its slot, and the recurrence defaults to daily. The order of steps inside a routine is Skylight's position field, assigned in creation order; skylight_move_routine_step reorders steps afterwards. For example, the three-step prompt above creates:
{ "chores": [
{ "summary": "Brush teeth", "start": "2026-10-13", "profileIds": ["<Ellie>"], "routine": true, "timeOfDay": "morning" },
{ "summary": "Get dressed", "start": "2026-10-13", "profileIds": ["<Ellie>"], "routine": true, "timeOfDay": "morning" },
{ "summary": "Pack backpack", "start": "2026-10-13", "profileIds": ["<Ellie>"], "routine": true, "timeOfDay": "morning" }
] }Time zones
Skylight stores and returns UTC. skylight-mcp shows you everything in one zone, Eastern time (America/New_York) by default, so EST and EDT are handled for you:
Times you type, such as
startsAt: "2026-10-12T18:30", are read as wall-clock time in that zone and sent to Skylight with the right offset (-04:00in summer,-05:00in winter). Without that conversion Skylight would store 18:30 as 18:30 UTC, which is 2:30 PM Eastern. Add an explicit offset orZif you do mean another zone. A time that does not exist because the clocks skip forward (such as 2:30 AM on the spring-forward Sunday) is refused with a request to pick another time; a time that happens twice when the clocks fall back resolves to the first (daylight) occurrence. "Today" and the default date ranges also come from this zone, not from the machine's.Times in results are shown in the same zone with an explicit offset (
2026-10-12T18:30:00-04:00). Events also have a plain-wordswhen, such asMon Oct 12, 6:30 PM EDT to 7:30 PM EDT. All-day events show dates only.This covers event start and end times, reward
redeemedAt, chorecompletedAtand the login token expiry inskylight_auth_status,skylight-mcp status,loginanddoctor.To use another zone, set
SKYLIGHT_TIMEZONEto an IANA name such asAmerica/Chicagoin theenvblock of the Claude Desktop config (skylight-mcp doctorprints the block with the variable when it is set). An invalid name stops the server with an error naming the variable.
Development
Use skylight-mcp ... as above, or node dist/cli.js ... without linking.
npm run check # typecheck (Mac, tests, Worker), tests, build, and the Worker's dry-run bundle
npm run remote:dev # the shared server locally (wrangler dev; put dummy secrets in .dev.vars)
npm run live:smoke # opt-in checks against the real APIDependencies are pinned to exact versions, normally ones published at least 14 days earlier. One exception: wrangler is 4.149.0 (published 2026-10-08), with @cloudflare/workers-types 5.20261006.1 to match its workerd 1.20261006. 4.149.0 is the oldest wrangler without high-severity npm audit advisories (checked 2026-10-12): npm lists wrangler up to 4.148.0 as affected through miniflare, 4.142.0 reported high advisories in undici (7.0 to 7.29) and sharp (below 0.35.5), and 4.148.0 still reported the sharp one. Both tools are development-only; neither is in the deployed Worker.
npm run live:smoke uses your stored login and is read-only by default. Set SKYLIGHT_LIVE_WRITE=1 to also create, update, complete, revert and delete a one-time chore and a daily recurring chore (including deleting a single occurrence and the whole series), the weekly, monthly, interval and until recurrences, a morning routine step (complete, revert, delete as a whole), an up-for-grabs chore, and a field-clearing update. It then runs the phase 2 leg (scripts/live-smoke-phase2.ts) on a dedicated smoke profile: rewards (create, update, redeem preview, redeem, unredeem, delete), reordering two routine steps, a list with items (add, complete, rename, move, bulk delete), and calendar events (all-day, timed with offset, weekly recurrence with one occurrence and the series deleted, and the refusal of a synced event when one exists). After that comes the phase 3 leg (scripts/live-smoke-phase3.ts): a recipe with two zzsmoke ingredients (parsed back), a one-time and a daily meal, applyTo one (a new mealId appears), delete one date and the rest of the series, adding the recipe to the grocery list and waiting up to 15 seconds for the two items (then deleting them), deleting the recipe together with its planned meal, an album (create, rename, add and remove the newest photo, delete), setting and restoring the newest photo's caption, flipping and restoring a device's showHeart, and a no-op frame time-zone update. The smoke never resets or removes a device, deletes photos, invites or blocks anyone, or changes marketing emails. Everything it creates is prefixed [skylight-mcp smoke], cleaned up in a finally block and checked for leftovers. It is not part of the automated tests. Other scripts: npm run dev:server and npm run dev:cli run the TypeScript sources directly. API notes are in docs/api.md.
Credits
The API knowledge and the Keychain credential-store design come from kamilio/skylight-calendar-agent, which is MIT licensed. This project is also MIT licensed. See LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Family calendars, tasks, reminders, and pickup coordination for your AI assistant.
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
Your household's calendar, tasks, messages and apps. Read, update, or build new apps with AI.
Scraps Kitchen gives any AI agent a persistent, household-aware kitchen memory. Unlike generic chatbot recall, Scraps maintains structured cooking data: what's in your fridge (with freshness tracking), who you cook for (with allergens, dietary restrictions, and preferences), your recipe collection (with cook notes and per-diner ratings), your shopping list, and your kitchen equipment. 27 tools across 6 domains let agents read kitchen context, suggest meals that respect dietary safety, update the pantry after cooking, and build a history of what works for your household. Every interaction makes the data richer. Cooking history, preference signals, kitchen awareness = better suggestions next time. All tools work via oAuth and a free scraps.kitchen account.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage shopping lists, recipes, meal plans, and shared expenses with a KitchenOwl instance via its REST API.MIT
- AlicenseCqualityAmaintenanceMCP server for Skylight Calendar family hub, providing over 100 tools to manage events, lists, chores, meals, messages, albums, and device settings.1161,601 npm23MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with the Skylight family calendar API, allowing management of calendars, chores, lists, tasks, family members, and rewards through natural language.2333 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to read, create, update, delete, and search Google Calendar events across multiple accounts, check availability, and handle recurring events and invitations through natural language.79 npmMIT