ComingUp Today!
Keep your household on the same page with ComingUp Today.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Search Public Product Content: Use this when you need published ComingUp product docs, integration or MCP setup, troubleshooting, FAQs, or support guidance.
- Get Public Product Content: Use this when you need the complete published public content for one search result's stable slug and content kind.
- Get User Context: Use this first when troubleshooting sign-in, permissions, plan access, household availability, feature availability, or calendar connection status—not household content.
What data it sees
Do you need an account
No: the server works without sign-in
Keep your household on the same page with ComingUp Today. Built for families and caregivers managing busy schedules, ComingUp brings calendars, lists, notes, contacts, and recipes together.
Connect your AI assistant to see what’s coming up, add groceries, find important household information, save recipes, and create or update ComingUp events—all through conversation.
Connect securely with OAuth and choose the permissions you grant. Connected external calendars remain read-only.
Server tool list (28)
Raw names from tools/list. Only developers need these.
| search_public_product_content | Use this when you need published ComingUp product docs, integration or MCP setup, troubleshooting, FAQs, or support guidance. |
| get_public_product_content | Use this when you need the complete published public content for one search result's stable slug and content kind. |
| get_user_context | Use this first when troubleshooting sign-in, permissions, plan access, household availability, feature availability, or calendar connection status—not household content. |
| get_my_support_reports | Use this when the signed-in user wants to review their own recent ComingUp support reports, ticket status, public support responses, or privacy-preserving issue-pattern and known-incident status. |
| get_schedule | Use this when you need household events in a date range; very dense ranges return explicit truncation guidance and can be retried with a smaller range. |
| get_lists | Use this to locate a list and get the listRef and current version required by list-write tools; call get_list only when item details or listItemRef values are needed. |
| get_list | Use this when existing item details or listItemRef values are needed; do not call it merely to append items. |
| find_events | Use this when you need to search events by text, person, contact, or date; narrow a truncated result. |
| get_event | Use this when you need one event occurrence; unusually large details are explicitly shortened, and provider events stay read-only. |
| find_notes | Use this when you need to search private notes; use get_note with its returned note reference for full content. |
| get_note | Use this when you need one private note's full content after obtaining its opaque note reference. |
| get_household | Use this when you need the active household and people; large results disclose truncation and can be narrowed by name. |
| find_contacts | Use this when you need to search reusable contacts before creating one or attaching a returned reference. |
| find_recipes | Use this when you need to search private recipes; narrow a truncated result, then use get_recipe for details. |
| get_recipe | Use this when you need one private recipe; unusually large fields or collections are explicitly shortened. |
| submit_support_report | Use this after reasonable troubleshooting when the signed-in user asks to privately submit a possible bug, connection problem, unexpected behavior, data problem, feature request, or other support issue to ComingUp. It creates an internal ComingUp support ticket and automatically attaches a strictly sanitized diagnostic snapshot; it does not send email, create a public issue, or contact a third party. |
| create_list | Use this when you need to create a shopping, to-do, or miscellaneous list; use focused list-write tools for later changes. |
| add_list_items | Use this when you need to append one or more items in one ordered batch; get listRef and expectedVersion from get_lists, and do not call get_list first. |
| change_list | Use this when you need the legacy-compatible path to rename a list or edit/check an existing item; use add_list_items for all additions and remove_list_item for removals. |
| remove_list_item | Use this when you need to permanently remove an item or clear completed items; it never deletes a list. |
| create_recipe | Use this when you need to save a private structured recipe; use update_recipe with a current version for changes. |
| update_recipe | Use this when you need to change a private recipe with its returned reference and current version; it cannot delete or publish. |
| create_contact | Use this when you need to save a reusable contact after find_contacts confirms it is not already available. |
| update_contact | Use this to update an existing reusable household contact after find_contacts returns its current version. It can change contact details but cannot delete the contact. |
| create_note | Use this when you need to create a private Markdown note; use update_note with a current version for changes. |
| update_note | Use this when you need to change a private note with its returned reference and current version; it cannot delete notes. |
| create_event | Use this when you need to create a ComingUp-owned event; it cannot create or write provider calendar events. |
| update_event | Use this when you need to change a ComingUp-owned event or occurrence with its current version; it cannot delete or write provider events. |