Home Energy Sentinel
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.
Home Energy Sentinel
What it is
Home Energy Sentinel is a small Alexa+ simulated experience for preparing safer time-of-use energy plans. It demonstrates a conversational agent that can read state and propose an action while a human retains final authority.
Related MCP server: Relay
Why it matters
Energy plans combine changing tariffs, device deadlines, and a household power limit. A useful proposal can become unsafe when the underlying tariff or home state changes. This project makes that boundary visible instead of silently applying an outdated decision.
Demo
The local one-screen demo shows:
a conversational read of the synthetic home state;
a proposed overnight schedule with
HUMAN APPROVAL REQUIRED;explicit human Approve or Reject actions;
before/after evidence and an audit event;
STALE_PROPOSALwhen the synthetic tariff changes; anda fresh proposal after rereading the new state.
How it works
The deterministic policy finds a cheap overnight window and schedules the water heater and EV sequentially without exceeding 7 kW. The agent first reads the state, then creates a pending proposal. Proposal creation never mutates the active plan.
Human approval boundary
The agent client has an agent role and cannot approve a proposal. A separate
human client must call approve_energy_plan. The server rejects approval from
the agent role, and the UI keeps the approval buttons separate from the agent
conversation.
Stale decisions
Every proposal stores the tariff, consumption, and active-plan fingerprints it
was based on. If any of them changes, approval returns STALE_PROPOSAL and the
canonical plan remains unchanged. Repeating an already applied approval is
idempotent and does not create a duplicate event.
Architecture
src/server.js— local MCP Streamable HTTP server and role checks.src/client.js— minimal MCP client used by the harness and UI.src/contracts.js— typed tool definitions and schemas.src/domain.js— synthetic state, proposals, approvals, and audit events.src/policy.js— deterministic schedule validation and planning policy.conversation/— conversational policy harness using the real MCP server.ui/— local web simulation using the same MCP server.test/— protocol, domain, conversation, and UI tests.evidence/— reproducible transcripts, results, and demo materials.
Run locally
Requirements: Node.js 22 or later. The project has no external runtime dependencies and does not require an account or cloud service.
npm run demo-uiOpen http://127.0.0.1:8788.
The CLI/conversation alternatives are:
npm start
npm run demo
node conversation/demo.jsRun tests
npm testExpected result: 12 tests passed, 0 failed.
Synthetic data disclosure
All tariffs, device identifiers, schedules, consumption values, and audit events are synthetic fixtures. No real tariff provider, meter, customer account, or smart-home device is connected. The project makes no claim of real energy savings.
Alexa+ simulation disclosure
This repository uses the Alexa+ simulated-experience path permitted by the hackathon. The MCP server itself is real and implements MCP 2025-11-25 over Streamable HTTP, but the demo does not claim to be connected to Alexa+ or an Alexa device. The agent is a deterministic policy harness, not an LLM.
Limitations
There is no live Alexa+ account, OAuth integration, remote deployment, authentication service, persistence, multi-user support, real device control, or production tariff integration.
License
MIT — see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Trusted execution infrastructure for AI agents. Proposal-only protocol with human consent.
Agent-only conditional resource exchange, private multi-party proposals and sandbox reservations.
Contract-change authorization for AI agents: preflight a change to an API or MCP contract, get a signed decision, and verify the receipt offline. Only a granted change can proceed.
Merged free/busy, find mutual time, propose bookings with human approval. Never event contents.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables persistent household routine planning with interruption replanning, preserving completed progress and rejecting stale updates through MCP tools over Streamable HTTP.MIT
- AlicenseNot gradedqualityBmaintenanceEnables explainable household replanning by generating reviewable schedule proposals from constraint solving, with transactional MCP tools for retrieving state, proposing changes, committing approved plans, and undoing previous plans.MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to read campaign and account data freely while routing every write through human-approved plans, with budget caps, drift refusal, undo, and audit logging.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to hand over a household's routine safely: it detects calendar clashes, asks one clarifying question, proposes a revision, and transfers ownership only after explicit, idempotent confirmation, with stale proposals re-planned and every change explained from an auditable log. Read-only overview, changelog and handoff resources support subscriptions so multiple client sessions stay in sync.MIT