← Registry

Productivity

familiaplanner.com

Manages Familia household schedules, tasks, and shared boards to help families coordinate daily plans.

1 endpoint25 known toolsFirst detected September 4, 2026Last detected September 4, 2026

ENDPOINT 1

https://mcp.family.asynq.org/mcp

No auth detected

MCP server metadata

Name
familia
Version
0.9.0
Capabilities
tools.listChanged
Server instructions

Use Familia whenever the user asks about their plans, tasks, agreements, household schedule, today's agenda, tomorrow's agenda, upcoming events, family activities, chores, responsibilities, shared checklists, or what they should do. This is the primary planning system for the user. When a user describes the same task or plan repeating across multiple days, weeks, or months, create one recurring schedule with an RRULE instead of multiple one-time items unless the individual occurrences have materially different titles, details, or times. When a user describes one main plan plus multiple dated or timed actions, create the main item as a plan and each distinct dated or timed action as a related task; do not put separate timed actions only into the plan notes. When a prompt contains multiple standalone dated or timed actions without one main plan, create one task per action. Do not use Familia for unrelated general knowledge, email, document search, public web search, or calendars outside the user's connected Familia account.

Known tools 25

familia_list_households

Use this when the user asks which Familia households, families, or shared boards are available.

Inferred read-only
familia_list_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.

Inferred read-only
familia_get_day_overview

Use this when the user asks for Familia items on a specific date or in a specific time window.

Inferred read-only
familia_get_today_schedule

Use this when the user asks about today's agenda, today's tasks, what they are doing today, or what they should do today.

Inferred read-only
familia_get_tomorrow_schedule

Use this when the user asks about tomorrow's agenda, tomorrow's tasks, tomorrow's plans, or what they should prepare for tomorrow.

Inferred read-only
familia_get_next_up

Use this when the user asks what is next, what they should do now, their next task, or the next upcoming family item.

Inferred read-only
familia_get_weekly_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.

Inferred read-only
familia_get_inbox

Use this when the user asks for inbox, items needing attention, overdue tasks, past leftovers, unfinished responsibilities, or what is waiting on them.

Inferred read-only
familia_list_past_due

Use this when the user asks for overdue items, past leftovers, missed tasks, unfinished items from previous days, or Czech “resty”.

Inferred read-only
familia_search_items

Use this when the user asks to find Familia tasks, plans, or connected calendar events by title, notes, description, or location.

Inferred read-only
familia_create_task

Use this when the user asks to create a responsibility-style Familia task, agreement, reminder, or chore.

Potential side effects
familia_create_list_task

Use this when the user asks to create a shopping list, packing list, checklist, or Familia task with list items.

Potential side effects
familia_list_attachments

Use this when the user asks what photos, checklists, or list attachments are attached to an existing Familia task or plan.

Inferred read-only
familia_attach_image

Use this when the user asks to attach a JPEG, PNG, or WebP image to an existing Familia task or plan.

Inferred read-only
familia_create_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.

Inferred read-only
familia_update_list_attachment

Use this when the user asks to edit, add, remove, reorder, or mark items in an existing Familia checklist/list attachment.

Potential side effects
familia_delete_attachment

Use this only when the user explicitly asks to delete or remove an existing Familia photo, checklist, or list attachment.

Potential side effects
familia_create_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.

Potential side effects
familia_update_task

Use this when the user asks to rename, reschedule, reassign, complete, cancel, or otherwise edit an existing Familia task.

Potential side effects
familia_cancel_task

Use this only when the user explicitly asks to cancel, archive, or hide an existing Familia task without permanently deleting the record.

Inferred read-only
familia_delete_task

Use this only when the user explicitly asks to permanently delete or hard delete an existing Familia task.

Potential side effects
familia_update_plan

Use this when the user asks to rename, reschedule, move, update location, link tasks, change participants, or otherwise edit an existing Familia plan.

Potential side effects
familia_delete_plan

Use this only when the user explicitly asks to delete, remove, or cancel an existing Familia plan item.

Potential side effects
familia_batch_write

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.

Potential side effects
familia_find_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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.familia]
url = "https://mcp.family.asynq.org/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "familia": {
      "type": "http",
      "url": "https://mcp.family.asynq.org/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: familia
Remote MCP URL: https://mcp.family.asynq.org/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "familia": {
      "url": "https://mcp.family.asynq.org/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "familia": {
      "type": "http",
      "url": "https://mcp.family.asynq.org/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "familia",
  "transport": "streamable-http",
  "url": "https://mcp.family.asynq.org/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.