Slackbot’s MCP Client

The shared-channel angle is the part I’d test hardest.If Slackbot takes an action from a channel, is authority bound to the requester, the channel, or the app install? For things like signing docs or updating tickets, that identity boundary is what makes the audit console useful.

I use Slack daily, and I really appreciate the MCP client ecosystem, the ease it makes in connecting the context and the actions you need to an AI chat interface. Everyone has their own personal preference on where they like that interface to live, and I think more options make it easier for everyone to find their ideal interface. The personalization in that way is very useful while at the same time giving everyone the same access to the tools and "middleware" we all use.

We are on an enterprise account, but when I follow the instructions on https://docs.slack.dev/ai/slackbot-mcp-client/ and go to https://api.slack.com/apps and do a "Create a new app", I do not see the MCP option.

The "multiplayer" framing is the underrated part. Read side is an easy yes; the write side across 20 apps is where small teams freeze. But running actions in a shared channel instead of a private DM means the team sees what got done in real time — the channel becomes a free audit log. That visibility might do more for trust than any confirm dialog. Does it post a structured "here's what I changed" back to the channel after a write?

The read side of this is an easy yes; the write side is where I'd want detail. "Sign docs" and "update tickets" from a plain-language command means the model is interpreting intent and then taking an irreversible action inside someone else's app. As someone who ships an MCP server, the thing that earns trust is a clear confirm step on anything destructive and a visible log of what it actually did, not just what you asked it to do.

What I find most interesting is that this turns Slack into the interface rather than another tool to switch to. Curious… have you seen users adopt it more for retrieving information across apps or for actually taking actions and completing workflows from Slack?

Slackbot's MCP client is Slackbot's AI that connects 20+ apps into one multiplayer conversation.Teams use isolated AI tools across private tabs, manually carrying data between systems. Slackbot becomes the connective layer for your entire stack, coordinating actions in plain language in team channels.Work is multiplayer from the start in Slack channels, not single-player silos in private tabs.Features:Actions, not just answers: sign docs, update tickets, review dashboards right from SlackbotNative Block Kit support (coming soon): rich visuals like data tables update in real timeMultiplayer execution: share Slackbot's response into a channel for team collaborationPlug-and-play MCP integration: connect any tool via MCP server in minutesEnterprise-grade security: user-specific data boundaries, IT admin audit consoleBenefits: Finish tasks faster, scale best practices, maximize software ROI, collaborate with live data.Who it's for: Engineering, sales, marketing, product teamsUse cases:Track Linear tickets + PagerDuty incidents (Product & development)Find Q2 pitch decks (Document management)Review Canva layouts (Creative & design)Draft Docusign agreements (Business operations)Analyze Tableau trends + Lucidchart diagrams (Visual collaboration)P.S. I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends