Hearth MCP Server
Allows connecting the MCP server to Alexa+ as an add-on, enabling voice-driven family evening planning, reminders, and elder care check-ins through the Alexa+ platform.
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.
Hearth — Alexa+ Family Concierge
Hearth is a hackathon demo for the Alexa+ track: a real MCP server (specification 2025-11-25, Streamable HTTP) plus an Echo Show–style web simulation. A family evening concierge personalizes plans for kids and grandma, suggests timelines, sets reminders, and logs gentle care check-ins.
Tracks: Alexa+ (primary) · AWS Builder mini-challenge (Amazon Bedrock)
Pitch: Alexa+ that plans the whole living room evening — kids, captions, and an elder care check-in — through an open MCP server.
Full Devpost blurb: docs/DEVPOST_DESCRIPTION.md · Bedrock setup: docs/AWS_BUILDER.md · AWS clip: docs/AWS_BUILDER_CLIP.md
Record the demo video
npm run demo:prep
# Window A opens ?demo=1 — Window B: npm run demo:brollChecklist + VO + frames: docs/demo-assets/RECORDING_READY.md · shot list: docs/VIDEO_VOICEOVER.md
Architecture
Browser (device UI + voice)
→ Simulator API (agent loop: Bedrock or offline)
→ Hearth MCP server POST/GET /mcp (Streamable HTTP JSON-RPC)
→ tools, resources (hearth://…), prompts (evening_briefing)The repository actually invokes local MCP tools in code. External AWS calls are virtual by default so the whole project works offline as a self-contained demo.
Related MCP server: Aura+
Quick start (PC only)
Prerequisites: Node.js 20+ and npm. No AWS account required.
git clone <your-repo-url>
cd amazon-hakaton
npm install
npm run demoOpen http://127.0.0.1:5173. One command starts MCP (:3100) and the simulator (:5173 + API :8787).
Or run separately:
npm run build -w @hearth/shared
npm run mcp # http://127.0.0.1:3100/mcp
npm run sim # http://127.0.0.1:5173Try scenario chips, or:
Plan a low-key evening for me, the kids, and grandma
The UI shows a device frame, evening timeline, live MCP tool calls, latency, and optional voice input (Chrome). Agent mode is virtual Bedrock (real local MCP + Bedrock-shaped AWS chips) with CloudWatch dry-run — no outbound AWS traffic.
Optional: live Amazon Bedrock (AWS Builder)
Demo networking is the default. To hit real Bedrock / CloudWatch:
set HEARTH_LIVE_AWS=1
set AWS_REGION=us-east-1
set AWS_PROFILE=your-profile
set BEDROCK_MODEL_ID=anthropic.claude-3-haiku-20240307-v1:0If live Bedrock fails, Hearth falls back to the offline MCP agent. Force the plain offline router (no Bedrock UI):
set HEARTH_FORCE_OFFLINE=1MCP surface
Kind | Name | Purpose |
Tool |
| Members, preferences, accessibility notes |
Tool |
| Personalized options + why/chips/timeline |
Tool |
| Reminder tied to a plan |
Tool |
| Gentle elder / accessibility check-in |
Tool |
| Lock in a chosen plan |
Tool |
| Tonight’s plan, reminders, check-ins |
Resource |
| Live household JSON |
Resource |
| Tonight’s state |
Resource |
| Demo scenario presets |
Prompt |
| Spoken Alexa+ briefing |
Prompt |
| Elder care check-in script |
Protocol: Streamable HTTP on /mcp · version 2025-11-25. Tool latency is exposed on /health (Alexa+ target < 500 ms).
Demo script
See docs/DEMO_SCRIPT.md — two scenarios, timeline, tools, optional voice/Bedrock.
Connecting to real Alexa+ (optional)
Expose the MCP server with a tunnel (
cloudflared tunnel --url http://127.0.0.1:3100).Follow the Alexa+ MCP QuickStart (
alexa-ai configure/ add-on deploy).Production Alexa+ also expects OAuth/PRM; this repo includes a hackathon PRM + PKCE S256 scaffold (
/.well-known/*,/oauth/*). The web simulator path can stay local/open per hackathon rules.
Tests, Docker, architecture
npm test # mcp-server + simulator vitest suites
npm run test:e2e # Playwright: /?demo=1&fast=1 (Rivera → Okonkwo)
npm run test:oss # OSS starter: build dist/ + Streamable HTTP smoke
npm run lint # ESLint
npm run format:check # Prettier
npm run typecheck
npm run build
docker compose up --build # MCP :3100 + UI/API :8787CI (GitHub Actions): .github/workflows/ci.yml — lint → format → typecheck → test → Playwright → OSS smoke → build.
Simulator coverage: offline agent, Bedrock→offline fallback, knowledge retrieve, /api/chat + demo-script, demo autoplay sequencer (/?demo=1).
Tunnel hardening (optional): HEARTH_API_KEY, HEARTH_CORS_ORIGINS, HEARTH_RATE_LIMIT_RPM, OAuth/PRM scaffold, session TTL — see .env.example and docs/ALEXA_PLUS_TUNNEL.md.
See ARCHITECTURE.md.
Alexa+ tunnel (optional P3)
npm run mcp
npm run tunnel # cloudflared → then alexa-ai deployDetails: docs/ALEXA_PLUS_TUNNEL.md.
Open Source mini
Standalone MIT starter: oss/streamable-http-mcp-starter
Published: https://github.com/SERGIOCORVALIS/streamable-http-mcp-starter
Details: docs/OSS_MINI.md · Strong-plus status: docs/STRONG_PLUS.md
Before you submit
npm run sanity
# record video per docs/VIDEO_VOICEOVER.md
# push private repo, then AT SUBMIT TIME:
.\scripts\add-amazon-collaborators.ps1 -Repo YOUR_USER/YOUR_REPOChecklist: docs/SUBMISSION_CHECKLIST.md · Devpost paste: docs/DEVPOST_PASTE.md · Bugs: docs/BUG_JOURNAL.md · Features: docs/FEATURE_REQUESTS.md · Deps: docs/DEPENDENCY_AUDIT.md · Plan card: docs/MCP_APPS_PLAN_CARD.md
Repository layout
mcp-server/ Streamable HTTP MCP server + Hearth tools
simulator/ React UI + agent API (Bedrock / offline) + MCP client
packages/shared Shared types + protocol constant
oss/ Additional OSS starter (Streamable HTTP MCP)
docs/ Devpost feedback, bug journal, tunnel, OSS notes
ARCHITECTURE.md System design for reviewersGitHub submission notes
Prefer a private repo for judging; add Amazon reviewers as collaborators when you submit (invites expire in 7 days):
chris-trag,knmeiss,giolaq,anishamalde,mosesroth,emersonsklar
Include an MIT
LICENSE(already present) if you open-source later.Demo video: < 3 minutes, public YouTube/Vimeo, English.
License
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP server for live public-data APIs and Skills for AI agents.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Skills, agents and memory in the cloud, plus a gateway to your other MCP servers.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables Alexa+ to autonomously orchestrate multi-step household tasks by decomposing goals into parallel tool calls — cross-session memory and dietary/allergy auditing, culinary planning with wine pairings, Amazon Fresh cart assembly with human-in-the-loop purchase approval, smart-home ambiance and climate control, and calendar scheduling. It pairs AWS Bedrock multi-agent reasoning with Streamable HTTP transport and interactive generative UI cards, carousels, and live IoT sliders.MIT
- AlicenseNot gradedqualityBmaintenanceEnables an Alexa-style assistant to plan and execute multi-step smart home routines, remember user preferences across sessions, and render interactive UI cards on screen via Streamable HTTP MCP tools. Uses AWS Bedrock for reasoning with a built-in offline intent fallback.MIT
- AlicenseNot gradedqualityCmaintenanceEnables an older adult to talk with Alexa+ about medicines and daily routine while a caregiver sees a calm, consent-gated dashboard and push alerts only when a genuine pattern (e.g. an unusually late first activity) appears. Includes elicitation-based consent, emergency bypass, resumable SSE streams, and an inline MCP App view.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables Alexa+ to coordinate a household through 14 MCP tools: it tracks family members, auto-assigns and completes chores by workload, adds calendar events while reporting clashes, rotates pickup duty, manages a grocery list, and returns a spoken morning briefing with reasoning for every decision.MIT