Granola
win4r/MuseAI-Skills
Search and read Granola meeting notes and transcripts through Granola's OAuth-backed MCP server.
“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…”
Install Vexa MCP Setup
$ npx skills add Vexa-ai/vexa --skill vexa-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Vexa-ai/vexa vexa-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Vexa-ai/vexa.git skills-src && mkdir -p .claude/skills && cp -r skills-src/clients/claude-plugin/skills/setup .claude/skills/vexa-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vexa-setup" agent skill from https://github.com/Vexa-ai/vexa/tree/main/clients/claude-plugin/skills/setup into .claude/skills/vexa-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vexa-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Vexa-ai/vexa/tree/main/clients/claude-plugin/skills/setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Vexa-ai/vexa --skill vexa-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Vexa-ai/vexa vexa-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Vexa-ai/vexa.git skills-src && mkdir -p .agents/skills && cp -r skills-src/clients/claude-plugin/skills/setup .agents/skills/vexa-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vexa-setup" agent skill from https://github.com/Vexa-ai/vexa/tree/main/clients/claude-plugin/skills/setup into .agents/skills/vexa-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vexa-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Vexa-ai/vexa --skill vexa-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Vexa-ai/vexa vexa-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Vexa-ai/vexa.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/clients/claude-plugin/skills/setup .cursor/skills/vexa-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vexa-setup" agent skill from https://github.com/Vexa-ai/vexa/tree/main/clients/claude-plugin/skills/setup into .cursor/skills/vexa-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vexa-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Vexa-ai/vexa.git --path clients/claude-plugin/skills/setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Vexa-ai/vexa --skill vexa-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Vexa-ai/vexa vexa-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Vexa-ai/vexa.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/clients/claude-plugin/skills/setup .gemini/skills/vexa-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vexa-setup" agent skill from https://github.com/Vexa-ai/vexa/tree/main/clients/claude-plugin/skills/setup into .gemini/skills/vexa-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vexa-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Vexa-ai/vexa vexa-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Vexa-ai/vexa --skill vexa-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Vexa-ai/vexa.git skills-src && mkdir -p .github/skills && cp -r skills-src/clients/claude-plugin/skills/setup .github/skills/vexa-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vexa-setup" agent skill from https://github.com/Vexa-ai/vexa/tree/main/clients/claude-plugin/skills/setup into .github/skills/vexa-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vexa-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Vexa-ai/vexa --skill vexa-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Vexa-ai/vexa vexa-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Vexa-ai/vexa.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/clients/claude-plugin/skills/setup .opencode/skills/vexa-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vexa-setup" agent skill from https://github.com/Vexa-ai/vexa/tree/main/clients/claude-plugin/skills/setup into .opencode/skills/vexa-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vexa-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vexa-setup- GitHub stars
- 2.9k
- Token cost
- ~289 tokens
- SKILL.md length
- 133 words
- Files
- 2
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
- Calls make; reaches api.cloud.vexa.ai
About 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.”
Vexa MCP Setup is a skill in Vexa-ai/vexa (2.9k stars). Its SKILL.md is about 289 tokens, with 1 other file in the folder. Licence: Apache-2.0.
What it can do on your machine
Read from SKILL.md and the folder at commit 6ee2a3a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
make
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
api.cloud.vexa.ai
Also links to:
vexa.aidocs.vexa.ai
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vexa MCP Setup loads about 289 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 133 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Vexa-ai/vexa at commit 6ee2a3a, republished under its Apache-2.0 licence (© Vexa-ai). 133 words, ~289 tokens.
Download SKILL.mdSave it as
.claude/skills/vexa-setup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- 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 allin the Vexa repo prints a key when the stack is up; set the URL to your gateway's/mcp(Docker Compose defaulthttp://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).
© Vexa-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in clients/claude-plugin/skills/setup of Vexa-ai/vexa.
- SKILL.md
- README.md
Open the folder on GitHubat commit 6ee2a3a
Compare with similar skills
Vexa MCP Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vexa MCP Setup this skillVexa-ai/vexa | 2.9k | — | ~289 | Automated safety check: Pass | Apache-2.0 | |
| Granolawin4r/MuseAI-Skills | 336 | 1 repos | ~805 | Automated safety check: Pass | None | |
| API Mirrorcyanheads/pubmed-mcp-server | 156 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| Unbrowseunbrowse-ai/unbrowse | 780 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Gemini SkillWJZ-P/gemini-skill | 832 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Turnstile Testingjumodada/Drissionpage-MCP-Server | 487 | — | ~1.7k | Automated safety check: Pass | Custom licence |
Similar skills
API Mirror
cyanheads/pubmed-mcp-server
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror).
Unbrowse
unbrowse-ai/unbrowse
Search and call websites through Unbrowse's hosted API or remote MCP, reuse indexed site tools, read pages, and learn missing routes in its cloud browser.
Gemini Skill
WJZ-P/gemini-skill
通过 Gemini 官网（gemini.google.com）执行生图、对话等操作。用户提到"生图/画图/绘图/nano banana/nanobanana/生成图片"等关键词时触发。操作方式分三级优先级：首选 MCP 工具 → 次选 Skill 脚本 → 最次连接 Skill 浏览器手动操作（需用户授权）。禁止自行启动外部浏览器访问 Gemini。
Turnstile Testing
jumodada/Drissionpage-MCP-Server
A skill your agent uses when testing an authorized Cloudflare Turnstile integration or operating an authorized production challenge with drissionpage-mcp.
Triage Security Advisories
activepieces/activepieces
Triage the GitHub privately-reported vulnerability backlog for Activepieces — pull repository security advisories from the Security tab, scope-check against SECURITY.md, deeply validate each…
More from Vexa-ai/vexa
Vexa Scheduler Routines
Vexa-ai/vexa
Writes durable recurring or future-dated jobs for a Vexa workspace as routine files, replacing OS cron, timers and session-only reminders.
Vexa Meetings
Vexa-ai/vexa
Sends a Vexa bot into a meeting, follows the live transcript and writes meeting notes with speakers, decisions and action items into Obsidian, Notion or Markdown.
Related
Works with
Categories
Questions about Vexa MCP Setup
How do I install Vexa MCP Setup in Claude Code?
Run `npx skills add Vexa-ai/vexa --skill vexa-setup -a claude-code`. Or copy the skill folder (clients/claude-plugin/skills/setup in Vexa-ai/vexa) into .claude/skills/vexa-setup in your project. Claude Code loads it when a task matches its description.
How do I install Vexa MCP Setup in Codex?
Run `npx skills add Vexa-ai/vexa --skill vexa-setup -a codex`. Or copy the skill folder (clients/claude-plugin/skills/setup in Vexa-ai/vexa) into .agents/skills/vexa-setup in your project. Codex loads it when a task matches its description.
Can I use Vexa MCP Setup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Vexa-ai/vexa --skill vexa-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vexa-setup, .gemini/skills/vexa-setup, .github/skills/vexa-setup and .opencode/skills/vexa-setup in your project.
What does Vexa MCP Setup need to run?
Going by SKILL.md and its folder, Vexa MCP Setup needs the command-line tools its instructions call (make).
Does Vexa MCP Setup access the network?
SKILL.md names 3 domains. In commands or code: api.cloud.vexa.ai; the agent is likely to contact it when it follows the instructions. As links in the text: vexa.ai and docs.vexa.ai. This is read from the text; nothing was executed.
Is Vexa MCP Setup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vexa MCP Setup use?
Vexa MCP Setup is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vexa MCP Setup use?
About 289 tokens (SKILL.md is roughly 1.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vexa MCP Setup?
Skills that share tags, products or a category with Vexa MCP Setup: Granola (win4r/MuseAI-Skills, 336 stars), API Mirror (cyanheads/pubmed-mcp-server, 156 stars), Unbrowse (unbrowse-ai/unbrowse, 780 stars) and Gemini Skill (WJZ-P/gemini-skill, 832 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vexa MCP Setup?
Vexa-ai (a GitHub organization) maintains it in Vexa-ai/vexa, which has 2,864 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 9, 2026.
Source: Vexa-ai/vexa on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.