Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Hearth v2 How is Mum doing today? Anything I should know?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Hearth lets an older adult talk to Alexa+ about medicines and mood. Their caregiver gets a calm, honest signal only when a real pattern appears, and the person is asked before anything proactive is shared.
Track: Alexa+ (MCP integration on Streamable HTTP + Agent Skill + web simulator).
npm install
npm start # MCP endpoint http://127.0.0.1:3000/mcp simulator http://127.0.0.1:3000
npm test # 24 protocol-level checksNode 18+ (tested on Node 22). No API keys. All data is fictional and in memory. Open the simulator at http://127.0.0.1:3000 (the Origin allow-list covers localhost and 127.0.0.1 on the chosen port).
Demo video: docs/demo.mp4 · Requirements and evidence: docs/COMPLIANCE.md · Deploy: docs/DEPLOY.md
Related MCP server: CareCompanion
Spec feature (source) | How Hearth uses it |
Streamable HTTP 2025-11-25: Origin validation, localhost bind, | Stateful sessions, 403 on foreign Origin, 400/404 per spec, bound to 127.0.0.1 |
SSE streams, event ids, | In-memory EventStore; subscribed clients are pushed |
MCP Apps ( |
|
Elicitation | Proactive alerts need the person's consent; emergencies and explicit requests bypass it |
Agent Skills |
|
Structured results |
|
Personalised routine model: the "no morning activity" threshold is median + max(60 min, 4×MAD) of the person's own first-activity times (usual 07:18, alert after 08:18), not a fixed hour.
server.js MCP server (8 tools, 3 resources incl. the ui:// view)
src/store.js care logic, personalised baseline, demo clock, change events
src/eventStore.js resumable SSE event store
ui/dashboard.html the MCP App view (no SDK, plain JSON-RPC over postMessage)
public/index.html Alexa+ simulator: real MCP client (sessions, SSE, consent) and an MCP Apps host
skills/hearth-care/SKILL.md Agent Skill
test.mjs spec-level tests (security, lifecycle, UI metadata, consent, push, resume)
As Amina: "Good morning", "I feel tired".
Press +3 h, then ★ Run proactive check: Alexa+ asks Amina for consent (MCP elicitation) before telling Salma.
Switch to Salma, "How is mum doing?": the dashboard renders as an MCP App; press Refresh (app-only tool).
Back to Amina: "I fell" gives the emergency-first response and an urgent alert without a consent step. Watch Live MCP traffic and push stream on the right.
Not tested on a real Alexa+ device or with third-party MCP hosts (Claude, ChatGPT, VS Code). The simulator is our own client/host; phrase-to-tool mapping is rule-based.
The simulator's MCP Apps host uses a sandboxed srcdoc iframe (opaque origin) instead of the spec's recommended double-iframe sandbox proxy on a separate origin. A production host needs the proxy.
Home signals are simulated, not connected to Ring. No auth, persistence or encryption yet. Not a medical device.
To expose the server beyond localhost set HOST, ALLOWED_ORIGINS, ALLOWED_HOSTS and add authentication first.
Household auth (OAuth), persistence, real Ring/IoT events, clinician-ready weekly report, Bedrock summaries (AWS mini-challenge), sandbox proxy host.
This server cannot be deployed
Authenticated MCP for a user's care circle: read CareEvents, list loved ones, inspect workspace.
Remote MCP for MCP consent scope receipt, structured receipts, audit logs, and reviewer-ready eviden
An AI concierge that turns static forms into adaptive AI conversations. From any MCP client.
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
