Servidor MCP de Familia

• Nombre en el registrocom.familiaplanner/familiaverificado en el registro MCP

El nombre en el registro está bajo familiaplanner.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

• Estadorespondecomprobado el 2026-10-21
• Herramientas25
• El servidor se llamafamilia
• Versión del servidor0.10.4
• Versión del protocolo2025-06-18

El 2026-10-21 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 261 ms.

• Aún no se ha juzgado si sus herramientas hacen el trabajo del producto.
• Comprobado 6 de los 7 días necesarios para juzgar su fiabilidad.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

• Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 6 hasta ahora
• Respondiómidiendo6 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
• Mediana de la primera respuesta197 ms
• Espacio en el contexto del agente≈ 10.351 tokenslas definiciones de todas sus herramientas (25), que el agente lleva en cada turno
• Definiciones de herramientasA · 99 de 100
• Resultados tipados25 de 25 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez

• Parámetros sin descripción: en 2 de 25

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

• familia_list_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.

• 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.

• familia_get_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.

• 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. Includes tasks, plans, Google/calendar events, and an overdue summary.

• 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. Includes tasks, plans, Google/calendar events, and an overdue summary.

• 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. Defaults to personal assigned items; use household scope only for family-wide wording. Never describe owner-only tasks…

• 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.

• 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.

• 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”. Calendar events are excluded.

• familia_search_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.

• familia_create_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…

• familia_create_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…

• familia_list_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.

• familia_attach_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.

• 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. Do not use for editing an existing attachment.

• 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. This replaces the existing list content; list attachments first if the attachment id is unknown.

• familia_delete_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.

• 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. If the same plan repeats across several days, weeks, or months…

• familia_update_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…

• 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. Do not use to mark a task done; use familia_update_task instead.

• familia_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.

• 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. Do not use to create a new plan. Updates can synchronize copies already imported by…

• familia_delete_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…

• 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…

• 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. Do not use for listing tasks on one known date.