minutes-x1-send-meeting

1# /minutes-x1-send-meeting
2 
3Send one of the user's own meetings to their X1 household for review. Minutes
4supplies the meeting's outcomes. X1 decides who the sender is, which
5household it goes to, and what gets matched, and the user approves the send
6in X1. The meeting lands in the user's own review queue. Nothing reaches the
7household record until they confirm each item, and no professional sees it.
8 
9## Required connections
10 
11This workflow needs both the local Minutes MCP and the official X1 MCP. Call
12X1 `get_user_capabilities` first. If `submit_my_meeting` or
13`request_human_confirmation` isn't mounted, stop: X1 hasn't turned meeting
14sends on for this account yet. Don't substitute another X1 write tool, invent
15an endpoint, or save the meeting somewhere else in X1.
16 
17Before using `dueStatement` or `detail`, inspect the mounted
18`submit_my_meeting` input schema from MCP `tools/list` and check its
19`meeting.actionItems` item properties. A mounted tool name alone does not
20prove support for a field. If that schema is unavailable, an available X1
21`get_user_capabilities` action proposal contract for `submit_my_meeting`
22may supply the argument schema; capability discovery never grants approval.
23If a needed field is absent or neither discovery path supplies its schema,
24stop before requesting a send and ask: “Can you update or reconnect X1 so
25it accepts this meeting's original timing or detail?” Do not silently drop
26conditional timing or rewrite a task to work around an older backend.
27…