How to Use Claude in Slack | Setup Guide for Connectors and MCP Integration

What Can You Do by Integrating Claude with Slack?

Anthropic officially announced the Claude and Slack integration in January 2026. The integration enables two broad categories of functionality:

• Using Claude inside Slack: You can consult Claude via direct message, or mention @Claude in a thread to get responses. Access through the AI assistant panel is also supported.
• Referencing Slack from Claude apps: While conversing in Claude.ai (web version) or Claude Desktop, you can search relevant Slack discussions, channels, and files to incorporate them as context for responses.

For example, when preparing for a meeting, you can delegate an entire workflow in a single instruction: checking related Slack discussions, gathering necessary documents, and creating a briefing summarizing the latest information and key decisions. Source: Claude and Slack (Anthropic official).

Two Integration Methods: Slack Connector and MCP

There are two ways to connect Claude and Slack, each differing in supported plans and ease of setup.

Think of the Connector as the "official standard integration" and MCP as the "custom extended integration you configure yourself." For a detailed comparison, Claude and Slack Integration Explained (Zenn) is also a helpful reference.

Supported Plans and Prerequisites for the Slack Connector

The official Slack Connector has different availability dates depending on your plan.

• Claude Pro / Max: Available from January 26, 2026.
• Claude Team / Enterprise: Available once the Slack app is installed and the connector is enabled by an administrator.

In all cases, a workspace administrator must have approved the app in the Slack Marketplace. After approval, users connect by logging in with their existing Claude account credentials. Source: Use connectors to extend Claude's capabilities (Claude Help Center).

Setup Steps for the Slack Connector

Assuming administrator approval is already in place, users can complete the connection with the following steps:

1. The workspace administrator approves the "Claude" app in the Slack Marketplace.
2. Open Claude.ai settings and navigate to the "Connectors" tab.
3. Select Slack from the list and authorize the connection.
4. In Slack, mention @Claude and select "Connect Account" to link your Claude account.

After connecting, you can combine Claude with its existing capabilities such as web search and document analysis. This means context from previously connected documents, emails, and more can be pulled directly from conversations in Slack.

Integration via MCP (Available on All Plans)

If the official connector is unavailable for your plan, or if you want more flexibility, MCP is the alternative. This approach involves creating a Slack Bot app yourself, generating a token, and registering it with Claude Desktop.

1. Create a Bot app in the Slack API dashboard, grant the necessary permissions, and obtain a token.
2. Find the Team ID of the workspace you want to connect.
3. Enter the obtained token and Team ID in Claude Desktop's configuration file claude_desktop_config.json.
4. Restart Claude Desktop to apply the connection.

Via MCP, you can search channels and DMs, post messages, create Canvases, and build workflows combining other MCP tools such as GitHub or Google Drive. For configuration examples, Claude and Slack Integration (Zenn) provides detailed guidance.

Claude Code x Slack: Automating Everything from Bug Reports to PR Creation

Development teams are also paying attention to connecting Claude Code and Slack via MCP. The idea is to retrieve bug reports posted to a Slack channel and then automatically carry out the entire process——from investigating the root cause and fixing the code to creating a Pull Request. A chat request becomes the direct starting point for a development task. Real-world examples are introduced in Requesting Code Fixes from Slack Directly to Claude Code (Qiita) and Claude Code x Slack Integration (start-link).

Choosing Between the Connector and MCP

If you are on Team or Enterprise, using both in combination is practical. You can divide roles: use the Connector for quick questions and searches directly in Slack, and use MCP for embedding into development workflows or combining multiple tools. If you are on Free or Pro and want to try Slack operations, starting with MCP is the realistic approach. For post-adoption impressions and business use cases, Claude Now Available in Slack (Chaen AI Lab) is also a useful reference.

Security and Privacy Considerations

A key concern when integrating is how internal conversation data is handled. According to official information, Claude in Slack maintains the same security standards and privacy settings as individual Claude accounts, and only searches channels that the user has access to. It will not independently access all channels beyond the boundaries of your permissions. Before deployment, it is advisable for administrators to review the scope of approvals in alignment with your organization's workspace data handling policies. Source: Claude and Slack (Anthropic official).

Summary

The Claude and Slack integration enables two-way functionality: "talking to Claude within Slack" and "searching and referencing Slack from Claude." If ease of use is your priority, go with the Connector (available for Pro / Max / Team / Enterprise). If flexibility is what you need, MCP works across all plans. In development environments, the Claude Code x Slack combination is also gaining traction for automating everything from bug reports to PR creation. Start with whatever method is available for your plan, and transform Slack——where your team's information is already gathered——into Claude's working environment.