Slack
Your Slack workspace, connected to the agent
Let your AI read and write in Slack
Channels, threads, users, profiles, messages and reactions — with explicit scopes.
Slack is where team decisions, status updates, incidents, threads and conversations live. The official MCP server connects Claude to the Slack Web API to "interact with Slack workspaces": read channels, fetch threads, list users, inspect profiles, post messages and add reactions.
What it does: it lists public or pre-defined channels, reads recent channel history, fetches thread replies, posts messages, replies in threads, adds emoji reactions and reads users/profiles. If you set SLACK_CHANNEL_IDS, you limit scope to specific channels.
What you can ask
- "Summarize the last 50 messages in the incident channel and extract action items."
- "Post this deploy status in
#engineeringand reply in the release thread." - "Find the profile for this user ID and tell me their timezone before I ping them."
What token you need
You need a Slack App installed in your workspace and its Bot User OAuth Token (xoxb-...). The official README asks you to create the app from api.slack.com/apps, go to OAuth & Permissions and add these scopes:
channels:history— View messages and other content in public channelschannels:read— View basic channel informationchat:write— Send messages as the appreactions:write— Add emoji reactions to messagesusers:read— View users and their basic informationusers.profile:read— View detailed profiles about users
Then install the app to the workspace, copy the Bot User OAuth Token and find the Team ID (starts with T). Paste them when the Lab asks for SLACK_BOT_TOKEN and SLACK_TEAM_ID. Terminal Sync stores them encrypted in your Keychain.
We open the app and set it up in Claude Code (and your other Macs).
How it works with Terminal Sync
Set up the connector once on one machine. Terminal Sync keeps your claude_desktop_config.json encrypted in your Drive, so on any other machine where you open Claude Code, the connector is already there.