> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getwhys.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Tag (Claude in Slack)

> Connect GetWhys to @Claude in Slack with Access bundles, credentials, and the GetWhys skills plugin.

`@Claude` in Slack does **not** inherit anything from [Claude.ai setup](/integrations/mcp-claude) — no MCP connection, no skill. It's a separate surface with its own configuration, even if you've already connected GetWhys in Claude.ai.

<Info>
  Claude Tag is **not** the [GetWhys Slack bot](/integrations/slack). The Slack bot is a separate GetWhys integration that answers `@GetWhys` mentions. Claude Tag brings GetWhys into Anthropic's `@Claude` in Slack via MCP.
</Info>

Complete the shared steps in [MCP Setup](/integrations/mcp-setup) first, and [generate an Organization MCP API Token](/integrations/mcp-setup#generate-an-organization-mcp-api-token) with a label like `claude-tag`.

There are two variants. Anthropic is retiring the older one on **August 3, 2026** — set up new integrations on Claude Tag.

## Claude Tag (current, recommended)

A Claude org Owner/Admin configures this at [claude.ai/admin-settings/claude-tag](https://claude.ai/admin-settings/claude-tag) → **Slack** tab:

1. Pick a scope — the whole org, a single workspace, or a single channel.
2. Create an **Access bundle** (`+` next to *Access bundles* → *Create new bundle*) and name it (e.g. `getwhys`).
3. On the bundle's **Credentials** tab, add the GetWhys MCP connection: credential type **Bearer**, value = your Organization MCP API Token, server URL `api.getwhys.io`, path prefix `/mcp`.
4. Add the GetWhys skill. For Claude Tag this is **not** the `.zip` used in [Claude.ai](/integrations/mcp-claude) — Tag loads plugins, so upload the plugin package instead:
   * Download `getwhys-skills.zip` from the agent-skills releases page:

```text theme={null}
https://github.com/GetWhys-Engineering/agent-skills/releases/latest/download/getwhys-skills.zip
```

* In claude.ai admin settings: **Plugins → Upload plugin → Upload to a new marketplace** → name it (e.g. `getwhys`) → select the zip → **Upload**.
* In the bundle's **Plugins** section, click **+** and attach the `getwhys-skills` plugin to this scope.

Sessions in covered channels pick up the plugin automatically — nothing for channel members to install. To update later, re-upload the latest `getwhys-skills.zip` to the same marketplace; updates apply to **new threads only**.

## Legacy "Claude Code in Slack" — migrate before August 3, 2026

If you're still on this path: each `@Claude` coding request runs as a Claude Code session under the individual user's own Claude.ai account. Skills enabled on Claude.ai may load into these sessions depending on your workspace configuration, and the MCP server is **not** inherited — it needs to be declared in the target repo's `.mcp.json` or added as a per-session connector.

Plan to move to Claude Tag above ahead of the August 3 cutover rather than investing further here.