daybook:readRead the authorized workspace context, visible days, and care-entry history.
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
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/mcpOAuth permissions
daybook:readRead the authorized workspace context, visible days, and care-entry history.
daybook:writeCreate and update open-day records and prepare corrections to finalized records.
daybook:finalizePrepare and confirm finalization of an open care day.
Tool catalog
Tool names and descriptions below are generated from the same catalog used by the live MCP server.
get_daybook_contextdaybook:readGet the authorized member role, workspace timezone, local date, and active child/caregiver references.
get_daydaybook:readGet a visible care day with tasks, entries, completion, and its concurrency version.
get_care_entrydaybook:readGet a visible care record, its current version, and revision history.
create_care_entrydaybook:writeCreate a routine, special-arrangement, or factual custom care entry.
update_care_entrydaybook:writeUpdate an existing record while its care day is open.
update_day_notesdaybook:writeReplace notes on an open care day.
preview_care_entry_correctiondaybook:writePreview a correction to a finalized record and issue a five-minute confirmation handle.
confirm_care_entry_correctiondaybook:writeConsume a correction confirmation handle and append the unchanged proposed revision.
Requires a valid preview confirmation
preview_day_finalizationdaybook:finalizeReturn the exact open-day summary and a five-minute confirmation handle.
confirm_day_finalizationdaybook:finalizeConsume a finalization handle and finalize the exact unchanged day it represents.
Requires a valid preview confirmation
Safeguards
Read, write, and finalization scopes are granted separately during OAuth authorization.
Updates carry current record or day versions so stale requests fail instead of overwriting newer work.
Corrections and finalization are previewed first. Confirmation applies only to the exact unchanged preview.
Every operation repeats the same membership, role, billing, and workspace checks used by the private app.
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.