archflow-setup-mcplisted

> Arguments are the text after the skill name. # /archflow-setup-mcp — MCP Server Setup Helper Argument (`the text the user wrote after the skill name`): optional tool name (e.g. `jira`, `notion`). Empty → list the registry. Configure external tool MCP servers for use with Copilot. ## Usage ``` /archflow-setup-mcp → List available MCPs from registry /archflow-setup-mcp [tool-name] → Configure a specific MCP server ``` ## Registry The curated MCP registry is stored in `.github/archflow/skills/archflow/mcp-registry.yaml`. Read that file to look up tool details. Edit it to add or update MCP servers. ## Invocation When the user runs `/archflow-setup-mcp`, follow this flow exactly. --- ## Flow ### Step 1: Check If Already Configured ```bash claude mcp list ``` Parse the output. If the requested tool is already listed: > "[Tool] MCP is already configured. No action needed." If not found, proceed to Step 2. **Special case — shared MCPs**: Some tools share a server (e.g., Jira and Confluence both use Atlassian Rovo). If the registry entry has `shared_with`, check if that sibling is already configured. If so: > "[Tool] is available through the already-configured [sibling] MCP (same server). No additional setup needed." ### Step 2: Lookup in Registry Read `.github/archflow/skills/archflow/mcp-registry.yaml` and search for the tool name (case-insensitive). If found, show: > "[Tool] MCP uses [command/url] via [transport] transport." > Purpose: [purpose] If