Care Ladder MCP Server
Serves as the MCP backend for Amazon Alexa+ (primary surface), exposing seven care-flow tools — start_or_resume_incident, check_in_prompt, advance_rung, resolve_incident, get_incident_status, notify_caretaker, and request_call — that drive multi-rung, multi-turn incident handling with session state keyed by household and incident. Also powers an accompanying Amazon Fire TV caregiver surface (/firetv/) that renders a data-driven, silhouette-only calm care-tech audit view with D-pad navigation from the live ladder API.
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., "@Care Ladder MCP Serverstart a wellness check for the Amazon demo home and see if she's okay"
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.
Care Ladder · Alexa+ · Fire TV · MCP
Camera cue → multi-rung care ladder → Alexa+ agent (self-hosted MCP) → Fire TV caregiver audit (silhouette-only). Wellness ladder, not a medical device.
Hackathon map
Amazon Build, Ship, Shape (draft — no Final Submit).
Surface | Role |
Alexa+ (primary) | Self-hosted MCP care-flow tools + in-repo simulated Alexa+ MCP client. Multi-rung, multi-turn, incident session state — not single-turn Q&A. |
Fire TV (supporting) | Calm Care-Tech caregiver surface at |
MCP | Spec 2025-11-25+ Streamable HTTP at |
AWS Builder mini | Not filed. No Bedrock / AgentCore in-tree. |
Seven MCP tools: start_or_resume_incident · check_in_prompt · advance_rung · resolve_incident · get_incident_status · notify_caretaker · request_call
Related MCP server: CaseMargin MCP Server
Agentic proof (not thin MCP)
Session state is keyed by household + incident (household_id + incident_id). Every MCP tool return includes a session_snapshot (household_id, incident_id, rung, status, tools trail) so the agent carries one memory across turns — not disconnected FAQ calls.
The in-repo MCP client src/care_ladder/mcp_server/alexa_sim.py drives a real HTTP initialize → tools/call chain and prints a SESSION … rung=N status=… banner after each call:
start_or_resume_incident— open the incidentstart_or_resume_incidentagain with the same ids — resume-same-incident (resumed: true)check_in_prompt— fail-closed intent (clear_ok/needs_human/unclear)advance_rung/notify_caretaker/resolve_incident— same incident id throughout
Soft “don’t worry” can stand the ladder down; “okay but hurt” will not. Both Path A soft-OK and needs-human print resume-same-incident and keep one incident id from start → check-in → resolve/notify.
Quickstart (≤60s to something on screen)
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
.venv/bin/uvicorn care_ladder.api.app:app --port 8010
# Fire TV: http://127.0.0.1:8010/firetv/ (Demo console, bottom right)
# MCP: POST http://127.0.0.1:8010/mcp (Streamable HTTP)
.venv/bin/python -m care_ladder.mcp_server.alexa_sim --url http://127.0.0.1:8010
# Soft OK: ... alexa_sim --url http://127.0.0.1:8010 --answer "don't worry"Amazon household: configs/amazon_demo_home.yaml (resident + primary/secondary contacts, stillness 4m). configs/demo_home.yaml is the legacy OpenCV plan, kept for before/after regression.
Demo paths
Path | Fixture | What judges should see |
Silence → notify |
| Two Alexa+ check-ins, 45s wait, notify + simulated call |
Soft OK |
| Resolves; no notify |
Needs human |
| Does not resolve; notify stays up |
Unclear |
| Groan / garbage → re-ask, then escalate |
Path B occlusion |
| Covered camera is privacy, never distress ( |
Fire TV Demo console posts these fixtures to /demo/run. Or:
curl -s -X POST http://127.0.0.1:8010/demo/run \
-H 'Content-Type: application/json' \
-d '{"fixture":"alexa_path_a_soft_ok"}'Privacy & fail-closed
Silhouette-only on Fire TV — no live video element, no raw frames.
Frames that leave the device path go through
blur_faces/to_silhouettebefore attach.Emergency dial is off and hard-locked in this demo build (hold-to-review explains; no call possible).
Demo phones are reserved NANP fiction only: (555) 010-2276 (
+12125550176).Footer copy: Wellness ladder — not a medical device.
Known limits: docs/failure-modes.md. Why this design: docs/research-brief.md.
Friction log
Honest tool/SDK notes (bonus): docs/friction-log.md.
Tests
.venv/bin/pytest tests/ -vMCP handshake + seven tools, Fire TV HTML/API flow, response intent, alexa_sim client, and the shared ladder/API spine.
Shared demo host (read-only from this repo)
Live HTTPS today: https://d2u7pls4da2poz.cloudfront.net/ — shared host from the opencv-care-ladder stack. CI on this repo is test-only (no auto-deploy) so OpenCV judges keep a stable CloudFront. Optional AWS replay: infra/README.md. Local run needs no AWS credentials: ./scripts/run_demo.sh.
Vision ONNX models and eval clips are not committed. If you want the optional vision-trigger proofs: ./scripts/download_models.sh and ./scripts/download_clips.sh. Alexa+ fixtures do not need ONNX.
Origins
Significant in-window update of OpenCV Care Ladder (pamu512/opencv-care-ladder). Vision cues are vendored here as the trigger; Amazon work is MCP + Fire TV + rungs. The OpenCV repo stays separate until after OpenCV judging. No Bee / Ring / Bedrock / AgentCore.
License
MIT © 2026 Anoop Pamu. See LICENSE.
This server cannot be deployed
Maintenance
Related MCP Connectors
Exposes FEDLIN's public security scanners as agent-callable tools over Streamable HTTP.
AI Reasoning Cache & Consensus Layer with 11 MCP tools via Streamable HTTP.
Human-input bridge for AI agents with voice-first answer links, MCP tools, and HTTP APIs.
Give your AI agent a phone: place calls, navigate IVRs, wait on hold, get structured answers.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables Claude to drive a gated incident-response runbook that enforces step order and logs all actions via an XState machine.Apache 2.0

CaseMargin MCP Serverofficial
AlicenseAqualityAmaintenanceExposes support case reasoning tools — generate structured case briefs and check escalation readiness from any MCP-compatible AI client.253 npm1MIT- FlicenseNot gradedqualityBmaintenanceDemonstrates stateful application patterns on the stateless MCP 2026-07-28 protocol, enabling request-scoped state, multi round-trip confirmations, and streaming progress updates across independent tool calls.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search and retrieve support tickets, add notes, close tickets, and access SLA policies through MCP tools, resources, and prompts over Streamable HTTP.MIT