Salesforce and Anthropic unite Claude's world-class intelligence with Salesforce's trusted data, workflows, actions, and governance — delivering AI built for your customers and trusted by your business.
SF
Published by
Salesforce & Anthropic
Aug 26
2026
10 min
read
Q2 FY27 earnings day
Cloudeforce
What is Claudeforce?
Claudeforce is the expanded strategic partnership between Salesforce and Anthropic, publicly announced on August 26, 2026 — coinciding with Salesforce's Q2 FY27 earnings. It runs in two directions: Claude moves into Salesforce as a first-class reasoning model, and Salesforce moves into Claude as a plugin carrying 37 prebuilt sales skills.
Rather than a superficial integration, Claudeforce is the commercial packaging of Salesforce's Headless 360 architecture — a platform initiative that exposed Salesforce capabilities as APIs, MCP tools, and CLI commands. Launched in April 2026, Hosted MCP Servers entered Beta in July 2026, laying the technical foundation. The core administrative insight is elegant: one admin connects the org once. Every user gets access scoped to their own existing Salesforce permissions.
When people stop using Salesforce through the traditional human interface and start using it through an agentic interface, it dramatically increases the value of Salesforce.
— Patrick Stokes, President of Applications & Marketing, Salesforce
83%
Salesforce workforce using Claude-powered Slackbot
8.1M
annualized productivity hours gained
37
prebuilt sales skills in the Claude plugin
150%+
QoQ Slackbot user growth
Three Distinct Workstreams
Claudeforce is an umbrella name covering three initiatives with different maturity levels, buyers, and risk profiles. Keep them separate before planning your pilot.
🧠
Claude in Salesforce
Claude as a reasoning model across Atlas, Vibes, Coworker, and Agent Builder — served through Amazon Bedrock inside the Salesforce Trust Boundary.
🔌
Salesforce in Claude
A plugin in the Claude interface with 37 prebuilt sales skills. Single-admin setup. Every seller gets access scoped to their own permissions.
💬
Claude in Slack
Claude becomes the default model for Slackbot, Claude Tag, and Slack Code — already driving 8.1M annualized productivity hours inside Salesforce.
Workstream 1: Claude in Salesforce
A clarification most launch coverage missed: Claude didn't arrive in Agentforce this week. It has been a foundation model since late 2025. What Claudeforce does is make that placement official across four specific surfaces. Claude inference runs through Amazon Bedrock inside the Salesforce Trust Boundary — your data never leaves Salesforce's security perimeter.
Surface
Claude's Role
Status
Atlas Reasoning Engine
Powers agent plan-and-act loops
Available
Agentforce Vibes
Default model in the Vibes IDE
Default
Agentforce Coworker
Default model
Default
Agent Builder
Selectable alongside Amazon Nova
Available
Model optionality is preserved
Prompt Builder still offers Amazon Nova Lite and Nova Pro alongside Claude models. Nobody is forcing a single-model architecture on your org.
Workstream 2: Salesforce in Claude
The headline product — the genuinely new thing. A plugin in the Claude interface shipping with 37 prebuilt sales skills co-engineered with Anthropic against Claude's reasoning and agentic tool use. On first run, the plugin sweeps a seller's context across Salesforce, Slack, and connected tools, then surfaces a tailored dashboard assembled on the fly.
Design Decision
What It Means
Single-admin setup
One org-level connection. Central auth. No per-user MCP config.
Scoped permissions
Each user accesses only what their existing Salesforce permissions allow.
Context sweep on first run
Reads seller context across Salesforce, Slack, and connected tools on first login.
Dynamic UI generation
Claude generates dashboards as live HTML from real Salesforce data in real time.
Status
Select Pilot → Open beta September 2026
Four Value Pillars
👤
AI for Every Employee
Boost productivity and make every team stronger through embedded Claude assistance.
💬
AI for Every Customer
Deliver smarter, faster, and more personalized customer experiences at scale.
🔗
AI on Salesforce
Seamlessly integrated. Deeply trusted. Infinitely powerful across the whole platform.
🛡️
Built on Trust
Enterprise-grade security, privacy, and reliability you can count on.
Workstream 3: Claude in Slack
Claude becomes the default model for Slack, powering Slackbot, Claude Tag, and Slack Code. The internal Salesforce numbers are the most persuasive data in the entire announcement — because Salesforce is eating its own cooking. 83% of its workforce uses the Claude-powered Slackbot, generating 8.1M annualized productivity hours, with QoQ growth exceeding 150%. Slackbot activity now counts in Agentforce ARR as of Q2 FY27.
Auth note for architects
Claude Tag's Salesforce connection uses the OAuth 2.0 client credentials flow with a dedicated integration user — different from the Hosted MCP Server's per-user OAuth. Every request in the Access bundle runs as that one integration user.
Architecture: How It Actually Works
The Salesforce in Claude plugin is the Headless 360 Hosted MCP Server architecture with a managed auth layer on top. The platform/headless-360 MCP server exposes just four tools — a deliberately small surface that makes Claude search for the right operation, read its spec, then call it.
Discover
discover
Semantic search across all Salesforce operations. Returns ranked candidates so Claude finds the right API without drowning in hundreds of tools.
Describe
describe
Returns the full technical spec for a chosen operation — parameters, field types, required inputs — before Claude commits to calling it.
Dispatch
dispatch
Invokes the operation with full read/write access (GET, POST, PUT, DELETE, PATCH). Standard Salesforce writes fire normally.
Dispatch Read-Only
dispatch_readonly
GET-only variant. Start all pilots here — enables full analysis and reporting without exposing any write path.
Best Practices & Gotchas
1
Audit permissions before you pilot — not after
Over-provisioned profiles that were harmless behind a slow UI become genuinely risky behind an agent. This is the single highest-value prep step.
2
Start read-only, expand deliberately
Use dispatch_readonly. Add write access per skill only after watching what the agent does in your sandbox.
3
Writes hit your full automation stack
A dispatch PATCH is a normal Salesforce write. Validation rules, Flows, and Apex triggers all fire.
4
Instrument tokens before signing anything org-wide
Pricing is consumption-based, contracted separately with Anthropic. Run a pilot cohort and get your own token number first.
5
Govern your MCP registry before pilots expand
Teams building their own MCP connections alongside the official plugin is shadow IT with better branding.
6
Stagger the beta and your Winter '27 upgrade
Open beta lands September 2026, right on top of Winter '27 production waves. Running both in the same sandbox makes debugging impossible.
Availability Timeline
Component
Status
Notes
Claude in Atlas Reasoning Engine
Available
Powers agent plan-and-act loops
Claude in Agentforce Vibes & Coworker
Default
Alternatives still selectable
Claude in Agent Builder
Available
Selectable alongside Amazon Nova
Salesforce in Claude plugin
Select Pilot
Open beta September 2026
Claude Tag (Slack)
Public Beta
Includes Salesforce connection
Slackbot + Slack Code
Rolling Out
83% Salesforce internal adoption
platform/headless-360 MCP Server
Beta
Requires Salesforce API v67.0+
Winter '27 / API v68.0
Notes Live
Production: 4 Sept, 2 Oct, 9 Oct 2026
Additional skills beyond sales
Planned
Late 2026 — domains TBA
AgentforceAI CRMAnthropic ClaudeClaude in SlackClaudeforceHeadless 360MCP ServerSalesforce AIWinter 27
Ready to pilot Claudeforce
in your org?
One admin connection. Every seller gets AI, scoped to their own permissions. Start with read-only.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.