Slack (a Salesforce company) is rolling out the Slackbot MCP Client starting June 18, 2026, with full availability to all eligible customers by mid-July 2026. This update lets Slackbot securely connect to external tools and take real actions inside your conversations — and it puts new decisions in front of every Slack admin.
This guide explains what changed, who is affected, and the exact governance steps admins should take before opening MCP-powered apps to the whole organization. It is written for all Slack admins and members, with no org-specific details.
What it is: The Slackbot MCP Client implements the Model Context Protocol (MCP) — an open standard — so Slackbot can authenticate to external apps, call the right tool endpoints, and return results directly in Slack. Who it matters for: Slack admins, IT and security leaders, and members who want Slackbot to take action on their behalf. What to do: Review which MCP apps to enable in the Slack Marketplace, apply app-approval and access controls before broad rollout, and plan member enablement. Why Vantage Point is relevant: Vantage Point is a senior-only Salesforce and Slack partner with deep MCP and connector expertise, helping mid-market teams adopt agentic AI safely through governance, app approval, and the right integration choices.
The Slackbot MCP Client is Slack's implementation of the Model Context Protocol, an open standard that lets Slackbot securely connect to external tools and services through MCP servers. When you ask Slackbot to take an action, it uses MCP to authenticate, invoke the correct tool endpoints, and deliver the results directly within the conversation.
In practice, this turns Slackbot from a helper that answers questions into an assistant that can do work in connected systems. Slackbot now connects to more than 20 launch-partner MCP apps, including Figma, Canva, Box, Linear, Atlassian, Docusign, and Replit, among others. These apps render rich, interactive UIs directly within Slackbot conversations — app-specific dashboards, forms, and previews — without leaving Slack.
MCP is the same open standard, originally created by Anthropic, that powers the broader agentic AI ecosystem of connectors. If your teams are already exploring Claude connectors or Salesforce's Hosted MCP (GA April 2026), the Slackbot MCP Client extends that same pattern into everyday Slack workflows.
The shift is not just convenience. When an assistant moves from reading data to taking action — creating tickets, updating files, managing incidents — the governance bar rises. You do not need perfect data to start, but you do need clear governance over who can connect which apps and what those apps are allowed to do.
For Enterprise Grid and Enterprise+ customers, Slack provides centralized governance, workspace-level access controls, and support for apps built with MCP servers, including Salesforce, third-party, and custom solutions. That makes this a platform decision, not just a feature toggle — and a good moment to align Slack, Salesforce, and security policies.
| Group | What changes | What they should focus on |
|---|---|---|
| Slack admins | Can install/update apps with MCP servers and configure access from June 18, 2026 | App approval, access scoping, audit of data access |
| IT & security leaders | New action-taking pathways into connected systems | Governance policy, least-privilege access, monitoring |
| Members / end users | Can connect accounts and ask Slackbot to take action once apps are installed | Account connection, approved use cases, enablement |
| Enterprise Grid / Enterprise+ | Centralized governance and workspace-level controls for MCP apps | Org-wide policy, custom and Salesforce MCP servers |
Use existing app-approval settings and governance controls — they still apply to MCP apps. Then work through these steps before a broad rollout:
Governance nuance: Agents that take actions raise the stakes on access control. Treat MCP app enablement like any other privileged integration — approve deliberately, scope tightly, and review regularly.
| Date | What happens |
|---|---|
| June 18, 2026 | Rollout begins. Admins can install or update apps with MCP servers and configure access permissions. |
| Mid-July 2026 | Full rollout to all eligible customers. |
To prepare, review available apps in the Slack Marketplace, visit the Slack Help Center for full setup guidance, and contact your Slack account team with questions.
The Slackbot MCP Client is one more sign that MCP is becoming the default way assistants connect to business systems. We cover the standard in depth in what MCP is and how it works and in Anthropic's MCP for business data. If you are weighing the governance risks of action-taking agents, our MCP security guide walks through the controls that matter. For the broader Slack June 2026 changes beyond the MCP Client, see our Slack June 2026 admin updates roundup.
Do not wait for mid-July to think about governance. Use the June 18 start date to pilot a short list of MCP apps with a trusted group, confirm your app-approval and access policies, and document which actions Slackbot is allowed to take. Mid-market teams that align Slack, Salesforce, and security policy now will roll out faster — and safer — than teams that flip the switch organization-wide on day one.
Vantage Point is a US-based, employee-owned, senior-only Salesforce and Slack consulting partner, a HubSpot Gold Partner, and an Anthropic Registered CPN member. We have deep MCP and connector experience — including Salesforce Hosted MCP and our ongoing Claude connector ecosystem work — and we help mid-market teams adopt agentic AI safely.
For the Slackbot MCP Client specifically, we help you choose the right launch-partner apps, configure app approval and compliance and security controls, define access policy, and connect Slack actions to your CRM and back-office systems through system integration and data services.
Ready to roll out the Slackbot MCP Client with confidence? Book a Slack and Salesforce governance and agentic-AI enablement consultation with Vantage Point. We will help you decide what to enable, how to govern it, and how to drive adoption without opening unnecessary risk.
The Slackbot MCP Client is Slack's implementation of the Model Context Protocol, an open standard that lets Slackbot securely connect to external apps via MCP servers. It authenticates, invokes the correct tool endpoints, and returns results directly in your Slack conversation.
According to Slack, the rollout begins June 18, 2026, when admins can install or update apps with MCP servers and configure access permissions. Full availability to all eligible customers arrives mid-July 2026.
Slack says Slackbot now connects to more than 20 launch-partner MCP apps, including Figma, Canva, Box, Linear, Atlassian, Docusign, and Replit, among others. These apps render interactive dashboards, forms, and previews directly inside Slackbot conversations.
Admins should review which MCP apps to enable in the Slack Marketplace, apply existing app-approval and governance settings, define who can connect accounts and take actions, and audit data-access implications before a broad rollout. Existing app-approval and governance controls continue to apply.
It can be, with the right controls. Enterprise Grid and Enterprise+ customers get centralized governance, workspace-level access controls, and support for Salesforce, third-party, and custom MCP servers. Because Slackbot can take actions, scope access tightly and approve apps deliberately.
Once apps are installed, members can connect their accounts and ask Slackbot to take action — such as creating tickets, updating files, or managing incidents — without leaving Slack. What they can do depends on the apps and access policies the admin approves.
MCP, or Model Context Protocol, is an open standard originally created by Anthropic that lets AI assistants connect to external tools and data through MCP servers. It is the same standard powering the broader agentic AI connector ecosystem across platforms like Salesforce and HubSpot.
Vantage Point helps mid-market teams choose which MCP apps to enable, configure app approval and access controls, audit data-access risk, and connect Slack actions to CRM and back-office systems. As a senior-only Salesforce and Slack partner with MCP expertise, we focus on safe, governed adoption.