What it can do is exactly what the Slack bot can do: read the channels it has been given, post and reply in threads, react, and look up who people are — and an optional variable is there for when you would rather it only saw a few channels.
A Slack MCP server published by 김팔복TV as example code for the setup they use. Eight tools cover the workspace's public or pre-declared channels, posting and replying, emoji reactions, message history, thread replies and user profiles. It runs locally over stdio.
- The workspace's public channels listed, or only the channels you declared in advance
- A message posted to a channel
- A reply posted into an existing message thread
- An emoji reaction added to a message
- Recent message history from a channel
- Every reply under one thread
- All workspace users with their basic profiles, and one user's profile in detail
A Slack bot token in SLACK_BOT_TOKEN and the workspace id in SLACK_TEAM_ID, with the scopes you need granted under OAuth and Permissions on the Slack app. A further optional variable narrows the server to a comma-separated list of channels. Runs through npx against kimpalbok-slack-mcp-server. The documentation is written in Korean.
One command plus a key — npx -y kimpalbok-slack-mcp-server, then supply credentials