Skill
meetings
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…
Automation
Skill
/setup
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.
Install
$ npx -y skills add Vexa-ai/vexa --skill setup --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/setup
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
setup.SKILL.mdname: vexa-setup description: 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.
Vexa setup
The plugin needs one value: **Vexa API key** (`vexa_api_key`), and optionally the **MCP URL** (`vexa_mcp_url`).
- **Hosted**: sign in at https://vexa.ai/account and create a key. URL stays `https://api.cloud.vexa.ai/mcp`.
- **Self-hosted**: `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/deployment
- **The door**: https://vexa.ai/connect mints a key and registers the server for the user's agent without this plugin; either path works.
Check 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).
Ships withvexa
Open-source meeting bots and real-time transcription — cloud or fully self-hosted.
Get the whole plugin
Stats
2,914
Stars
523
Forks
Active
Maintenance
Python
Language
Apache-2.0
License
15h ago
Last commit
1y ago
Created
3h ago
Added
Other skills on vexa.
Skill
scheduling
Set up recurring or scheduled work — anything the user wants run on a schedule, repeatedly, or at a future time ("every morning",…