# Slack, Claude, and MCP

> Connect Selfwin to Slack or an MCP client while preserving project scope, revocable access, and approval boundaries.

- Product: Selfwin
- Section: Operate Selfwin
- Updated: 2026-09-06
- Canonical: https://docs.selfwin.co/integrations
- Keywords: Selfwin MCP, Claude integration, Slack AI employee, OAuth

Selfwin can be operated from its dashboard, Slack, or an MCP-compatible client such as Claude or Codex. These surfaces share the same project data and approval rules.

## MCP access

Selfwin exposes authenticated tools for project configuration, analytics, tracking, perception, sources, the Visibility Agent, and the action queue.

Access can use a revocable Selfwin token or the supported OAuth flow. Tokens are shown only when created; Selfwin stores a hash rather than the original token.

An MCP client can:

- List and inspect projects.
- Manage topics, tags, prompts, and competitors.
- Read chats, fanouts, metrics, matrices, sources, and perception results.
- Ingest an externally collected anonymous answer.
- Start tracking or the Visibility Agent.
- Read and update actions.

Tool descriptions identify writes and destructive operations. Clients should still request human approval before irreversible or external work.

## Claude

Claude can connect to Selfwin through MCP and OAuth. Once authorized, it can read the selected Selfwin project and operate the exposed tools within the user’s account.

Claude integration does not mean Claude is automatically enabled as a tracking model. Tracking channels are configured separately in project Settings.

## Slack

The Slack integration installs one project-scoped Selfwin employee in a workspace. It can provide briefs and answer supported questions using the same project evidence.

The installation stores:

- Slack team and bot identity.
- Encrypted bot token.
- Granted scopes.
- Default channel.
- Daily-brief preference and status.

Slack event receipts make retried events idempotent. A repeated Slack delivery should not create repeated work.

## Security boundaries

- MCP tokens are user-owned and revocable.
- OAuth authorization codes expire and are stored by hash.
- Slack installations are visible only to their owning authenticated user.
- Server-only OAuth and Slack records are not exposed to anonymous or authenticated browser clients.
- External publishing remains outside the default approval action.

Open **Integrations** in Selfwin to create or revoke access and test the current connection.