claude.
Recommended: org-wide connector
Set up a custom connector at claude.ai/customize/connectors → Add custom connector:

Alternative: individual connector (OAuth)
Same steps as above, but paste justhttps://api.getwhys.io/mcp with no token — you’ll be sent to GetWhys to sign in and authorize with your own account.
Claude Code CLI
Using your GetWhys user authentication:Recommended: Installing the GetWhys skill for your whole Claude.ai org
Without the skill, Claude may not consistently know when to reach for GetWhys during a conversation. The skill gives Claude clear instructions for when to call GetWhys tools, what workflow to follow, and how to apply results — which makes GetWhys meaningfully more reliable in day-to-day use. Install it alongside the MCP connector for every org. The skill is a companion to the MCP server, not a replacement — it won’t do anything without the MCP connected.- Download the skill.
.../releases/download/vX.Y.Z/validate-gtm-output.zip. You do not need to unzip it — upload the .zip as-is.
- One-time org setup (first install only). Log in to claude.ai as an org admin → Organization Settings → Skills → enable both Skills and Code execution & file creation.
The GetWhys skill doesn’t execute code or create files itself — it only guides Claude in calling GetWhys MCP tools. Code execution & file creation is a platform-level prerequisite for Claude’s Skills feature generally, not something this specific skill uses.
- Add the skill. Still under Organization Settings → Skills, find Organization skills → + Add → select the
validate-gtm-output.zipyou downloaded.
Verify
Ask Claude the verify prompt: “Who am I in GetWhys?”Next: Claude Tag in Slack
If you also want GetWhys inside Anthropic’s@Claude in Slack, that is a separate setup — see Claude Tag. That is not the GetWhys Slack bot.