# Muse House — llms.txt Muse House is a stateless MCP blueprint service that turns a Muse assistant into a personal operating house: rooms (Money, Travel, Home, Health, Game, Art, Dev), a foundry that mints personalized setups, and a mill of daily routines. ## Endpoints - MCP (Streamable HTTP, plain JSON responses, no SSE): POST https://mymuse.house/mcp - Health: GET https://mymuse.house/health - Website: https://mymuse.house/ - Configurator: https://mymuse.house/configurator.html - Privacy: https://mymuse.house/privacy.html - Terms: https://mymuse.house/terms.html - Source: https://github.com/0xRayAI/muse-house - Help & feedback: https://mymuse.house/help.html (form POSTs to /api/feedback, forwarded via Resend to support@mymuse.house; nothing stored server-side) - Tech architecture: https://mymuse.house/tech.html ## Auth None. The public blueprint tier needs no key or login. The service is stateless and stores no user data. ## MCP tools (10) - suggest_utilities(profile, goal): rank Muse connectors a household should turn on, with a one-line why each. - suggest_steps(goal, utilities): ordered operating plan the host executes. - list_rooms(): the nine room blueprints with one-line descriptions. - get_room_brief(room): full blueprint — purpose, connectors, onboarding fills, mill jobs with specs, board cards, ask-first list, side-chat seed. - get_house_template(owner_name?, timezone?): starter HOUSE.md + OP-PROC.md with {{TOKENS}} filled where given. - stamp_rooms(rooms, owner_name): the executable room-creation protocol — returns the exact steps and verbatim seed the host sends to mint rooms. - codex_check(action): advisory PASS / ADVISORY / FLAG against the 22-term consumer codex. Not a gate — the host decides. - send_feedback(kind, room, summary, details): relay user-initiated feedback to the Muse House team. Only call when the human explicitly asks AND confirms the exact text. Never forward personal data — the service redacts obvious patterns server-side. Rate-limited; nothing is stored. - get_feedback_form(): the feedback form schema — fields, allowed values, limits, privacy note. Present it conversationally before send_feedback. - check_room_updates(rooms): diff the house's recorded room blueprint versions against the live product; returns upgrades with a patch (send to the room chat) or re-stamp (recreate via stamp_rooms) path. Run weekly. ## Usage pattern 1. suggest_utilities → user enables connectors in the Muse app. 2. get_house_template → host writes the household's HOUSE.md / OP-PROC.md. 3. list_rooms → get_room_brief per room → one side chat per room, seeded. 4. suggest_steps → host creates the mill crons and hooks. 5. codex_check before anything irreversible. ## Privacy Stateless by design. No accounts, no stored user data, no conversation history. Tool arguments are not persisted. See /privacy.html.