Connect Claude Tag

Claude Tag is Claude working in your Slack channels as your organization's own identity, not as each person's account. Connecting XPT Tracker to it lets anyone in a channel ask about tasks, projects and the knowledge base without leaving Slack.

This is a different connection from the one on Connect Claude. That one belongs to a person and follows them into Chat, Code and claude.ai. This one belongs to a Slack channel, is configured once by an administrator, and serves everyone in that channel. Both can exist side by side: in a direct message with Claude, the personal connector is what applies.

Setting this up takes an Owner in your Claude organization and an administrator of your Slack workspace. Claude Tag is in public beta, so the admin screens named below may shift.

Before you start

Create the account the connection will run as

Do this before you connect anything.

The connection signs in to XPT Tracker once, and from then on the agent acts as whichever account was signed in at that moment. Every task it creates, every comment it leaves and every page it edits is attributed to that account, and it can reach exactly what that account can reach. Anyone in a channel the connection covers is using it.

So create a member for the agent rather than using your own account:

1. In XPT Tracker, open Settings → Members and invite an address you control, such as claude@yourcompany.com.
2. Accept the invitation from that mailbox and finish creating the account.
3. Give it the narrowest role that covers the work you expect from it.

Connecting under your own account works and is tempting during a pilot, but it leaves the agent's writes indistinguishable from yours in the task history, and it hands every channel member your level of access. Re-connecting later under a dedicated account is quick; untangling the history is not.

Pair the Slack workspace

Open claude.ai/admin-settings/claude-tag and select Start setup. The page walks through the steps below in order and saves your progress.

1. Install the Claude app in Slack. From claude.com/claude-for-slack, select Add to Slack and approve the permissions. If the app is already installed, install it again over the existing one — settings and the @Claude handle are kept.
2. Invite Claude to a channel. Pick a channel for the pilot and run /invite @Claude. In a private channel, a mention alone does not reach Claude: Slackbot intercepts it and offers Add Them.
3. Request the pairing code. Send @Claude connect as a message with no other text. Claude replies with a code visible only to you, valid for 15 minutes. Only a Slack workspace administrator can run this; anyone else is told whom to ask. On Enterprise Grid, the reply carries two codes — the enterprise_ one pairs every workspace in the Grid.
4. Redeem the code in the Paste the pairing code field on the setup page.
5. Choose where Claude may reply — the entire workspace, or specific channels by ID. For a pilot, name the one channel.
6. Skip the tool steps. Choose Claude's first tools and Connect GitHub are about other services; XPT Tracker is added afterwards, as a connection. Selecting tools there commits you to nothing, and Skip on the accounts step is safe.
7. Fund and launch. Channel work draws from a usage balance, so the setup page asks you to buy credits before it lets you launch. Until you select Launch Claude Tag, every mention is answered with "Claude is disabled in this channel".
8. Set a spend limit at claude.ai/admin-settings/usage/claude-tag. When the setup included a credit purchase, the launch screen does not offer the limit, so it has to be set afterwards.

Confirm Claude answers at all before going further. In the channel, ask it to summarize the week. A reply in a thread, with a footer naming the model and a Configure link, means the channel is covered.

Add XPT Tracker as a connection

Claude's access in channels is held in an Access bundle — a named set of credentials, domains, repositories and plugins attached to a scope. Setup created one for your workspace.

1. On claude.ai/admin-settings/claude-tag, open Access bundles and select your bundle.
2. On the Credentials tab, find Custom tool at the foot of the list and open the arrow next to its Connect button. Choose Connect MCP connector.
3. Give the connection a name, then open the Provider list and select Add custom connector… at the bottom.
4. Paste your workspace's MCP URL. Copy it from Settings → Connect to Claude in XPT Tracker; it has the form https://mcp.xpt.ai/<your-workspace>/mcp. Select Verify connector.
5. Sign in to XPT Tracker as the account you created above. The sign-in uses whatever session your browser already holds, so open a private window, or sign out first, unless you are already signed in as that account.

The connection is then listed under Connected, and on the Access bundles page it shows Active once an allow rule uses it. Never used is only a counter; it changes the first time Claude calls the server.

Check which scope the bundle is attached to — the used in N places link on the bundle says. A bundle on the workspace covers every channel in it; a bundle on one channel covers only that one.

Verify it works

Claude is told about a connection when a session starts, so use a new thread; an existing one keeps the access it began with. Changes reach the network layer within about a minute.

@Claude what can you access from this channel?

The connection should be listed alongside Slack. Then ask for something that requires a real call:

@Claude what projects in XPT Tracker are in progress right now?

A good sign that the connection carries more than raw access: asked to create or change something, Claude follows the workspace's own process. XPT Tracker hands every client its process instructions at connection time, so the workflow tools (wf_task_create and the rest) are used rather than the underlying primitives.

Tune the experience

Channel work runs in a sandbox that is created when a conversation starts and discarded when it goes idle, and Claude posts a progress checklist as it works. That makes a delegated job — investigate this, open a pull request — feel natural, and a one-line lookup feel slow. Three settings help:

For quick questions to the tracker throughout the day, the personal connector on Connect Claude is the better surface: no sandbox, no Slack round trip. Claude Tag earns its setup on work you hand over and collect later.

If something does not work