Headless Data 360 [What It Changes]

TL;DR

• Headless Data 360 is Salesforce's Model Context Protocol server for Data 360: it exposes more than 200 Salesforce APIs so AI agents can query, transform, segment, and activate customer data without a person logging into the CRM, as of August 19, 2026.

• The Data 360 MCP Server is generally available; the broader Headless 360 MCP server and Experience Layer are in open beta (TechTarget).

• MCP access is included with Enterprise Edition and above and consumes existing API limits; Flex Credits apply when you invoke Agentforce actions, Data 360 queries, or Prompt Builder.

• A 10-person marketing agency does not need a Salesforce rebuild. It needs one governed path from form to CRM to agent, because the new interface is a connector, not a screen.

Key Takeaways

• Headless Data 360 is a data-and-API layer for agents, not a new CRM and not a replacement for HubSpot, Plutio, or a form tool.

• The constraint that broke is the login: agents cannot click Lightning. They call APIs and MCP tools.

• Salesforce is shipping this on the open MCP standard Anthropic released in 2024, so Claude, Cursor, ChatGPT, and Agentforce can share one connector style.

• Governance did not go away. Agent IDs, Data 360 policies, and MuleSoft Agent Fabric are the control plane Salesforce is selling next to the APIs.

• Plug the connector into an existing form-to-CRM and review workflow rather than buying a second marketing stack.

What Headless Data 360 is

Headless Data 360 is Salesforce Data 360 exposed as a hosted MCP server, so an agent can build, transform, map, segment, and activate customer fields through more than 200 APIs without opening a Salesforce tab.

If you run a two-truck HVAC shop, a ten-person marketing agency, or a solo clinic, you probably do not live in Data 360. You still live the same problem: the customer record sits behind a screen that only a person can click. A receptionist pastes a web-form lead into the CRM. An account manager exports a CSV for a Friday report. An agency media buyer logs into Salesforce to pull a segment that should have been in the ad tool already. Headless Data 360 is Salesforce admitting that the next user of that record is often an agent, not a human at a console.

A 10-person shop comparing Plutio alternatives for marketing agencies already bounces between proposals, invoices, and a CRM. A team picking form-to-CRM automation tools already fights the copy-paste gap between a Typeform and a contact record. Headless Data 360 is the enterprise version of that gap closing: the API becomes the UI.

It is not a campaign builder. It is not a replacement for marketing agency automation tools. It is a way for whatever agent you already use to reach the same customer graph a Salesforce admin sees, under the same permissions.

What shipped in August, and what was already on the road

According to SiliconANGLE, Salesforce announced Headless Data 360 for Model Context Protocol on August 19, 2026, exposing more than 200 existing APIs as programmable endpoints agents can use without a user interface.

That August drop sits on an April foundation. Salesforce introduced Headless 360 on April 15, 2026, after co-founder Parker Harris asked, in a TDx keynote, why anyone should ever log into Salesforce again. The Headless 360 announcement said every capability would be an API, an MCP tool, or a CLI command.

According to TechTarget, Headless 360 avails more than 200 Salesforce APIs, Data 360 MCP server is generally available, and the Headless 360 MCP server plus Experience Layer are in open beta.

Salesforce's own Data 360 Headless page states that Data 360 Headless means the API is the UI, that it is built on MCP, and that MCP access is included with Enterprise Edition and above with no separate SKU.

MCP access ships with Enterprise Edition and above. That Salesforce Headless FAQ also says Data 360 MCP Server will use existing API limits, and that Flex Credits apply when you invoke Agentforce actions, run Data 360 queries, or use Prompt Builder.

Sources: Salesforce Headless 360 announcement; SiliconANGLE; TechTarget.

Why now: agents cannot click, so the CRM had to grow a socket

The constraint that broke is mechanical. Agents do not hover, click, or remember which list view you saved. They call tools. Salesforce spent 25 years putting work inside Lightning. The Headless 360 product page now describes Headless 360 as exposing those 25 years of capability as an API, MCP tool, or CLI command, with more than 60 MCP tools and 30+ coding skills in the April pack.

The socket they chose is not a Salesforce-only protocol. According to Anthropic, the Model Context Protocol was open-sourced on November 25, 2024 as a standard for connecting AI assistants to content repositories, business tools, and development environments.

The MCP documentation describes MCP as an open-source standard that lets Claude or ChatGPT connect to data sources, tools, and workflows. The MCP GitHub org lists 50.3k followers and a servers repository with 90,011 stars. Cursor's MCP docs describe three transports:

Source: Cursor MCP docs. "2+" here means Cursor's "Multiple users" remote-server row.

That ecosystem is why Salesforce can say Claude, Cursor, ChatGPT, and Agentforce can all hit Data 360. The connector is a public plug. The data, permissions, and Flex Credits remain Salesforce's.

Rohan Kumar, Salesforce's president and chief platform officer, told TechTarget that headless is making existing semantic models and analytics pipelines agent-readable rather than asking customers to rebuild them. The Data 360 product page still lists 200+ connectors, Zero-Copy links to Snowflake, Databricks, BigQuery, and AWS, and consumption-based pricing on credits, storage, and add-ons.

What an agent actually does with 200 APIs

SiliconANGLE's August piece walks through the job that used to take days: a person had to know fields, schema, segments, and tables before activating them. With Data 360 and the APIs in one place, a user can describe a need in natural language — lifetime value of electronics customers excluding software — and have the agent write the query, construct semantic models, and run it.

Conversational interfaces can build transforms, suggest field mappings, inspect data graphs down to individual records, and interrogate new CRM streams as they land. Salesforce says the Data 360 MCP Server is Salesforce-hosted and managed, with prepackaged Skills for modeling, mapping, transforms, and activation, and that custom Skills can wrap repeated workflows. Skills were slated for later in August.

On the Agentforce page, Salesforce says over 18K companies already run on Agentforce. That is the installed base Headless Data 360 is trying to reach from Cursor and Claude, not only from Lightning.

Identity is the other half. Salesforce is using an 18-character Agent ID that plugs into Data 360 governance. The developer doc shows the legacy builder exposing that ID in the setup URL, for example 0XxSB000000IPCr0AO. Kumar told TechTarget that many agents today run on an on-behalf-of user model, which gets dangerous as agents get more sophisticated. Headless without an Agent ID is just a wider hole in the CRM.

The rest of the Salesforce stack this sits on

Headless Data 360 is one layer. Salesforce's April announcement stacked four: Data 360 as system of context, Customer 360 as system of work, Agentforce as system of agency, and Slack as system of engagement.

The same April post said custom AI agents on Slack have grown 300% since January, that Natural Language DevOps can cut cycle times by as much as 40%, and that AgentExchange brings together 10,000 Salesforce apps, 2,600+ Slack apps, and 1,000+ Agentforce agents, tools, and MCP servers. Notion cut its average sales cycle from four months to three weeks after listing. Docusign processed 200+ private offers in Q4 2025 with 60% faster time to signature. A $50M Builders Fund sits next to that marketplace.

According to SiliconANGLE, one enterprise customer saw Agentforce adoption jump from 22% to 78% in six weeks after the experience changed, not the agent.

Agentforce adoption jumped from 22% to 78%. That SiliconANGLE April report is a single unnamed customer, not a platform average.

Slack's homepage states users can save 97 minutes weekly with AI in Slack and that 700 million messages are sent daily. Those are Slack figures, not Data 360 figures. They explain why Salesforce wants the agent in the channel instead of in a CRM tab.

Data quality is the other dependency. According to TechTarget, Salesforce closed an $8 billion Informatica acquisition and is folding Informatica's catalog and master data tools into Data 360 so Agentforce can see ERP and other non-Salesforce context. Tableau, acquired years earlier for nearly $16 billion, is the precedent TechTarget cites for keeping a specialist user community intact.

MuleSoft Agent Fabric, announced September 25, 2025, is the control plane for agent sprawl: a registry, a broker, governance on Flex Gateway for MCP and A2A, and a visualizer. The MuleSoft Agent Fabric page describes scanners that register agents and MCP servers across Amazon, Google, Microsoft, Claude, Databricks, and Kong, plus an Omni Gateway for spending caps and token routing.

Salesforce's own workforce research, a survey of 200 HR chiefs, projected 327% growth in agent adoption from 15% to 64% by 2027 and a 30% productivity gain. That is demand context, not a Headless Data 360 metric.

Sources: SiliconANGLE; Salesforce Headless 360; Agentforce; TechTarget Informatica; Slack; Salesforce workforce research; FedEx story.

USTA analysis: how much wider the data socket is than the April coding pack

USTA analysis, using only cited counts: the August Data 360 layer exposes more than 200 APIs, while the April Headless 360 coding pack listed more than 60 MCP tools. 200 / 60 = 3.33, so the data socket is more than 3.3 times the April tool count if you take both floors at face value. Inputs: 200 from SiliconANGLE and TechTarget; 60 from the April Salesforce announcement. These are overlapping but not identical inventories (APIs versus MCP tools). The multiple is a size comparison, not a claim that Salesforce added 140 new APIs in four months.

For a 10-person agency the analogue is simpler. You do not have 200 Salesforce APIs. You have a form, a CRM, and an ads tool. The August news is that the enterprise CRM is willing to speak MCP. Your job is to make sure the form-to-CRM path is clean enough that an agent would not hallucinate the field names you already fight over in spreadsheets.

What this changes for a marketing agency

Most agencies will not rip out the CRM this quarter. They will keep the system of record and ask whether an agent can read it.

Lead intake is the HVAC analogue. A two-truck shop photographs a work order. An agency captures a briefing form. If that form already lands in Salesforce through a mapped path, Headless Data 360 is a later connector on the same record. If the form still dies in a shared inbox, an MCP server will only automate the mess. Start with the live form-to-CRM pattern, then point an agent at the object, not at the inbox.

Segmentation is the second job. SiliconANGLE's electronics-LTV example is the same job as "clients who spent over X on paid social in Q2, excluding retainers." Today a media lead exports. Tomorrow an agent writes the segment if Data 360 actually holds the spend. If spend lives in Ads Manager, you still need a connector. Data 360 lists 200+ connectors on the product page; that is the inventory, not a promise your ad account is in it.

Activation is the third job. Salesforce talks about activating fields without leaving existing tools. For an agency that means the audience should appear in the ad platform or the email tool without a coordinator downloading a CSV. Teams already routing those hand-offs through US Tech Automations can treat Data 360 MCP as a later step on the same queue, not as a new campaign system.

Reporting is where Flex Credits will show up. MCP access is included; queries are not free at unlimited volume. Log the query, cap the agent, and keep a human on anything that goes to a client.

Dispatch-style work still needs a human calendar. An agency comparing dispatch software is really comparing who owns the appointment. Headless Data 360 can fetch the account. It should not silently book the shoot.

A shop already sending briefing PDFs into a US Tech Automations extraction workflow should keep the review step even if the next model call hits Salesforce over MCP. The workflow is the asset. The connector is a part.

FedEx is the large-customer proof, not the agency template. The FedEx Data 360 story says Data 360 lifted activation from 25% to 40% in five months and reports +2,000% ROI with Data 360. Copy the pattern (unify, trigger, follow up), not the petabyte architecture.

Executive-assistant load is the last SMB tell. If an AE still copies Salesforce fields into a deck, executive-assistant automation is the cheaper win while you wait for MCP access your edition actually includes.

Limits you should not round off

Headless 360 MCP server is in open beta. Data 360 MCP Server is GA. Do not brief a client that "Salesforce is headless now" without naming which server and which edition.

MCP included with Enterprise Edition is not the same as unlimited queries. Flex Credits still meter Agentforce actions, Data 360 queries, and Prompt Builder.

An agent that can discover APIs dynamically is the sprawl risk Kumar named. Agent Fabric, Agent IDs, and on-behalf-of permissions are the actual project. Connecting Cursor to production Salesforce without an allowlist is how you get a deleted campaign.

Salesforce marketing pages still use "world's #1" language for CDP. This hub does not repeat those claims as facts. The sourced figures above are the working set.

The state of small-business automation is the right zoom-out if your CRM is not Salesforce at all. Headless Data 360 only matters if the system of record is already Salesforce, or about to be.

Signal vs Speculation

Fact, sourced: Salesforce announced Headless Data 360 for MCP on August 19, 2026, with 200+ APIs, a GA Data 360 MCP Server, an open-beta Headless 360 MCP server, Enterprise Edition inclusion, and Flex Credits on queries. April Headless 360, Agentforce's 18K-customer claim, Informatica's $8 billion close, MuleSoft Agent Fabric, Slack usage, FedEx's Data 360 ROI, and the 200-CHRO survey are on the record above.

Fact, sourced: MCP is an open standard from Anthropic (November 25, 2024) with a public spec, SDKs, and a servers repo at 90,011 stars. Cursor documents three transports and OAuth.

Our read: if Data 360 MCP stays generally available and agencies get Enterprise-edition access without a new SKU, the 12–36 month pattern is connector-first CRM. Form tools, ad platforms, and agency operating systems will grow an MCP client the way they grew a Salesforce sync. The agencies that win will be the ones whose field dictionary is clean enough for an agent to map without a Slack thread.

Our read: if Flex Credits and API limits make exploratory queries expensive, Headless Data 360 stays an enterprise admin toy. Small teams will keep exporting CSVs. In that world, invest in form-to-CRM hygiene, not in a Salesforce MCP project.

Our read: agent sprawl is the operational risk. A 10-person shop with one Cursor install pointed at production is a worse outcome than a logged extraction queue. Put the connector behind the same review step you already use for client email.

How to act this month

Do not buy a new CRM. Inventory whether you are on Salesforce Enterprise or above, and whether the objects an agent would touch are already the system of record.

Pick one object: new leads from the briefing form, or a single client segment that currently requires an export.

Put that object on a path you control. A team already routing those records through US Tech Automations workflows will plug an MCP client in as a connector swap, not a rebuild, once the edition and credits are confirmed.

Label the agent on the output. If a segment was built by Claude over Data 360, say so in the client deck.

When you want that path on one board, use the Headless Data 360 workflow map on the US Tech Automations platform.

FAQs

What is Headless Data 360?

Headless Data 360 is Salesforce Data 360 exposed through a hosted MCP server so agents can use more than 200 APIs without a person logging into Salesforce. Salesforce announced it on August 19, 2026.

Is Headless Data 360 the same as Headless 360?

No. Headless 360 is the April 2026 platform program (APIs, MCP tools, CLI, Experience Layer). Headless Data 360 is the August Data 360 MCP server that focuses on query, transform, segment, and activate.

Do I need a separate Salesforce SKU?

Salesforce's Headless FAQ says MCP access is included with Enterprise Edition and above, with no separate SKU, and that the Data 360 MCP Server uses existing API limits. Flex Credits still apply to Agentforce actions, Data 360 queries, and Prompt Builder.

Can Claude or Cursor use it?

Salesforce and SiliconANGLE both list Claude, Cursor, ChatGPT, and Agentforce as clients that can discover and invoke Salesforce data over MCP. Your org still has to grant the server, the Agent ID, and the object permissions.

What should a 10-person agency change this quarter?

Clean the form-to-CRM path, stop exporting segments by hand for one client, and confirm your Salesforce edition before promising MCP to a client. You do not need 200 APIs to do those three things.

Does this replace HubSpot or agency operating tools?

No. It is a connector into Salesforce Data 360. If your system of record is not Salesforce, this announcement is a pattern to watch, not a product to buy.

Glossary

• Headless Data 360: Salesforce Data 360 delivered as an MCP server so agents can use 200+ APIs without a CRM login.

• Headless 360: Salesforce's April 2026 program to expose the platform as APIs, MCP tools, and CLI commands.

• MCP: Model Context Protocol, an open standard for connecting AI apps to tools and data, open-sourced by Anthropic on November 25, 2024.

• Data 360: Salesforce's real-time data engine, formerly Data Cloud, with Zero-Copy connectors and consumption pricing.

• Agentforce: Salesforce's AI agent platform; Salesforce says more than 18,000 companies run on it.

• Agent ID: An 18-character identifier for an Agentforce agent, used with Data 360 governance.

• Flex Credits: Salesforce consumption units that meter Agentforce actions, Data 360 queries, and Prompt Builder.

• MuleSoft Agent Fabric: A control plane to register, orchestrate, govern, and observe agents and MCP servers across vendors.

Headless Data 360 is a socket on the CRM, not a new agency OS. Small teams will not stand up Data 360 this month. They can copy the workflow: own the path from form to record to review, log which agent touched the segment, and keep a human on the client send. For the agent-side version of that path, open the agentic workflows board.