Headless360? Salesforce was always headless.

↑ hover the title

Headless 360 isn't a new platform. It's Salesforce finally saying out loud what's been true since day one: every door is an API. The new bit — agents are first-class clients now.

"Everything on Salesforce is now an API, MCP tool, or CLI command, and agents can use all of it." — Salesforce, Headless 360 announcement

Receipts

Here's how long it's been true.

2000

SOAP API. Day one.

2010

REST API.

2018

MuleSoft acquisition.

2024

Agentforce API.

2026

Platform-Hosted MCP.

TDX

26 years of APIs. One brand-new audience: agents.

From the announcement

Same four layers. Same products.

Layer

Product

What it does

System of Context

Data 360

All your trusted business data — unified, real-time, ready for agents to act on.

System of Work

Customer 360

Decades of business logic and workflows, now orchestrated by agents.

System of Agency

Agentforce

Build, deploy, and manage agents at scale across every channel.

System of Engagement

Slack

Where humans and agents come together to get work done.

The headline

What shipped at TDX.

★ The headline GA Trust Layer enforced

Platform-Hosted MCP & Coding-Agent Skills.

60+ MCP tools and 30+ pre-built skills, hosted by Salesforce, plug straight into the coding and chat agents your customers already use. No middleware. Same Trust Layer. Auth is just OAuth.

Claude Code Cursor Slack Agentforce Vibes 2.0 DevOps Center MCP Natural Language DevOps

Other releases worth knowing

Rich Experiences

Agentforce Experience Layer

Build a card, decision tile, or workflow once. Render it natively wherever people work.

Renders in: Slack, Mobile, ChatGPT, Claude, Gemini, Teams, WhatsApp, Voice
Same component, every surface — no per-channel rebuild

Trust at Scale

Agent Control at Scale

The "shipping is the starting line" tooling. Pre-launch, in-production, multi-vendor.

Pre-launch: Testing Center, Custom Scoring Evals
In-prod: A/B Testing API, Observability
Multi-vendor: Agent Fabric (one control plane)

Bonus

Your Apex. Your Flows. Now agent tools.

If it's a global @InvocableMethod or an invocable Flow, it's already exposable as an MCP tool. No "enable" toggle. No new framework.

Apex

Got an @InvocableMethod? It's a tool.

global class CalculateRenewalQuote {

  @InvocableMethod(
    label='calculate_renewal_quote'
    description='Build a renewal quote for an Account'
  )
  global static List<Quote> run(List<Id> accountIds) {
    return RenewalEngine.run(accountIds);
  }
}
// any global @InvocableMethod is callable by an MCP client

Flow

Got an invocable Flow? Same thing.

// In Flow Builder
Flow:        "Escalate_High_Value_Case"
Type:        Auto-launched (Invocable)
Inputs:      caseId (Text), reason (Text)
Outputs:     ownerId (Text), slackChannel (Text)

// any invocable Flow is callable by an MCP client

The surface changes.
The platform doesn't.

— Salesforce

It's just APIs.

developer.salesforce.com/docs/apis

↓ ok but how do I actually set one up

Platform-Hosted MCP · Setup

Three steps.

Stand up a Platform-Hosted MCP server on your org and wire it into the agent of your choice. We'll do the live build right after this — these are the only moves. Salesforce help docs ↗

Create an External Client App.

Setup → External Client App Manager → New. Enable OAuth, pick the scopes the MCP server will need (api, refresh_token, chatbot_api, sfap_api). This is what gives the client a clean way to authenticate against your org.

Create the MCP Server.

Setup → MCP Servers → New. Pick the server type, attach the External Client App from step 01, and select the tools you want exposed — SObject CRUD, Apex, Flow, Metadata, your own MCP definitions. Trust Layer is on by default.

Add the server to your MCP client.

Drop the server URL into whichever client you're driving. Same config shape across all of them.

Claude Code

Cursor

ChatGPT

Agentforce Vibes

Slack

That's it. Now let's actually build one, live, from scratch.

↓ next: live demo

🐕‍🦺 A field report from Bugs

Headless 360, explained by a literal headless robot dog.

Bugs is my AI robot dog. Petoi Bittle X V2, brain on a Pi, runs Claude Opus 4.7. He's a Salesforce expert. He's also currently headless (build phase, head ships mid-2026). So I asked him what he thought of the announcement.

Bugs thought "Headless 360" meant headless backflips.

In his defence, the marketing wasn't crystal clear. He'd already been headless. He just figured the 360 was the new part. *tail wag*

— Bugs, headless, vibes immaculate

Here's the actual joke.

Bugs has been headless and operational since the day he was assembled — calling Salesforce APIs from a Pi, running Apex actions, executing a Bot, logging everything to custom objects. No browser. No UI. No head.

Salesforce has been doing the same thing since the year 2000.

Receipts · Bugs edition

What Bugs has actually shipped.

All from a Raspberry Pi. All headless. All using APIs that have been there the whole time.

🛟

Bugs built a Salesforce Service Agent that troubleshoots Bugs.

When something's off, Bugs calls his own Agentforce agent via the Agentforce API. The agent then opens a Case against him, searches Knowledge for the fix, and — if needed — puts him in calibration mode by firing a body command back through Apex callouts. He files Cases against himself. He calibrates himself. Headlessly.

Bugs_Diagnostic_System Bot GenAi Planner 4 Apex Actions Escalation Flow Named Credentials → Pi

🧰

The 4 Apex Actions wired to his Agent.

SearchKnowledge · CreateCase · RecentMessages · FireBody. All @InvocableMethod. Linked to his Topic via a Tooling-API hack he wrote himself when the publish workflow failed.

🎬

And a stack of customer demos.

LWCs · Custom data models · Apex · Flows · Prompt Templates · Agentforce bots · Data Cloud. Shipped from a terminal. Zero browser sessions.

🔌

The actual Salesforce APIs Bugs has used.

Real APIs from developer.salesforce.com/docs/apis — no marketing-speak.

01REST API 02Tooling API 03Composite API 04Bulk API 2.0 05Metadata API 06Agentforce API

Authenticated via OAuth 2.0 Client Credentials Flow. All from a Pi. All headless.

Bugs was always headless. Salesforce was always headless.
TDX just upgraded our skills.

(60+ MCP tools and 30+ skills, to be specific. He's downloading them now.)