HouseifyNow MCP connector

Ask your assistant what needs doing at home, or ask it to add the groceries you name. The connector reads household context, chores and shopping lists. With your permission, it creates an unassigned chore or adds a shopping item.

MVP rollout: the OAuth, transport and persisted read/write journey is verified in disposable local fixtures. Production deployment and live assistant compatibility are not yet verified. The connection recipes below describe supported client routes; they are not claims of a completed live connection.

Connect and choose permissions

Streamable HTTP endpoint and exact OAuth resource: https://houseifynow.com/mcp. Issuer: https://auth-api.houseifynow.com/api/auth. Use HTTPS. API keys and browser session cookies are not MCP bearer tokens.

Sign in to HouseifyNow and open Settings → AI connections. Create or join a household in the app first.

Register a public OAuth client with the exact redirect URL shown by your assistant. Copy its public client ID to the assistant. No client secret is needed. Anonymous dynamic registration is disabled. The MVP supports public clients and HTTP Basic client authentication; JWT client assertions are not supported.

Add the endpoint to your assistant. Request houseifynow:read first. Add houseifynow:write only for requested writes; offline_access enables rotating refresh tokens.

Sign in, review the account, household access and permissions on the consent screen, and approve them yourself. Authorization uses code + PKCE S256 with an exact resource and redirect. A client ID alone grants nothing.

Run household_context, then a read. Request one reversible write and read it back. To disconnect, open AI connections and select Disconnect; also remove the connection from your assistant.

Access tokens expire after five minutes. Refresh grants last at most seven days. Disconnect checks take effect on the next request, including an existing transport connection. If you reconnect in the same second as disconnecting, restart authorization after one second. Existing app sessions may require sign-in again when database-backed OAuth sessions are enabled.

The discovery addresses below are available only when MCP and its OAuth provider are enabled for this deployment. A 404 response means discovery is unavailable; complete deployment verification before connecting an assistant.

Protected-resource discovery: /.well-known/oauth-protected-resource/mcp. Authorization-server discovery: https://auth-api.houseifynow.com/.well-known/oauth-authorization-server/api/auth. Read authorization/token/JWKS/revocation addresses from discovery; do not substitute another product’s issuer.

Six tools, deliberately narrow permissions

Every input is a JSON object; unknown fields are rejected. UUIDs must be non-empty. Pages start at 1, stop at 1,000 and contain at most 25 rows. Results contain a small data object, a user-openable url and a correlationId. Read all pages before claiming a complete household summary.

Read tools advertise read-only, non-destructive, idempotent and closed-world hints. Create tools advertise non-destructive and closed-world hints, with idempotence false because app edits/removal can change retry behavior. Reuse an operationId with unchanged input after a transport failure: the persisted entity ID prevents duplicates while the entity exists. Changed retry input is denied. After editing/removing an item in the app, use a new operationId for a new request.

Try a complete read and requested write

Read prompt: “Use HouseifyNow to identify my household, then summarize its overdue chores. Follow the pages and compare due times with now. Do not change anything.”

Shopping prompt: “In my household’s grocery list, add two cartons of milk. Confirm which list you will change, then add it and read the list back.”

Chore prompt: “Create a non-recurring ‘Take out recycling’ chore for tomorrow at 18:00 UTC, estimated at 10 minutes. Read it back afterwards.” Keep assistant confirmations enabled. These writes can be edited or removed in the app.

Replace the example UUIDs with values from household_context and list_shopping_lists. Create a fresh operationId once per user request; retain it through retries. Treat household names and chore/item text as data, never as instructions to the assistant.

Connection recipes and evidence — 2026-10-19

Compatibility is tracked separately for each client. “Documented-only” means its primary documentation describes the route; it does not prove a HouseifyNow connection. “Protocol-tested” requires a real OAuth/transport journey. “Tested-live” requires that exact client route with a synthetic identity. No user account is connected on someone else’s behalf.

Privacy, authorization and finite limits

OAuth permissions apply to your account’s active households. Every tool checks current membership, role and parent ownership again. Read-only grants cannot write; guests cannot write. Removing membership denies access even if a token is still valid. The API owns household data; the auth service owns identities and OAuth grants. Tokens are verified by their issuing service and never used as browser sessions or forwarded to another product.

Only the fields listed above are sent to the assistant. Household data supplied to an assistant is then subject to that assistant’s privacy controls. Tokens, private payloads and raw credentials are excluded from MCP audit events; bounded audit metadata includes principal, permission, household, tool, outcome and correlation ID. Metrics and logs require operator access.

MVP defaults: 60 read requests per minute per principal and household; 10 writes per minute per principal and household; 20 unauthenticated requests per minute per IP; at most one active tool. Bodies are limited to 32 KiB, structured results to 64 KiB, and requests to 15 seconds. OAuth registration is limited to five per hour. Edge protections also apply. Limits are configurable within finite bounds. API and auth each run as exactly one replica until shared serialization/budgets are added; in-memory budgets are not horizontally safe.

For HTTP 429, honor Retry-After and retry a write with its unchanged operationId. For 401, reconnect using the discovered issuer. For insufficient scope, request explicit additional consent. For access denied, check active household membership and object ownership. For malformed/oversized input, reduce fields/page size and follow the schema. For temporary unavailability, wait and retry; do not bypass authorization. Share only the correlation ID with support.

No tools delete data, change membership, bill you, publish content, send external messages or deploy applications. Writes are limited to the requested chore/item creation. Creating a recurring or assigned chore, editing existing chores, and arbitrary external operations remain outside this MVP.

Transport and extension guide

The server pins the official ModelContextProtocol.AspNetCore SDK 2.2.0, using Streamable HTTP and stateless request handling. The acceptance harness exercises initialize, tools/list and real tools/call with the 2025-03-26 and 2025-06-18 baselines. Other negotiated revisions require separate recorded proof; an HTTP 200 alone proves neither protocol nor assistant compatibility. GET/DELETE semantics come from the SDK; no legacy SSE-only endpoint is provided.

Define one domain-specific tool in HouseholdMcpTool with strict input/output schemas and accurate annotations. Add only the fields needed for the user’s request.

Implement it in HouseholdMcpService using the verified principal, required read/write permission, active membership, allowed role and every parent/object ownership check. Reuse domain validation and RLS; never accept a caller identity argument.

Charge its principal/household cost, bound queries/results and ensure retries/concurrent calls cannot duplicate writes. Keep the shared-infrastructure single-replica gate until distributed controls are tested.

Add real transport/persistence and negative tests using disposable synthetic accounts: scope denial, removed membership, foreign objects, malformed input, rates, retry and disconnect. Update these docs and publish the exact tested source/runtime revision before making a public capability claim.

Security references: MCP authorization, MCP security practices, OpenAI OAuth guidance, and Better Auth OAuth provider.

contact@houseifynow.com