How it's built
An MCP service, stateless by design.
For the technically curious. Everyone else: here's how it works.
The shape of it
Muse House is an external MCP (Model Context Protocol) service, consumed through a custom Muse connector. It speaks Streamable HTTP on a single /mcp endpoint and answers every request with one plain JSON body — no Server-Sent Events, no sessions, no streaming. Boring on purpose: it's the most compatible shape for review pipelines and egress proxies.
The endpoint
POST https://mymuse.house/mcp · GET https://mymuse.house/health
No authentication on the public blueprint tier. No accounts, no API keys, no login walls.
Ten tools
Blueprints: suggest_utilities ranks which Muse connectors a household should turn on. suggest_steps builds the operating plan. list_rooms and get_room_brief serve the nine room blueprints. get_house_template mints starter HOUSE.md / OP-PROC.md. stamp_rooms returns the executable room-creation protocol the host agent follows. check_room_updates compares a house's recorded room versions against the live blueprints and returns patch-or-restamp guidance.
Governance: codex_check runs a planned action against the 22-term consumer codex — advisory, not a gate.
Feedback: send_feedback relays structured, user-confirmed feedback to the team inbox (personal data redacted server-side); get_feedback_form serves the form schema so hosts present it consistently.
Stateless means stateless
The service stores nothing: no user data, no conversation history, no identifiers. Tool arguments are not persisted. Your board, routines, approvals, and connected accounts live inside your own Muse — never here. Feedback messages are forwarded to the support inbox and forgotten; only anonymous rate-limit counters exist, in memory, never on disk. The privacy policy says the same thing at greater length.
Open source
The whole thing is public: 0xRayAI/muse-house (MIT). Run it yourself with node src/server.mjs — the Dockerfile is in the repo. Machine-readable docs live at llms.txt.
Status
Submitted to the Muse Connector Directory; in review. Until then, add it as a custom connector — the homepage walks through it.