Slack Connect MCP integration
Connect Slack channels and thread context to MCP workflows so agents can read, write, and coordinate work from team conversations.
Slack is a first-class collaboration provider in Connexsus. Instead of treating chat as an isolated UI, the gateway exposes workspace messaging context as reusable MCP tools for support, incidents, and team coordination.
Install path
This provider uses a managed OAuth redirect flow. Teams sign in, authorize the workspace, and then enable the provider inside a project.
What you can do with Slack Connect
- List channels and summarize relevant threads.
- Post a status update from an operational workflow.
- Bridge issue, incident, and chat context between tools.
Sample prompts
Available capabilities
8 toolsslack_list_channels
List public and private Slack channels visible to the connected workspace.
slack_get_channel
Get metadata for a Slack channel by channel ID.
slack_list_channel_messages
List messages in a Slack channel.
slack_get_message_thread
Read replies for a Slack thread.
slack_post_message
Post a bot-authored message to a Slack channel.
slack_reply_in_thread
Reply to an existing Slack thread with a bot-authored message.
slack_list_users
List Slack users visible to the connected workspace.
slack_get_user
Get a Slack user by user ID.
FAQ
Which Slack mode does Connexsus use?
Slack uses a bot-token-first OAuth flow in v1 for core collaboration tools.
Are DMs included?
No. The first-class Slack v1 scope focuses on channels, threads, users, and bot-authored collaboration actions.
Why is Slack valuable for MCP?
Because operational context often lives in channels and threads, and that context is expensive to recreate manually in every client.
Auth and workspace model
Connexsus separates public provider information from private runtime state. Teams install the provider after sign-in, assign it to a project, and then expose tools to supported MCP clients from one managed gateway endpoint.