Enables Amazon Alexa+ to handle home maintenance workflows, including capturing observed issues, recording provider quotes, generating diagnostic and comparison plans, proposing owner-gated actions, and producing tamper-evident snapshots.
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., "@HomeOps Relay The kitchen sink is draining slowly, start a maintenance case"
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.
HomeOps Relay turns a spoken household problem into an evidence-linked maintenance case, deterministic diagnostic plan, quote comparison, and owner-gated action proposal. It is designed for the Alexa+ track as a self-hosted Model Context Protocol server using MCP protocol version 2025-11-25 over Streamable HTTP.
The differentiator is not another single-turn home-maintenance chatbot. HomeOps Relay maintains a tamper-evident state chain across sessions/workflows and separates three things agents often blur together: what the household observed, what a provider claimed, and what an owner actually authorized. Contacting a provider, scheduling, purchasing, warranty filing, payment, or any other real-world side effect is permanently outside this demo server; the MCP surface can create and review proposals, not execute them.
Captured from the current Amazon/Devpost first-party pages on 2026-09-17:
Submission deadline: 2026-10-23 12:00 PM Pacific.
Alexa+ accepts a working Agent Skill or a self-hosted MCP server implementing spec 2025-11-25 or later over Streamable HTTP.
Public source, working demo, and a public English demo video under three minutes are required at submission.
Alexa+ track cash prizes are $25,000 / $15,000 / $4,000; a qualifying primary-track project can also compete for the $5,000 Open Source mini challenge.
Judging emphasizes technical implementation, design, potential impact, and quality of the idea.
Authoritative sources are pinned in RULES_SNAPSHOT.md. Nothing in this repository is a registration, submission, eligibility, award, or payment claim.
Related MCP server: oficio
Alexa+ / MCP client
|
| JSON-RPC 2.0 over POST /mcp
v
+----------------------+ +--------------------------+
| Streamable HTTP MCP | ---> | HomeOps deterministic |
| protocol 2025-11-25 | | event / receipt ledger |
+----------------------+ +--------------------------+
|
+--------------------------+--------------------------+
| | |
issue intake quote intake plan + action
observations only caller-supplied/unverified proposals only
|
PENDING_OWNER_REVIEW
|
APPROVED_NOT_EXECUTEDThe hash chain is replayable: each event binds its sequence, semantic kind, exact payload, and predecessor receipt. HomeOpsLedger.verify_events() reconstructs the state and fails on mutation, reordering, unknown semantics, duplicate IDs, non-integer money, or invalid transitions.
An optional SQLite journal now retains commands, their original responses and the same domain events across process restarts. It reconstructs state through the existing ledger. A mutation returns success only after its transaction commits. Concurrent processes using the same local database serialize writes, while each read uses one consistent database snapshot. Without durable configuration, the original in-memory library and server mode remain available.
Tool | Purpose | External effect |
| Capture issue, severity, area, detail, evidence refs | none |
| Record caller-supplied provider quote in integer minor units | none |
| Create deterministic diagnostic + quote comparison plan | none |
| Create provider/schedule/purchase/warranty proposal | none |
| Record approval/rejection evidence | still none |
| Return state + tamper-evident receipt | none |
The original in-memory mode requires Python 3.10+ and the standard library only. The optional SQLite journal requires Python 3.11+ for the connection's runtime size-limit API; unsupported durable startup reports a contained error before creating a database.
git clone https://github.com/woahwhattheheck/homeops-mcp.git
cd homeops-mcp
python -m unittest discover -s tests -v
python -O -m unittest discover -s tests -v
python -m homeops_relay.demo
python -m homeops_relay.mcp_serverThe server binds 127.0.0.1:8000 by default. Its MCP endpoint is http://127.0.0.1:8000/mcp; health is /healthz. It implements the 2025-11-25 handshake lifecycle: successful initialize returns a cryptographically random MCP-Session-Id; the client sends notifications/initialized; subsequent calls require both that session ID and MCP-Protocol-Version: 2025-11-25. POST transport requests must advertise both application/json and text/event-stream in Accept, as required by Streamable HTTP. This implementation chooses JSON responses and intentionally returns 405 to the optional GET/SSE listener.
For an intentional remote deployment, set HOMEOPS_HOST=0.0.0.0 together with HOMEOPS_ALLOW_REMOTE_BIND=1, terminate TLS/authentication in a trusted production reverse proxy, and explicitly set HOMEOPS_ALLOWED_ORIGINS for browser origins. The handler rejects non-local Origin headers by default, caps request bodies, rejects duplicate JSON keys/non-finite numbers, rate-limits tool calls per session, and serializes append-only ledger mutation across concurrent HTTP workers.
With Python 3.11 or newer, choose a new database path inside an existing local directory:
HOMEOPS_DB_PATH=/tmp/homeops-demo.sqlite python -B -m homeops_relay.mcp_serverRestart with the same path to recover the retained journal. HOMEOPS_DB_PATH applies to the command-line server; library callers use make_server(..., durable_path=...) or Dispatcher(durable_path=...) explicitly. HTTP sessions are still process-local: initialize a fresh session after a restart. Session IDs are not durable operation IDs.
The configured tools/list schemas require operation_id for homeops.intake_issue, homeops.record_quote, homeops.request_action and homeops.record_owner_decision. For example, add "operation_id": "drawer-intake-001" to a fictional intake's arguments. Read-only snapshot and propose_plan retain their original arguments. An operation ID is 1–128 ASCII letters, digits, dots, underscores, colons or hyphens, beginning with a letter or digit.
Retain each mutation's operation ID and exact argument values. Retrying the same tool and canonical JSON arguments returns its original committed response, including its historical receipt, without another event. Reusing that ID with different content returns an error. An omitted default and an explicitly supplied default are different requests; JSON object key order is immaterial. To inspect the latest state after a retry, call homeops.snapshot.
If the commit result is uncertain, the MCP tool error includes storage_error: "UncertainCommitError" and retry_with_same_operation_id: true. A lost HTTP response can likewise follow a committed operation. Retry the identical request with the same ID; an interruption alone does not establish rollback. The journal does not execute the external actions described in a proposal or recorded decision.
Use the operator commands to inspect, export or copy a consistent database:
python -B -m homeops_relay.journal_cli inspect /tmp/homeops-demo.sqlite
python -B -m homeops_relay.journal_cli export /tmp/homeops-demo.sqlite --output /tmp/new-homeops-events.json
python -B -m homeops_relay.journal_cli backup /tmp/homeops-demo.sqlite --output /tmp/new-homeops-backup.sqlite
python -B -m homeops_relay.journal_cli restore /tmp/new-homeops-backup.sqlite --output /tmp/new-homeops-restored.sqliteBackup and restore retain the command/response retry history; the event export is for inspection and domain replay, and is not a replacement for a full journal backup. Destinations must be new. Use a local filesystem with working SQLite locking and keep the database and its transient journal files together while a process is running. Do not copy a live database file with a plain filesystem copy. The database and backups retain the supplied text in plaintext; the demonstration uses fictional records.
Even inspection needs a writable database and directory so SQLite can recover an interrupted transaction. Logical read commands do not add domain events or operations. A process crash before commit can leave a rollback journal; keep it with the database and let the adapter perform SQLite recovery rather than deleting it.
The completed fictional restart/retry/backup journey, actual execution and storage limits are documented in JOURNAL_OPERATOR_GUIDE.md and JOURNAL_EXECUTION.md. Each accepted normal and optimized rehearsal used three real server processes, 25 HTTP exchanges and ten CLI commands. The independent full suite passed all 79 methods in both modes: 36 original tests and 43 additional storage/server tests. JOURNAL_TEST_EXECUTION.md retains the complete logs and tested source identities, including actual interrupted-write recovery and concurrent-process checks. These results are local execution, not hosted-CI or Alexa acceptance.
This feature completes the existing durable-journal issue #2, preserving Z-Obsidian-6F2C's design and the original HomeOps product and competition lineage.
python -m homeops_relay.demo runs an entirely synthetic kitchen-leak flow:
record a leak observation and evidence references;
record two synthetic quotes;
produce an evidence-linked plan;
request a provider-contact action without executing it;
export a deterministic snapshot and verify the full event chain.
The submission storyboard in DEVPOST_SUBMISSION.md turns the same flow into a voice-first <3 minute demo without inventing Alexa runtime evidence before an actual deployment exists.
No provider contact, booking, purchase, payment, claim filing, account mutation, or home-system control is implemented.
A recorded quote is explicitly CALLER_SUPPLIED_UNVERIFIED.
APPROVE means APPROVED_NOT_EXECUTED; it does not authorize or prove an external side effect.
MCP transport hardening is part of the product: lifecycle/session checks, protocol-version pinning, Origin validation, request limits, per-session tool-call limiting, and deterministic JSON-only responses.
No AWS/Alexa/Devpost credential is stored here.
Final entrant identity, eligibility, Devpost registration, live Alexa+ integration, deployment, video, and submission remain separate owner/account actions.
HomeOps Relay is licensed under Apache-2.0; see LICENSE.
This server cannot be deployed
Homeowner's AI: view & update appliances, warranties, documents & maintenance for your home.
Property management AI: work orders, vendors, appliances, and triage for Claude and ChatGPT.
AI transaction coordinator + legal-matters platform for real estate and law firms.
Multi-expert decision intelligence with transparent synthesis and auditable workflows.
