io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026
Family planner for schedules, tasks, checklists, plans and attachments, shared by household.
Local stdio bridge to the Familia household planner, letting an assistant read schedules and create or edit shared tasks, plans and checklists.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
famboard is a small local bridge to Familia's hosted MCP server, a planner that households share for their schedules, tasks, checklists, plans and attachments.
The bridge keeps no family data and plans nothing on its own. It serves the upstream server's tool list locally, exactly as captured from the live endpoint, and forwards each tool call upstream, returning the result untouched. Reads and writes alike travel that path: creating a task or editing a plan through famboard is creating or editing it in Familia itself, on the caller's own households.
Schedule and overview reads:
familia_list_households — the households, families
or shared boards available to the caller, with member
names and user ids. No arguments.familia_list_household_members — active and pending
members of one household. Required: householdId.familia_get_day_overview — tasks, plans and calendar
events for a date or time window.familia_get_today_schedule — today's agenda, with an
overdue summary.familia_get_tomorrow_schedule — tomorrow's agenda,
with an overdue summary.familia_get_next_up — the next upcoming items, in
personal or household scope.familia_get_weekly_overview — a multi-day planning
overview, 1 to 14 days.familia_get_inbox — items needing attention.familia_list_past_due — overdue tasks and other
unfinished leftovers; calendar events are excluded.familia_search_items — find tasks, plans and calendar
events by text. Required: query.familia_find_free_days — runs of consecutive days
without hard availability blockers. No required
arguments.Tasks and plans:
familia_create_task — a responsibility-style task,
chore or reminder, optionally recurring or carrying a
checklist. Required: householdId, title.familia_create_list_task — a shopping list, packing
list or other checklist task. Required: householdId,
title, items.familia_create_plan — a plan item for an event, trip,
school activity, holiday or similar. Required:
householdId, title.familia_update_task — rename, reschedule, reassign or
complete a task. Required: agreementId.familia_cancel_task — cancel a task without deleting
its record. Required: agreementId.familia_delete_task — permanently delete a task.
Required: agreementId.familia_update_plan — edit a plan's title, schedule,
location, participants or linked tasks. Required:
planItemId.familia_delete_plan — delete a plan item. Required:
planItemId.familia_batch_write — run several task, list-task,
plan or attachment writes as one ordered batch.
Required: operations.Attachments:
familia_list_attachments — photos and lists attached
to a task or plan. Required: targetType, targetId.familia_attach_image — attach a JPEG, PNG or WebP
image to a task or plan. Required: targetType,
targetId.familia_create_list_attachment — add a new checklist
to a task or plan. Required: targetType, targetId,
items.familia_update_list_attachment — replace the contents
of an existing list attachment. Required:
attachmentId, items.familia_delete_attachment — delete a photo or list
attachment. Required: attachmentId.FAMILIA_MCP_URL (optional) — override the upstream
endpoint. Defaults to https://mcp.family.asynq.org/mcp.
(The override hook is this rebuild's own labelled
reconstruction.)FAMILIA_API_KEY (optional) — when set, every
upstream request carries an
Authorization: Bearer <key> header. When it is not
set, no auth header is sent. (This forwarding is also
a labelled reconstruction; the original surface was
captured keyless.)On the first tool call the client opens a streamable
HTTP session with the upstream: a JSON-RPC initialize
request (protocolVersion 2025-03-26, clientInfo name
famboard), then a notifications/initialized
notification, then the tools/call request carrying
the caller's arguments unchanged. When the upstream
answers initialize with an Mcp-Session-Id header,
that value rides on every later request of the session,
which is reused for the life of the process. Replies
may arrive as plain JSON or as server-sent events;
both are read.
Successful upstream results pass through verbatim,
including any isError flag the upstream sets.
Failures — a JSON-RPC error, a non-2xx status, an
unreadable response, or a request that cannot be
completed — come back as an isError result whose
text starts with famboard error: (this rendering
is this rebuild's own labelled reconstruction).
Each tool is also a subcommand taking one JSON argument string (omit it for tools that take none):
Exit codes: 0 on success, 1 on an isError
result, 2 on a usage error.
MCP client config:
The container's default command is mcp, so the first
form is a stdio MCP server; any other arguments reach
the CLI normally.
The test suite runs entirely against a stubbed JSON-RPC upstream — no live network calls.
MIT — see LICENSE.
Source: README.md at commit 3f2d8b4
List Familia households
Use this when the user asks which Familia households, families, or shared boards are available. Includes member names and user ids for assigning tasks or plans. Do not use for listing tasks, plans, or calendar events.
Takes no parameters.
List Familia household members
Use this when a task or plan must be assigned to, owned by, or shared with a named household member and their Familia user id is not already known.
timezonehouseholdIdrequiredGet day overview
Use this when the user asks for Familia items on a specific date or in a specific time window. Includes tasks, plans, and connected calendar events. Do not use for broad text search or multi-week availability.
dateendAtstartAttimezonehouseholdIdincludeCompletedWhat am I doing today?
Use this when the user asks about today's agenda, today's tasks, what they are doing today, or what they should do today. Includes tasks, plans, Google/calendar events, and an overdue summary.
timezonehouseholdIdWhat am I doing tomorrow?
Use this when the user asks about tomorrow's agenda, tomorrow's tasks, tomorrow's plans, or what they should prepare for tomorrow. Includes tasks, plans, Google/calendar events, and an overdue summary.
timezonehouseholdIdNext up
Use this when the user asks what is next, what they should do now, their next task, or the next upcoming family item. Defaults to personal assigned items; use household scope only for family-wide wording. Never describe owner-only tasks as assigned to the current user.
limitscopetimezonehouseholdIdWeekly overview
Use this when the user asks about this week, the next week, upcoming days, family schedule for the week, or a multi-day planning overview.
daystimezonestartDatehouseholdIdInbox / needs attention
Use this when the user asks for inbox, items needing attention, overdue tasks, past leftovers, unfinished responsibilities, or what is waiting on them.
limittimezonehouseholdIdList past leftovers
Use this when the user asks for overdue items, past leftovers, missed tasks, unfinished items from previous days, or Czech “resty”. Calendar events are excluded.
limittimezonehouseholdIdSearch family board items
Use this when the user asks to find Familia tasks, plans, or connected calendar events by title, notes, description, or location. Do not use for public web search or unrelated document search.
limitqueryrequiredoffsettimezonehouseholdIdCreate task
Use this when the user asks to create a responsibility-style Familia task, agreement, reminder, or chore. If the same task repeats across several days, weeks, or months, provide repeatRule and create one recurring task instead of multiple one-time tasks. Do not use for calendar-style events, trips, school activities, or holidays; use familia_create_plan instead. When the primary intent is a shopping list, packing list, or standalone checklist, use familia_create_list_task. Assigning to another household member queues a push notification; schedules can also queue reminders, and delivered notifications cannot be recalled.
dueAttitlerequiredallDaytimezonetodoListrepeatRuledescriptionhouseholdIdrequiredleadMinutesownerUserIdassigneeUserIdidempotencyKey+1 moreCreate list task
Use this when the user asks to create a shopping list, packing list, checklist, or Familia task with list items. If the same list task repeats across several days, weeks, or months, provide repeatRule and create one recurring list task instead of multiple one-time tasks. Do not use when editing an existing list attachment. Assigning to another household member queues a push notification; schedules can also queue reminders, and delivered notifications cannot be recalled.
dueAtitemsrequiredtitlerequiredallDaytimezonelistTitlerepeatRuledescriptionhouseholdIdrequiredleadMinutesownerUserIdassigneeUserId+2 moreList attachments
Use this when the user asks what photos, checklists, or list attachments are attached to an existing Familia task or plan. Use before editing an existing list attachment when the attachment id is unknown.
targetIdrequiredtimezonetargetTyperequiredAttach image
Use this when the user asks to attach a JPEG, PNG, or WebP image to an existing Familia task or plan. Provide either dataUrl or base64Data plus mimeType. Do not use for non-image files.
widthheightdataUrlfileNamemimeTypetargetIdrequiredtimezonebase64DatatargetTyperequiredreplaceExistingPhotoCreate list attachment
Use this when the user asks to add a new checklist, shopping list, packing list, or structured subtasks to an existing Familia task or plan. Do not use for editing an existing attachment.
itemsrequiredtitletargetIdrequiredtimezonetargetTyperequiredUpdate list attachment
Use this when the user asks to edit, add, remove, reorder, or mark items in an existing Familia checklist/list attachment. This replaces the existing list content; list attachments first if the attachment id is unknown.
itemsrequiredtitletimezoneattachmentIdrequiredDelete attachment
Use this only when the user explicitly asks to delete or remove an existing Familia photo, checklist, or list attachment. Do not use for hiding or summarizing attachments.
timezoneattachmentIdrequiredCreate plan
Use this when the user asks to create a Familia plan item for an event, trip, holiday, school, activity, care coverage, travel, chore block, or other scheduled family plan. If the same plan repeats across several days, weeks, or months, provide rrule and create one recurring plan instead of multiple one-time plans. If the user gives multiple dated or timed actions that clearly belong to the plan, such as flights, leaving for the airport, pickup, packing, check-in, or return travel, put the main event/trip in the plan and create each dated action as a relatedTasks entry instead of stuffing them all into notes. Do not use for standalone responsibility-style task reminders; use familia_create_task or familia_batch_write instead. Related tasks assigned to another household member can queue push notifications; schedules can trigger reminders, and delivered notifications cannot be recalled.
kindendAtnotesrruletitlerequiredallDaystartAtlocationtimezonehouseholdIdrequiredagreementIdsrelatedTasks+4 moreUpdate task
Use this when the user asks to rename, reschedule, reassign, complete, cancel, or otherwise edit an existing Familia task. When status is done, this completes the next actionable occurrence so recurring tasks continue. Do not use to create a new task. Updates may notify household members and reschedule reminders; delivered notifications cannot be recalled.
dueAttitlestatustimezonerepeatRuleagreementIdrequireddescriptionownerUserIdassigneeUserIdvisibleToHouseholdCancel task
Use this only when the user explicitly asks to cancel, archive, or hide an existing Familia task without permanently deleting the record. Do not use to mark a task done; use familia_update_task instead.
timezoneagreementIdrequiredPermanently delete task
Use this only when the user explicitly asks to permanently delete or hard delete an existing Familia task. This removes the record and related task schedules, occurrences, reminders, and attachments.
timezoneagreementIdrequiredUpdate plan
Use this when the user asks to rename, reschedule, move, update location, link tasks, change participants, or otherwise edit an existing Familia plan. Do not use to create a new plan. Updates can synchronize copies already imported by invited guests and queue notifications; delivered notifications cannot be recalled.
kindendAtnotestitleallDaystartAtlocationtimezoneplanItemIdrequiredagreementIdsparticipantUserIdsrequiresConfirmationDelete plan
Use this only when the user explicitly asks to delete, remove, or cancel an existing Familia plan item. Do not use to reschedule or complete a plan; use familia_update_plan instead. Cancelling a shared plan can update existing guest copies and queue cancellation notifications; delivered notifications cannot be recalled.
timezoneplanItemIdrequiredBatch write Familia items
Use this when the user explicitly asks to create or modify multiple Familia tasks, list tasks, plans, or task attachments in one request, or when one prompt contains multiple standalone dated actions that should become separate tasks. When the same task or plan repeats, use repeatRule/rrule on one operation instead of creating duplicate one-time operations. For a main event/trip plus clearly related dated actions, prefer one create_plan operation with relatedTasks. Internally this runs bounded individual write operations one by one; it does not create a backend transaction. Operations can queue assignment notifications and reminders; delivered notifications cannot be recalled.
timezoneoperationsrequiredidempotencyKeycontinueOnErrorFind consecutive free days
Use this when the user asks to find free days, open dates, vacation windows, long weekends, or consecutive days without hard Familia availability blockers. Do not use for listing tasks on one known date.
limittimezonestartDatebusyEndHourhorizonDayshouseholdIdbusyStartHourblockingPolicyconsecutiveDays90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx @reneturcios/famboard familia_list_householdsnpx @reneturcios/famboard familia_search_items '{"query":"dentist"}'npx @reneturcios/famboard familia_create_task '{"householdId":"hh-1","title":"Take bins out"}'npx @reneturcios/famboard --versionnpx -y @reneturcios/famboard mcp{ "mcpServers": { "famboard": { "command": "npx", "args": ["-y", "@reneturcios/famboard", "mcp"] } }}docker run -i ghcr.io/cloudcorprecords/famboarddocker run --rm ghcr.io/cloudcorprecords/famboard --versionnpm installnpm run buildnpm testnpm run dev