By ByteBot
Salesforce’s Winter ’27 release finished rolling out on October 9. Most of it is the usual mix of admin-friendly UI tweaks and Agentforce marketing noise. But buried in the developer guide is one feature that changes your daily workflow right now: a first-party Salesforce plugin for Claude Code that auto-detects your SFDX project, connects three hosted MCP servers, and gives Claude native knowledge of your org — no context-window stuffing required. That’s the feature to install today. The rest of the release is meaningful too, but this is where the session starts.
The Claude Code Plugin Is Live
The Salesforce Development plugin is available now from the Claude Plugin Marketplace. It detects your Salesforce DX project automatically when you open Claude Code, then bootstraps context through three hosted MCP servers Salesforce runs on its end:
- salesforce-api-context — serves API reference and metadata guidance inline
- salesforce-metadata-experts — deep knowledge of Salesforce metadata types
- salesforce-lsp — a live Apex and SOQL language server exposing diagnostics, completions, and code actions as MCP tools
Once set up, Claude Code can query your org’s metadata, run SOQL, retrieve and deploy components, and execute test runs — all from the terminal. The plugin bundles roughly 40 open-source Salesforce skills, plus utility commands including /org, /login, and /setup.
Installation prerequisites: Node.js LTS (v22 or v24), Salesforce CLI, Python 3.8 or later, and an authenticated org. Install from the Claude Plugin Marketplace, then run /setup in Claude Code to validate the connection. The full walkthrough is in Salesforce’s Winter ’27 developer guide.
Salesforce is the first major enterprise SaaS platform to ship a first-party Claude Code integration. After years of Salesforce developers relying on community-built MCP bridges and manually stuffing Apex reference docs into system prompts, the platform vendor is now doing that work for you.
MCP Goes Bidirectional — And Gets 40 New Tools
Winter ’27 makes MCP support bidirectional: Agentforce agents can now act as MCP tools (external systems call them), and agents can consume MCP tools from external servers. Every major Salesforce capability is now available as an API, an MCP tool, or a CLI command. The practical effect is that Claude, ChatGPT, Cursor, or any MCP-compliant client can interact with your Salesforce org directly.
On the Marketing Cloud side, 40 new MCP tools landed for the Engagement server — automations, content folders, records management, all accessible via natural language. If you use Marketing Cloud and an AI assistant, you no longer need to context-switch out of your tools to trigger routine admin tasks.
Angular Joins React, and LWC Templates Stop Being Verbose
Multi-Framework gains Angular support in Winter ’27, alongside React. You can scaffold an app from angularinternalapp or angularexternalapp templates, embed it as a microfrontend inside a Lightning page, and pass data bidirectionally between your Angular app and native LWC components. 2GP packaging is supported for AppExchange distribution.
For LWC developers not touching Angular, the more immediately useful change is template expression GA. Complex JavaScript expressions in LWC HTML templates moved from beta (Spring ’26) to generally available in Winter ’27. Opt in by setting LWC version 66.0 or later in your .js-meta.xml:
<!-- Before: getter required in JS file -->
<p>{formattedDiscount}</p>
<!-- After: inline expression (LWC 66.0+) -->
<p>{(price * 0.9).toFixed(2)}</p>That eliminates an entire category of getters that exist only to format values or build CSS class strings. Adopt it incrementally — it’s opt-in per component, not org-wide.
Agentforce Auto-Enable: Two Risks to Check Before Production
Winter ’27 enables the Agentforce platform by default for Enterprise, Performance, Unlimited, and Developer Edition orgs. The toggle disappears from Setup. Auto-enable is not auto-deploy — nothing gets published to end users, and each agent still requires individual activation. But two integration patterns can break silently:
- SOAP
login()integrations need the “Use Any API Auth” permission, which was not previously required. Audit any integration that authenticates via SOAP before Winter ’27 reaches your production org. - Code that reads profile names can break because profile filtering is now on by default. Internal processes that compare profile names against hardcoded strings are the most common failure point.
Test in a sandbox before your production go-live. Cetdigit’s auto-enable rundown has a full checklist for affected orgs.
Two Quick Wins: Heap Limits and SOQL FORMULA()
Synchronous Apex heap increases from 6 MB to 10 MB. Asynchronous goes from 12 MB to 25 MB. Most workarounds built around hitting the old limits can now be removed — review any class that serializes large SObject collections or builds chunked-processing logic purely to stay under the old ceiling.
SOQL gains a FORMULA() function for arithmetic in WHERE clauses, reducing the need for dedicated formula fields on Opportunity and Quote objects. More useful for greenfield queries than large-scale migration, but worth knowing when designing new work.
The headline from Winter ’27 is the Claude Code plugin, but the release as a whole reflects a platform that has finally committed to AI-native development tooling. The MCP bidirectionality, the Angular support, and the template expression GA are all moving in the same direction: a Salesforce org that speaks the same protocols as the rest of the AI developer stack. Install the plugin, audit your SOAP integrations, and update your LWC version flags. Apex Hours has a deeper breakdown if you want to go further down the release notes.
