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.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
The plugin needs one value: Vexa API key (vexa_api_key), and optionally the MCP URL (vexa_mcp_url).
https://api.cloud.vexa.ai/mcp.make all in the Vexa repo prints a key when the stack is up; set the URL to your gateway's /mcp (Docker Compose default http://localhost:18056/mcp). Docs: https://docs.vexa.ai/deploymentCheck the connection by calling whats_waiting. A 401 means the key is missing or wrong; a connection error usually means the URL points at a stack that is not up.
Do not paste keys into chat or files. Tell the user to enter the key in the plugin's settings (it is stored in the OS keychain).
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。