vexa-meetings

# Vexa meetings The `vexa` MCP server is connected. Start with `whats_waiting` — it says what the user's Vexa needs right now. ## Send a bot to a call 1. `parse_meeting_link(meeting_url)` → platform + native_meeting_id. 2. `request_meeting_bot(meeting_url)`. A human in the call must admit the bot; expect a delay between `requested` and `active`. 3. `get_meeting_transcript(platform, native_meeting_id)` while the meeting runs. Pass `since_index` to read only what is new. A meeting that is `active` with zero segments usually means the bot is not admitted yet or nobody has spoken. 4. `stop_bot(platform, native_meeting_id)` when done. Every tool returns `platform` + `native_meeting_id`; feed one tool's output straight into the next. ## Write a meeting into the user's notes When asked to sync, log, or file a meeting: - `list_meetings` (filters: status, platform, metadata) to find it; `get_meeting_transcript` for the segments; `get_meeting_participants` is not a tool — participants come from the segments' speaker names. - Write one note per meeting, dated, in the user's existing format if there is one (look at a recent note first). Include: title, date, participants (from speaker labels), a short summary, decisions, action items with owners, and the transcript or a link to it. Keep speaker labels as they are — do not guess names the transcript does not carry. - Ask before writing outside the folder the user named. ## Search across meetings `search_transcripts` returns ranke...