Work with the user's meetings through the Vexa MCP tools — send a bot to a call, follow the transcript while it runs, and write meetings into their notes (Obsidian, Notion, plain markdown) with speakers and action items. Use whenever the user mentions a meeting, a call, a transcript, meeting notes, or asks what was said.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
The vexa MCP server is connected. Start with whats_waiting — it says what the user's Vexa needs right now.
parse_meeting_link(meeting_url) → platform + native_meeting_id.request_meeting_bot(meeting_url). A human in the call must admit the bot; expect a delay between requested and active.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.stop_bot(platform, native_meeting_id) when done.Every tool returns platform + native_meeting_id; feed one tool's output straight into the next.
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.search_transcripts returns ranked snippets of what was said, not whole transcripts. Use it for "what did we decide about X", then open the meeting for context.
annotate_meeting attaches a title and metadata (a CRM id, a ticket, tags). Anything you put there is findable later with list_meetings(metadata_filter=...). If you learn something durable about a meeting, write it back.
speak_in_meeting unless the user asked for that exact thing to be said. It is audible to everyone present and irreversible.meetings_failed-style counters as reliability; a meeting ends in many states that are not errors.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Set up recurring or scheduled work — anything the user wants run on a schedule, repeatedly, or at a future time ("every morning", "each weekday at 9am", "daily digest", "weekly report", "remind me", "run this on a cron"). Teaches how to author a durable Vexa Scheduler routine that survives restarts. Use this instead of any OS cron job, system timer, or session-only reminder.
日本語の概要は準備中です。原文の説明を表示しています。
Set up or fix the Vexa MCP connection for this plugin — where the API key comes from, hosted vs self-hosted URL, and how to check the connection. Use when the vexa server is missing, returns 401, or the user asks how to connect Vexa.
日本語の概要は準備中です。原文の説明を表示しています。