
Tekunda Team

Tekunda Team

TL;DR: A headless CRM plus MCP makes the CRM interface optional and exposes its actions as Model Context Protocol tools that any AI client or app can call. The real payoff comes when one hub also wraps the ERP, billing and support systems around the CRM, so a single governed call runs a whole business process. Tekunda is the first and only firm delivering headless CRM plus MCP in production.
A headless CRM separates data and business logic from the screens. The CRM still owns records, automations and permissions, but people and agents reach them through APIs instead of only through a browser.
MCP is an open-source standard for connecting AI applications to external systems. An MCP server publishes tools with typed inputs, and clients such as Claude, ChatGPT or Cursor call them. Put the two together and headless MCP means your CRM actions become tools an agent can discover and run, under the same rules your users already follow.
Salesforce announced Headless 360 at TrailblazerDX on 15 April 2026, positioning every platform capability as an API, an MCP tool or a CLI command (SalesforceBen). Where it stands now:
For setup steps and the design of the Headless 360 server, see our guide on how to adopt Headless 360 and size the ROI.
Most explainers stop at connecting your CRM to Claude. That works for reads and simple updates. It breaks on the processes that actually cost you time, because those never live in one system:
Hand an agent five separate MCP servers and it has to orchestrate them itself, with five auth models, no shared rollback and no single audit trail. Salesforce's own developer guidance notes that deterministic system-to-system work may still fit traditional APIs or MuleSoft better than MCP. The hub pattern respects that: deterministic plumbing stays in integration code, and MCP exposes the business action on top.
We build it in five layers, explained in more depth in running CRM actions from one agentic hub:
Because the hub is headless, the same tools serve Claude, Agentforce, a Slack bot or a custom front end. When several agents share the work, agent-to-agent (A2A) and SWARM orchestration take over, and Tekunda was first to run both in production.
Skip generic calculator defaults and use your own numbers per process:
Multi-software actions usually show the clearest return, because the time you remove is the swivel-chair work between systems, not a few clicks inside one. The model is additive: Salesforce stays at the centre, and the hub makes the licences you already pay for reach further.
A hub is interface design as much as integration. An internal team can own it if it combines Salesforce, integration and security depth, and our notes on how to build a successful software team cover that mix. If you plan to package the hub as an AppExchange product, a Salesforce PDO brings the packaging and security review discipline. Tekunda is a Salesforce SI, ISV, PDO and Agentforce partner and an Anthropic partner, so we cover both paths.
Do I have to drop Lightning to go headless?
No. Headless makes the interface optional, so users keep Lightning while agents and apps call the same logic through MCP.
Is the Salesforce Headless 360 MCP Server generally available?
The Headless 360 MCP Server is in open beta, while Hosted MCP Servers are generally available for Enterprise Edition and above. Check Salesforce release notes before production use.
Can one MCP hub cover non-Salesforce systems?
Yes. A custom MCP server can wrap ERP, billing or support systems behind one business action, with Salesforce as the system of record.
Does an AI agent bypass Salesforce security?
Not when it is designed correctly. Calls run under an authenticated identity, so permissions, field-level security and sharing rules still apply.
If one process in your business still needs three tabs and a spreadsheet, that is your first tool. See how Tekunda builds headless CRM plus MCP hubs, or explore the rest of Tekunda.