Inspiration

One late parent can disrupt an entire household morning. Finding someone who can drive is only the first step: they also need a free time window, the bag must be ready, and the new assignment must not collide with another job. HomeRelay makes those constraints visible and keeps the final decision with people.

What it does

HomeRelay turns an explicit availability update into a proposed schedule for a fictional household. In the sample, “Lena is 30 minutes late” triggers real MCP calls to replan the school run, packing lunch, feeding the cat, and dropping off a parcel.

Every proposed assignment has an owner, an exact time interval, and an explanation. The planner checks capabilities, availability, duration, deadlines, and overlapping tasks. It explores alternative owners and times, prioritizes essential work, and shows unresolved tasks when capacity is insufficient. In the first sample disruption, all four tasks fit with two handoffs.

Approval is a separate action. The server recalculates the proposal against the current saved household and rejects edited or stale drafts. Approved times, owners, availability, and unresolved work survive a reload. Demo acknowledgments are available only for resolved tasks. A second disruption—Omar becoming unavailable after the first plan is approved—leaves the school run visibly unresolved instead of falsely marking it complete.

Handoff requests remain drafts inside the app. No external messages are sent or devices controlled.

How we built it

The self-hosted server implements MCP 2025-11-25 over stateless Streamable HTTP at /mcp. Its tools are get_demo_household, replan_household, and draft_handoffs. The web interface performs initialization and calls those tools to produce the plan and handoff drafts. Explicit input schemas, workload limits, and read-only annotations support predictable client use. A connection tab runs initialization, discovery, and sample planning calls.

React, TypeScript, Vinext, and Vite provide the interface and server routes. Cloudflare Workers and D1 persist household state, with Drizzle for the data model and Zod for validation. Tailwind and Lucide support the responsive interface. Node, pnpm, and esbuild support the reproducible build and regression checks.

Planning uses a bounded beam search across eligible owners and free intervals. It favors essential tasks, fewer owner changes, and earlier completion. It is not a guarantee of a globally optimal schedule. Saved household records are separate from the public MCP tools: the tools use fictional or caller-supplied context and cannot approve changes or retrieve saved private households.

This is an explicitly labeled Alexa+ web simulation with a real MCP server. It does not claim a live Alexa+ account/device connection, an LLM, or an AWS integration.

Challenges and what we learned

A greedy assignment can consume the only time window needed by another task. Exploring alternatives made the schedule more useful. Another challenge was preserving the exact plan people approved: we added server-side recalculation, revision checks, and durable schedule storage. Ambiguous names and invalid scenario numbers are rejected rather than guessed.

The key lesson was to separate a proposed plan, a human approval, and a completion acknowledgment. Each means something different and needs its own validation.

Accomplishments

HomeRelay was created during the event on October 7, 2026 and improved on October 8. The upgrades added alternative-owner planning, exact approved-plan persistence, stale/edited-draft rejection, unresolved-task protection, explicit MCP schemas, and connection verification.

Seventeen focused automated checks and TypeScript checks pass. Checks against the actual built Worker and a fresh local D1 database cover rendering, MCP calls, approval/reload, revision conflicts, partial plans, acknowledgments, workspace separation, and origin handling. Browser visual verification of the latest UI remains pending because the available preview was unreachable.

The public 1:54 video has English captions. It labels October 7 core workflow footage separately from verified October 8 code improvements; it does not present the earlier footage as a new recording of the latest interface. The MIT repository includes the complete source, assets, migrations, tests, locked dependencies, and run instructions in source.zip and README.md.

Narrated demo for judges

The submission attachment includes a 1:54 version with synthesized English narration and the same captions. Open HomeRelay-Demo-With-Sound.mp4 inside HomeRelay-Submission-With-Narrated-Video.zip. The archive also contains source.zip with the complete runnable source.

Try it

  1. Open the live demo and enter “Lena is 30 minutes late.”
  2. Inspect the four scheduled tasks, two handoffs, intervals, and reasons.
  3. Approve the proposal and reload to check the retained schedule.
  4. Report “Omar is unavailable” and inspect the unresolved school run.
  5. Use the MCP connection tab to verify the handshake and sample tools.

The demonstration uses fictional data and needs no login.

What is next

The intended audience is households coordinating a small number of time-sensitive jobs. Next steps are live Alexa+ onboarding, broader scenario input, accessibility testing, and a small user study comparing the same disruptions with and without HomeRelay. No adoption figures or measured time savings are claimed.

Built With

Share this project:

Updates

Submission history