Skip to content

Build around family life

Your assistant.
Your Nidox.

Connect a compatible external assistant to a family’s Nidox organiser through the Model Context Protocol. Existing accounts. Explicit permissions. Changes reviewed in Nidox.

Connect an assistant

No extra Nidox app and no administrator API key.

  • Add the remote MCP endpoint in a compatible client. The client opens a Nidox browser sign-in and consent flow. Availability depends on the pilot settings.
  • Sign in to your existing Nidox account. Select a family, inspect the client identity and approve only the requested permissions you need. Denying the request does not affect your family.
  • The connection uses delegated OAuth access, authorization code with PKCE and credentials intended for the Nidox MCP resource. Do not paste a Firebase token, password or service-account key into an assistant.
  • Closing the Nidox browser tab does not disconnect the assistant. Use Settings → Connected apps to inspect permissions and revoke its access.

Permissions stay narrow

A connection never increases a family member’s role.

  • Read and write permissions are separate for calendar, chores, shopping and meals. Each grant is tied to your account, one client and one selected family.
  • Every tool call checks the active connection, account status, scope and current membership. Revocation, lost membership or account deletion must stop access even if a previously issued credential has not expired.
  • Private imported calendars, private assistant history, contacts, documents, Follow Me locations, invitations, billing and account deletion are outside this first integration.
  • The assistant receives data covered by its approved tools. That data leaves Nidox and is subject to the external provider’s policy. Revocation prevents future access; it cannot recall already received copies.

Prepare → review → save

An assistant proposal is not yet a saved family change.

  • Read tools return bounded, structured information. Prepare tools validate a draft and return a review link. Open that link in Nidox to inspect the exact changes.
  • An authenticated person approves or rejects the draft in Nidox. A model saying “confirmed” is not approval. Approval is bound to the exact draft, account, connection, family and expiry.
  • Action status distinguishes awaiting approval, saved, rejected, expired and failed. Retrying an approval must not create duplicate events, chores, shopping items or meal slots.
  • For a week of the same breakfast, resolve the existing saved recipe first and prepare one multi-day plan. If several recipes match, ask which one instead of generating a new dish.

Compatibility & limits

A small, deliberate integration with clear boundaries.

  • The endpoint uses Streamable HTTP. Local SDK transport tests cover protocol versions 2026-07-28, 2025-11-25 and 2025-03-26; this does not certify any third-party assistant. A client must also support OAuth discovery and the required authorization flow.
  • Request rates, page sizes, date ranges and batch sizes are limited. Clients should respect retry responses and show action status truthfully, rather than silently repeating a write.
  • Reading data and preparing ordinary actions do not invoke Nidox’s language model. External assistant usage follows its provider’s pricing. Any future tool explicitly using Nidox AI must use Nidox’s plan and allowance checks.
  • This pilot is not a promise of universal client support or an additional subscription entitlement. Contact support with the client name and a request ID; never send credentials or private family exports.

MCP

The first tool set

ToolWhat it doesPermission
get_familyRead the selected family’s minimal context.family:read
list_eventsprepare_eventRead dated family plans; prepare a new event for review.calendar:read / calendar:write
list_choresprepare_choreRead chores; prepare a task with its assignee and schedule.chores:read / chores:write
list_shoppingprepare_shopping_itemsRead lists; prepare bounded shopping additions.shopping:read / shopping:write
list_mealsRead existing dated family meal plans.meals:read
prepare_meal_planPrepare dated meal slots and servings. Both permissions are required.meals:write + recipes:read
search_recipesFind saved and catalogue recipes without generating another dish.recipes:read
get_action_statusCheck the outcome of a prepared action belonging to this connection.Original action permission

Start with something useful

“What is on our family calendar this week?”
“Add oat milk and apples to our shopping list.”
“Plan our saved müesli for breakfast this week, for three people.”