FixLoop
Sends approved repair request emails through the Resend API, including recipient handling and idempotent delivery.
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., "@FixLoopmy kitchen faucet is leaking, capture and diagnose it"
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.
FixLoop
Voice-first household incident recovery, built as an Alexa+ concept simulation (not an official Alexa product; no native Alexa/Echo integration is claimed).
Status
See docs/IMPLEMENTATION_STATUS.md for what genuinely works today.
Related MCP server: Latchbook
Run locally (no Docker required)
pnpm install # pnpm 12, Node >= 22
cp .env.example .env
pnpm db:start & # real PostgreSQL 17 via embedded-postgres on :54329 (or: docker compose up -d)
pnpm db:migrate && pnpm db:seed
pnpm dev # API + MCP at http://127.0.0.1:4000 (POST /mcp)
pnpm verify # typecheck + testsDelivery: simulated or real email
After you approve a repair request, FixLoop delivers it one of two ways, chosen by DELIVERY in .env:
simulated(default): the request is stored in the localProviderRequesttable. No technician is contacted.email: the exact approved text is emailed through the Resend API. SetEMAIL_API_KEY,EMAIL_FROMandTECHNICIAN_EMAIL. With Resend's test sender (onboarding@resend.dev) mail can only go to the address that owns the Resend account, so use that address asTECHNICIAN_EMAILto try it safely.
In email mode the recipient address is on the approval card, is covered by the approval hash, and the request is sent at most once (the request's idempotency key is the email service's Idempotency-Key). The demo scenarios that submit a request or inject faults are disabled, because they only make sense with the simulated provider.
This server cannot be deployed
Maintenance
Related MCP Connectors
Collision-first MCP diagnostics for MCP, API, webhook and agent failures. Returns structured evidence, bounded repair guidance, agent compatibility checks and safe recovery routing.
MCP server for OnceAsk, the AI-native current-address layer for people and agents.
An authenticated remote MCP server for user-owned devices and one-shot capability invocation.
Experimental MCP server for current empirical verification of explicit public HTTPS endpoint claims.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that gives an Alexa+ household a durable operational memory for home repairs, warranties, and service cases, enabling multi-turn troubleshooting, provider booking, and reminders.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables an MCP client to resolve household appliances, retrieve local manual/warranty/incident records, compare a stored warranty date, review persistent service case history, and draft cited repair cases that only a human can approve or close before export.MIT
- AlicenseNot gradedqualityBmaintenanceEnables an Alexa+ host to remember a household's appliances, filter sizes, shut-off valves and past repairs, so it can triage a breakdown, walk through personalised repair steps hands-free, order the exact-fit part through a confirmed checkout, or hand a professional a complete job brief. Exposes 12 MCP tools plus 8 MCP Apps widgets over Streamable HTTP, secured by OAuth 2.1 with PKCE and scoped read/write access to home and order data.2 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables Alexa+ and other MCP clients to diagnose household appliance problems through safety-reviewed triage steps, find model-fit parts, place explicitly confirmed orders, and schedule delivery follow-ups and preventive maintenance. Every case, order, and reminder persists per household, so conversations resume from any device days later.MIT