Slack, Claude, and MCP

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.

Connect your AI assistant

Open Integrations → Connect your AI assistant → Connect assistant.

1. Choose Claude, Codex, or Other MCP client.
2. Choose the projects and permissions the assistant may use. View access is required; manage, run, and publish access are optional.
3. Connect your assistant using https://selfwin.co/mcp.

For Claude, copy the server URL and add Selfwin in Claude's connector settings. Claude opens Selfwin's authorization screen, where you sign in, select projects and permissions, and approve. No access key needs to be copied.

For Codex or another client, Selfwin creates an access key after you choose access. Copy the URL and key into the client's remote MCP server settings. Terminal instructions are under Advanced setup. The full key is shown only once; it is stored as a hash.

A new connection shows Waiting for first connection. It changes to Connected only after an authenticated MCP request succeeds. The card shows the selected projects, access, and last-use time.

Use Manage connection to change the selected projects or permissions, Connection details to copy the server URL, and Disconnect to immediately revoke access. Existing keys cannot be revealed again.

Permissions

• View data: read selected projects, prompts, visibility, sources, fanouts, tasks, and articles.
• Manage projects: edit selected project settings, prompts, competitors, and task review states.
• Run workflows: start tracking and analysis, and request suggestions. These calls may consume provider credits.
• Publish content: publish an existing article to the selected project's connected blog when requested.

Permissions are enforced by the server, including on direct tool calls. A connection with multiple projects must specify which project to operate on. Legacy connections retain their existing account-wide access until you edit them; their cards label this explicitly.

Connecting Claude does not enable Claude 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.
• Reviewing or approving a task does not publish it. Publishing requires a separate publish permission and tool call.

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