Slack MCP Server — Slack Integration for AI

What it is

This Slack MCP Server provides Slack workspace integration for AI tools via the Model Context Protocol. It lets AI assistants like Claude Code and Cursor read channels, post messages, search conversations, and manage threads within Slack workspaces. The server runs locally and communicates with the Slack API using a bot token.

This integration targets developers who want their AI coding tools to participate in team communication without switching to the Slack app. The AI agent reads context from channels and posts updates directly.

Why it saves time or tokens

Context switching between coding and team communication breaks focus. This MCP server keeps everything in one interface. The AI agent can search Slack history for past decisions, post code review summaries to channels, and notify teams about deployments without the developer leaving their editor.

How to use

1. Create a Slack Bot with the necessary OAuth scopes in your Slack workspace settings
2. Add the MCP server configuration to your AI tool's settings with the bot token
3. Use natural language to instruct the agent to interact with Slack

Example

{
  'mcpServers': {
    'slack': {
      'command': 'npx',
      'args': ['-y', 'slack-mcp-server'],
      'env': {
        'SLACK_BOT_TOKEN': 'xoxb-your-bot-token',
        'SLACK_TEAM_ID': 'T01234567'
      }
    }
  }
}

Example agent commands:

• 'Read the last 10 messages in #engineering'
• 'Post to #releases: v3.2.0 deployed successfully'
• 'Search Slack for database migration discussions'

Related on TokRepo

• MCP Slack integration — dedicated Slack MCP page on TokRepo
• AI tools for automation — communication automation tools

Common pitfalls

• The bot must be explicitly invited to each channel it needs to access; it cannot read channels it has not joined
• Slack rate limits apply to bot API calls; rapid operations may be throttled
• Bot tokens with broad scopes can read sensitive channels; use the principle of least privilege when configuring OAuth scopes