Slack rebuilds Slackbot as an MCP client and opens an MCP agent registry
Announced June 17 with rollout continuing through July, the new Slackbot turns Slack into a surface where third-party agents are discoverable and invocable.
Slack's rebuilt Slackbot — now an MCP client rather than a simple assistant — is rolling out alongside a new MCP app registry that makes third-party agents installable and invocable from Slack. Slack's announcement, published June 17, 2026, describes Slackbot as "no longer just a helpful assistant... it's an agent that works across your apps," with a directory of MCP-powered agents installable from Slack's marketplace. The rollout and partner listings continued through July.
Context
The announcement predates the July window, but the registry build-out is the in-window story: partner agents continued listing through July, and the move anchors the "Slack as agent surface" strategy Slack has pursued since its parent company Salesforce made agents its core product narrative. MCP — the open protocol for connecting models and agents to tools and data — gives Slack a standards-based way to host other vendors' agents rather than building every capability itself.
What changed
- Slackbot as MCP client: Slackbot can now invoke external tools and agents over MCP, working across connected apps rather than only answering questions, per the Slack blog.
- MCP app registry: A directory and marketplace of MCP-powered agents, installable from Slack, making third-party agents discoverable in-product.
- July rollout: Partner agent listings and registry availability continued expanding through July 2026, per Slack's AI blog stream.
Why it matters
Slack is betting that the enterprise agent wars will be won at the distribution layer — the surface where employees already work — rather than at the model layer. An MCP registry also gives admins a single governance chokepoint: which agents are installable, with what scopes, becomes a marketplace policy decision. For Salesforce, Slackbot-as-agent complements Agentforce by putting an agent front door inside the collaboration tool.
Details
The registry is a curated marketplace listing; agents listed there are MCP-powered and installable from within Slack. Slackbot's agent behavior — invoking tools across apps — is distinct from the legacy Slackbot's canned responses. Enterprises evaluating the registry should review per-agent permission scopes, since an MCP client can chain tool calls across connected systems.
Limitations and caveats
The June 17 announcement is window-adjacent; July coverage reflects rollout continuation rather than a new launch. Marketplace agent quality and permission models vary by listing. Slack's parent-company overlap with Salesforce means the strategy framing is partly vendor narrative.
Sources
- Slack blog: Introducing the new Slackbot (official)
- Slack blog — AI (official)
*Update note: Published July 1, 2026; last reviewed July 22, 2026. Registry listings continue to expand; availability may vary by plan.*
Sources
- Slack blog: Introducing the new Slackbot — official
- Slack blog — AI — official
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.