H

Headless 360

Salesforce’s architectural shift exposing every platform capability as an API, MCP tool or CLI command — making the browser interface optional so agents can plug in natively.

What it is

Headless 360 is Salesforce’s architectural transformation that, in its own words, "exposes every capability Salesforce has built over 25 years directly as an API, a Model Context Protocol (MCP) tool, or a CLI command." Its stated purpose is to make the browser interface optional, so AI agents can natively plug into Salesforce data, workflows and business logic. The release included over 60 new MCP tools, 30+ preconfigured coding skills, and the Headless Experience Layer.

Why it matters

It is the umbrella the rest of this vocabulary sits under. Multi-Framework is how a human-facing app gets built without the browser being the only way in; MCP tools are how an agent reaches the same capabilities. Both are expressions of one shift — the interface stops being the product surface and becomes one consumer among several.

Key components

  • Every capability as an API, MCP tool or CLI command
  • 60+ MCP tools
  • 30+ preconfigured coding skills
  • Headless Experience Layer
  • Salesforce Multi-Framework

How it connects

The Headless Experience Layer separates business logic, data and permissions from the screen, so one definition renders across surfaces. Multi-Framework is the runtime that lets those surfaces be built in React.

Good to know

Headless 360 is the platform-level programme; Multi-Framework is the specific runtime a React app uses. The two get used interchangeably and are not the same thing.

Need Help Implementing This?

We specialize in putting AI and Agentforce to work for Salesforce customers. Let's talk about your use case.

Book Intro Call