# Connect Home Range to an assistant Home Range exposes an authenticated, Streamable HTTP MCP endpoint at: https://homerange.app/mcp The endpoint uses your Home Range account and live database. Changes notify connected boards immediately. It does not require a computer to remain running. Assistants read their own guide to Home Range through the endpoint's `get_guide` tool. ## Connect from ChatGPT 1. On the ChatGPT **website**, sign in to your own account. 2. Open **Settings → Security and login → Developer mode** and enable it. 3. Open **Plugins**, select **Add → Create MCP App**, and create a connection named **Home Range** with the MCP URL above. 4. Choose **OAuth**. Under **Advanced OAuth settings**, use **Dynamic Client Registration (DCR)** (automatically selected after discovery); no client ID/secret is needed. This server issues public OAuth clients using PKCE; it does not require a client secret. If asked for scopes, use `choreclub`. 5. Approve the connection on your own phone or computer. A shared tablet cannot connect an assistant. If the device isn't signed in yet, sign it in (a parent's email and the six-digit code that is emailed, or shown in Settings → Devices on another parent's device) and choose yourself when it asks who uses it; it then goes straight on to the consent page. The request lasts ten minutes, so if it has expired by then, start connecting again from ChatGPT. Check the family and return address on the consent page. Only a parent can connect, and the connection manages the whole family; a child's device is turned away. 6. Start a new chat, select Home Range from the tools/developer-mode menu (or @ mention it where supported), and ask it to read today's chores first. 7. On your phone, sign in to the **same ChatGPT account**, open a new conversation, and check the plugin/tool picker. If Home Range appears, select it and try the same read-only request, then add a test chore. If the private draft does not appear, use the ChatGPT website; native-phone availability of developer-mode drafts is not guaranteed by the documented web setup. A private workspace distribution or reviewed public plugin is a separate distribution option. OpenAI documents developer mode for Plus, Pro, Business, Enterprise and Education **on the web**. Its general plugin documentation supports mobile plugins available to the account, but that alone does not establish native-mobile availability of every private developer-mode draft. Test the actual account/device; do not claim native-phone installation was verified without doing so. - https://developers.openai.com/api/docs/guides/developer-mode - https://developers.openai.com/plugins/deploy/connect-chatgpt - https://learn.chatgpt.com/docs/plugins Write tools may prompt for confirmation. Refresh the connection's tools after a tool-schema update. This endpoint is ready for a personal developer-mode connection; it has not been published in the public directory. To disconnect an assistant, use Settings → Devices in the app. Unlinking it in ChatGPT alone should not be assumed to revoke the grant. ## Implementation and security - MCP uses the official TypeScript SDK, stateless Streamable HTTP, and per-call authenticated identity. No sticky sessions or extra worker service is required. - The same validated HTTP/tRPC APIs serve the UI and MCP. MCP calls a fixed loopback URL, with code-defined routes, using an OAuth bearer token. Tool arguments cannot choose a host or arbitrary route. - OAuth uses SDK discovery/DCR/authorization-code parsing and S256 PKCE. Clients are public (`token_endpoint_auth_method:none`). Authorization codes are single-use, five-minute, client/redirect-bound; consent forms have a session-bound random CSRF token and require the canonical Origin. - OAuth resource is the canonical `/mcp` URL. Supplied resource indicators must match. Scope `choreclub` grants the connecting person's app capabilities, never more. No password grant or anonymous data tools exist. - Access tokens expire after one hour. Refresh tokens rotate, last up to a year, and reuse revokes the connection. Only token hashes are stored. Token revocation (RFC 7009) ends the connection when a client uses it. Each grant is a device of its own in the family's device list, belonging to the person who made it; signing that device out, or archiving the person, ends the connection. - Authentication happens on every MCP call and again at the API boundary. Admin checks, child restrictions, household-scoped queries and optimistic versions are shared with the app. - A connection belongs to one family and cannot reach another. - Each connection may make 1,000 MCP calls and 100 changes per 15 minutes. Requests that carry an Origin header must come from the app's own origin or `https://chatgpt.com`. - Secrets stay out of tool arguments and results, with one deliberate exception: `create_sign_in_link` returns a one-time link that signs a phone in as a child, for the parent to send them. PINs, raw private calendar URLs and other credentials are entered only in the app. Tool annotations accurately distinguish reads, writes and destructive account actions. - `APP_ORIGIN` must be the canonical public HTTPS origin (without `/mcp`). Railway's `RAILWAY_PUBLIC_DOMAIN` is the fallback. Local testing defaults to `http://127.0.0.1:`.