菜单
Interactive wizard to set up MCP server credentials in your shell environment (~/.zshenv, ~/.bashrc, etc.). Activates when the user needs to configure API keys, tokens, or environment variables for MCP servers, or after adding new MCP integrations that require authentication.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/terrazul-ai/tz-packages --skill setup-mcp命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
Creates well-structured Claude Skills with proper YAML frontmatter, clear instructions, and supporting files. Activates when the user wants to create a new skill, add capabilities to their AI assistant, encode team preferences, or structure any reusable instruction set. Covers the full lifecycle from intent capture through writing, testing, and refinement.
Shows all available skills, platform support, common workflows, and troubleshooting for the @terrazul/assistant-creator package. Activates when the user asks for help, wants to know what's available, or needs guidance on using the package.
Searches mcp.so marketplace for MCP servers and configures them for Claude, Codex, or Gemini. Use when user wants to add external tool integrations, find MCP servers, or configure model context protocol.
正在显示 SKILL.md
| name | setup-mcp |
| description | Interactive wizard to set up MCP server credentials in your shell environment (~/.zshenv, ~/.bashrc, etc.). Activates when the user needs to configure API keys, tokens, or environment variables for MCP servers, or after adding new MCP integrations that require authentication. |
Guides the user through setting up environment variables for MCP server authentication. Since Terrazul passes MCP configuration via CLI flags, credentials must be persisted in shell environment files.
This is an interactive setup flow. Guide the user through ONE credential at a time using AskUserQuestion to confirm progress.
Determine the user's shell and appropriate config file:
echo $SHELL
| Shell | Recommended File | Alternative |
|---|---|---|
| zsh | ~/.zshenv | ~/.zshrc |
| bash | ~/.bashrc | ~/.bash_profile |
Why ~/.zshenv? Environment variables in .zshenv are loaded for all shell sessions (interactive and non-interactive), ensuring MCP servers always have access to credentials.
Ask the user which file they want to use if multiple options exist. Default to ~/.zshenv for zsh users.
Read the project's MCP configuration to find which environment variables are needed. Check:
.claude/settings.local.json - Local project MCP configtemplates/claude/mcp_servers.json.hbs - Package MCP template.gemini/settings.json - Gemini MCP configLook for ${VAR_NAME} patterns. Present a summary:
echo $VAR_NAME)For each missing credential, provide service-specific instructions from reference.md. Ask the user to obtain the credential and provide it.
For each credential, append to the chosen profile file:
# MCP Server: [Server Name]
export VAR_NAME="value_here"
Group related variables with comments. Use double quotes around values. Add blank lines between different server configurations.
Ask the user to source the profile:
source ~/.zshenv # or ~/.bashrc
Verify variables are set:
echo $VAR_NAME
Run the test command for each service (see reference.md for test commands).
Provide a summary:
grep "VAR_NAME" ~/.zshenv
If using bash but .bashrc isn't loaded, try .bash_profile instead.
Restart Claude Code after setting up credentials. The terminal session used by Claude must have the updated environment.