Crush Configuration
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
Add, authenticate, list, and remove MCP (Model Context Protocol) servers — connect any external tool or service that publishes an MCP endpoint to the assistant
$ npx skills add vellum-ai/vellum-assistant --skill mcp-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vellum-ai/vellum-assistant mcp-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/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/mcp-setup .claude/skills/mcp-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 "mcp-setup" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/mcp-setup into .claude/skills/mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-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/vellum-ai/vellum-assistant/tree/main/skills/mcp-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 vellum-ai/vellum-assistant --skill mcp-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vellum-ai/vellum-assistant mcp-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/mcp-setup .agents/skills/mcp-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 "mcp-setup" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/mcp-setup into .agents/skills/mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-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 vellum-ai/vellum-assistant --skill mcp-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vellum-ai/vellum-assistant mcp-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/mcp-setup .cursor/skills/mcp-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 "mcp-setup" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/mcp-setup into .cursor/skills/mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-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/vellum-ai/vellum-assistant.git --path skills/mcp-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 vellum-ai/vellum-assistant --skill mcp-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vellum-ai/vellum-assistant mcp-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/mcp-setup .gemini/skills/mcp-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 "mcp-setup" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/mcp-setup into .gemini/skills/mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-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 vellum-ai/vellum-assistant mcp-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 vellum-ai/vellum-assistant --skill mcp-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/mcp-setup .github/skills/mcp-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 "mcp-setup" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/mcp-setup into .github/skills/mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-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 vellum-ai/vellum-assistant --skill mcp-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 vellum-ai/vellum-assistant mcp-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/mcp-setup .opencode/skills/mcp-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 "mcp-setup" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/mcp-setup into .opencode/skills/mcp-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcp-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.
mcp-setupAdd, authenticate, list, and remove MCP (Model Context Protocol) servers — connect any external tool or service that publishes an MCP endpoint to the assistant
MCP Setup is an agent skill from vellum-ai/vellum-assistant. Add, authenticate, list, and remove MCP (Model Context Protocol) servers — connect any external tool or service that publishes an MCP endpoint to the assistant
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Works on both the Vellum desktop app (local daemon) and the Vellum web app (platform-hosted). Auth flow differs by environment.
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol and Bash. The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 33cc983. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
mcp.context7.commcp.linear.appmcp.figma.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Works on both the Vellum desktop app (local daemon) and the Vellum web app (platform-hosted). Auth flow differs by environment.
From compatibility in the SKILL.md frontmatter.
MCP Setup loads about 1.6k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 707 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.
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.
The full file from vellum-ai/vellum-assistant at commit 33cc983, republished under its MIT licence (© vellum-ai). 707 words, ~1,556 tokens.
.claude/skills/mcp-setup/SKILL.md (or your agent's skills folder).Configure MCP servers to give the assistant access to any external tool or service that publishes an MCP endpoint.
DO NOT run exploratory commands. Do not check available CLI commands, search for bun/npx/node, or investigate transport types. Follow the steps below exactly and stop when done. (Looking up a service's MCP endpoint URL in its own documentation is allowed when the service is not in the recipe table, per Step 3.)
USE THIS SKILL WHEN:
assistant mcp auth <name>Many services have built-in OAuth integrations that are simpler and more reliable than MCP. Before setting up MCP, check whether the service already has a native OAuth provider:
assistant oauth providers listIf the service appears in that list, connect it natively instead of using MCP:
assistant oauth connect <provider>Only use MCP when:
assistant oauth providers listBefore doing anything else, determine which environment you are in.
Try host_bash:
echo "desktop ok"host_bash for all commands, including auth (opens a local browser).bash for all commands, including auth (the platform handles the browser redirect).Both environments fully support MCP. The only difference is which tool runs the commands.
Check this table before doing anything else. If the service is listed, run the command shown and do nothing else — no exploration, no checking available commands, no looking up documentation.
| Service | Command | After? |
|---|---|---|
| Context7 (docs) | assistant mcp add context7 -t streamable-http -u https://mcp.context7.com/mcp -r low | Done — no auth needed |
| Linear | assistant mcp add linear -t streamable-http -u https://mcp.linear.app/mcp | Run assistant mcp auth linear |
| Figma | assistant mcp add figma -t streamable-http -u https://mcp.figma.com/mcp | Run assistant mcp auth figma |
If the service is not in this table, go to Step 3.
Find the MCP endpoint URL in the service's documentation, then run:
assistant mcp add <name> -t streamable-http -u <url>Then run assistant mcp list. If it shows ! Needs authentication, run assistant mcp auth <name>.
host_bash (opens the local browser).bash (the platform handles the browser redirect).Run list, add, remove, and reload via bash on both environments. Run auth via host_bash on desktop, or via bash on the web app.
assistant mcp list
assistant mcp list --json # machine-readable outputShows each server's connection status, transport, and URL/command. Status indicators:
✓ Connected✗ Error! Needs authenticationassistant mcp add <name> -t <transport> -u <url>Transport types:
streamable-http — most modern remote servers (use this by default)sse — legacy remote serversstdio — local process: use -c <command> and -a <args...> instead of -uExamples:
assistant mcp add linear -t streamable-http -u https://mcp.linear.app/mcp
assistant mcp add context7 -t streamable-http -u https://mcp.context7.com/mcp
assistant mcp add local-db -t stdio -c npx -a -y @my/mcp-serverassistant mcp auth <name>host_bash (opens the user's local browser for OAuth login).bash (the platform handles the browser redirect and saves tokens).Tokens are saved automatically. Use when:
assistant mcp list shows ! Needs authenticationassistant mcp remove <name>Removes config and cleans up stored OAuth credentials.
assistant mcp reloadManually signals the assistant to reconnect all MCP servers from disk. Normally not needed — the assistant detects changes automatically after add, remove, and auth. Use this only if a server's tools aren't appearing after ~10 seconds.
mcp add covers the common cases. For stdio environment variables, edit $VELLUM_WORKSPACE_DIR/mcp.json under mcpServers.<name>.env. Auth headers for remote servers go through assistant mcp add -H or the settings UI, not mcp.json.
Match the completion condition to the task:
assistant mcp list with status ✓ Connected and the user confirms its tools are available in the conversation.assistant mcp remove <name> succeeds and the server no longer appears in assistant mcp list.© vellum-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/mcp-setup of vellum-ai/vellum-assistant.
Open the folder on GitHubat commit 33cc983
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 |
|---|---|---|---|---|---|---|
| MCP Setup this skillvellum-ai/vellum-assistant | 1.4k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence | |
| Record Demoapify/mcpc | 1k | — | ~3.3k | Automated safety check: Notes | Apache-2.0 | |
| Releasejgravelle/jcodemunch-mcp | 2.7k | — | ~6.5k | Automated safety check: Pass | Custom licence | |
| Mcpcapify/mcpc | 1k | — | ~3.6k | Automated safety check: Pass | Apache-2.0 | |
| Tool Selectiondatabricks-solutions/ai-dev-kit | 1.9k | — | ~519 | Automated safety check: Pass | Custom licence |
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
apify/mcpc
Record or regenerate the mcpc demo GIFs (the README hero docs/images/mcpc-demo.gif and the focused tapes in docs/vhs/) with VHS.
jgravelle/jcodemunch-mcp
Publishing a jMunch release (jcodemunch-mcp, jdocmunch-mcp, jdatamunch-mcp, jragmunch-cli), reviewing/merging/closing PRs, and responding to the community.
apify/mcpc
Use the mcpc CLI to work with MCP (Model Context Protocol) servers from the shell - connect to a server as a persistent session, then list and call tools, read resources, get prompts, and run async…
databricks-solutions/ai-dev-kit
Evaluates whether the agent selected appropriate MCP tools instead of shell workarounds.
nikolai-vysotskyi/trace-mcp
Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash.
vellum-ai/vellum-assistant
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity.
vellum-ai/vellum-assistant
Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration
vellum-ai/vellum-assistant
Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity
vellum-ai/vellum-assistant
Ingest a large dataset into memory as a skimmed map. An agent skill from vellum-ai/vellum-assistant.
vellum-ai/vellum-assistant
A skill your agent uses when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.
vellum-ai/vellum-assistant
Connect a Slack app to the Vellum Assistant via Socket Mode.
Works with
Categories
Add, authenticate, list, and remove MCP (Model Context Protocol) servers — connect any external tool or service that publishes an MCP endpoint to the assistant. MCP Setup is an agent skill from vellum-ai/vellum-assistant.
MCP Setup fits situations like: tasks that involve MCP servers.
Run `npx skills add vellum-ai/vellum-assistant --skill mcp-setup -a claude-code`. Or copy the skill folder (skills/mcp-setup in vellum-ai/vellum-assistant) into .claude/skills/mcp-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add vellum-ai/vellum-assistant --skill mcp-setup -a codex`. Or copy the skill folder (skills/mcp-setup in vellum-ai/vellum-assistant) into .agents/skills/mcp-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vellum-ai/vellum-assistant --skill mcp-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/mcp-setup, .gemini/skills/mcp-setup, .github/skills/mcp-setup and .opencode/skills/mcp-setup in your project.
SKILL.md names no scripts, command-line tools or credentials: MCP Setup is instructions for the agent only. Our summary lists: Node.js. Compatibility (from SKILL.md): Works on both the Vellum desktop app (local daemon) and the Vellum web app (platform-hosted). Auth flow differs by environment..
SKILL.md names 3 domains. In commands or code: mcp.context7.com, mcp.linear.app and mcp.figma.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
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.
MCP Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with MCP Setup: Crush Configuration (charmbracelet/crush, 29k stars), Record Demo (apify/mcpc, 1k stars), Release (jgravelle/jcodemunch-mcp, 2.7k stars) and Mcpc (apify/mcpc, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,408 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.
Source: vellum-ai/vellum-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.