Model Context Protocol

Let an authorized assistant help with the daybook.

Family Daybook exposes a focused set of MCP tools through secure OAuth sign-in. An assistant receives only the access you authorize and remains subject to the app’s workspace, role, validation, and history rules.

Connection

One canonical endpoint

Add this Streamable HTTP endpoint to a compatible MCP client. The client discovers OAuth requirements and asks you to authorize the requested scopes.

Streamable HTTP MCP endpoint

https://www.myfamilydaybook.com/mcp
  1. Add the endpoint in your MCP client.
  2. Sign in to Family Daybook through the OAuth window.
  3. Review and authorize only the scopes the assistant needs.

OAuth permissions

Access is explicit and scoped.

daybook:read

Read the authorized workspace context, visible days, and care-entry history.

daybook:write

Create and update open-day records and prepare corrections to finalized records.

daybook:finalize

Prepare and confirm finalization of an open care day.

Tool catalog

Ten tools with bounded responsibilities.

Tool names and descriptions below are generated from the same catalog used by the live MCP server.

Context and records

get_daybook_contextdaybook:read

Get Daybook Context

Get the authorized member role, workspace timezone, local date, and active child/caregiver references.

get_daydaybook:read

Get Day

Get a visible care day with tasks, entries, completion, and its concurrency version.

get_care_entrydaybook:read

Get Care Entry

Get a visible care record, its current version, and revision history.

Open-day updates

create_care_entrydaybook:write

Create Care Entry

Create a routine, special-arrangement, or factual custom care entry.

update_care_entrydaybook:write

Update Care Entry

Update an existing record while its care day is open.

update_day_notesdaybook:write

Update Day Notes

Replace notes on an open care day.

Protected final changes

preview_care_entry_correctiondaybook:write

Preview Care Entry Correction

Preview a correction to a finalized record and issue a five-minute confirmation handle.

confirm_care_entry_correctiondaybook:write

Confirm Care Entry Correction

Consume a correction confirmation handle and append the unchanged proposed revision.

Requires a valid preview confirmation

preview_day_finalizationdaybook:finalize

Preview Day Finalization

Return the exact open-day summary and a five-minute confirmation handle.

confirm_day_finalizationdaybook:finalize

Confirm Day Finalization

Consume a finalization handle and finalize the exact unchanged day it represents.

Requires a valid preview confirmation

Safeguards

Sensitive actions stay deliberate.

Separate permissions

Read, write, and finalization scopes are granted separately during OAuth authorization.

Fresh versions

Updates carry current record or day versions so stale requests fail instead of overwriting newer work.

Preview, then confirm

Corrections and finalization are previewed first. Confirmation applies only to the exact unchanged preview.

Workspace boundaries

Every operation repeats the same membership, role, billing, and workspace checks used by the private app.

Owner and reviewer access

Owners can use authorized read, write, and finalization tools. Reviewers remain read-only and can see only finalized records available to their membership. Billing eligibility follows the workspace owner.

Important limits

  • An assistant cannot cross workspace boundaries or expand the signed-in member’s role.
  • Identifiers must come from authorized reads; tools are instructed never to guess them.
  • Stale record and day versions fail and must be fetched again.
  • A preview does not change data, and confirmation cannot be inferred or automatic.
  • Family Daybook does not independently verify user-entered facts or attachments.
  • The MCP connection is a recordkeeping aid, not legal, medical, or emergency advice.