For years enterprise software was identified with its interface: open the CRM, find a screen, fill in a form, save and move to the next screen.
Headless 360 separates two concepts we have long treated as inseparable: the value of the system and the interface through which we consume it.
Headless does not mean “without software”
Data, permissions, workflows, rules and integrations do not disappear. The access point changes. Salesforce describes Headless 360 as reusable enterprise capabilities that authorized agents can securely discover and use while preserving established governance (official Salesforce source).
From screen to capability
An application no longer has to be a destination. Reading a customer, updating an opportunity or launching a workflow can become governed primitives that an agent combines while the underlying system continues to enforce permissions and rules.
Why MCP accelerates the transition
Salesforce’s Headless 360 MCP Server exposes Discover, Describe, Dispatch and Dispatch Read Only rather than forcing a model to navigate a huge flat tool surface (Salesforce technical reference).
This highlights a broader point: exposing APIs is not enough. Discovery, selection, validation and governance become part of the architecture.
The UI changes function
Dashboards, tables and administration consoles remain valuable. What can disappear is the obligation to traverse screens simply to communicate intent.
The more interesting consequence
If AI can use software without traversing its UI, why should the software have to be manually configured before the agent can use it?
That question leads from AI consuming existing capabilities to AI helping construct persistent data, rules and processes.
We develop that argument in the pillar article After Headless 360: if AI replaces the interface, what happens to enterprise software?.
From headless to conversational software
The endpoint may not be “use Salesforce without opening Salesforce.” It may be a model in which we describe how the business should operate and the system builds or modifies the necessary process inside deterministic boundaries.
Frequently Asked Questions
It describes an approach in which Salesforce data and capabilities can be used by authorized agents and external clients without depending on the traditional graphical interface.
No. Visual interfaces remain useful, but they stop being the only way to access the system’s capabilities.
MCP gives agents a standardized mechanism for discovering and invoking tools and capabilities exposed by software systems.