Do we need Agent Fabric for one Agentforce agent?

Not yet. It pays off when several agents share ERP or CRM access and you need one policy and one audit log.

How does this relate to MCP and A2A?

Agent Fabric is the control plane. MCP is how an agent reaches a system. A2A is how agents reach each other. Flex Gateway is where those calls are identified and logged.

MuleSoft Agent Fabric

See and govern every agent that touches Salesforce.

Agent Fabric inventories agents, MCP, and policies. Flex Gateway is still the front door.

Get the written assessment Dreamforce session

Founded 2022 · Founder in the Salesforce MVP Hall of Fame · Dubai HQ · Kochi studio

Control plane

See every agent. Enforce policy. Keep the trail.

If you cannot name the agents, you do not have a fabric. You have a demo.

Who this is for

Three estates where nobody could list the agents.

Agent Fabric pays off when several agents share CRM or ERP access. One agent and a pipe do not need it.

Example
CIO at a Dubai conglomerate
Today: Service, sales and finance each built an agent that writes to Salesforce, with three different keys.
After: One register of agents, tools and policies, and one audit log per caller.
Example
Head of IT risk at a Riyadh bank
Today: Audit asked which agents can read customer data, and the answer took weeks of emails.
After: Every agent and MCP server is listed with its policy family, so the answer is a report.
Example
Platform owner at a Chicago insurer
Today: Model spend rose and nobody could say which team spent it.
After: Token and tool usage tagged per caller on the same trail as the traces.

Examples of the work, not case studies. Roles and cities are typical of the desks we see.

The split

Fabric is the plane. Flex Gateway is the edge.

01
Fabric
Who exists, what they may call, which policy family applies.
02
Gateway
Enforce it. On-behalf-of, MCP hosting, LLM proxy, semantic checks.
03
Tools and models
Hosted and proxied. Not a shared key in the agent prompt.
04
Record
Salesforce, ERP, files. Fabric does not become the warehouse.

Agent Fabric inventories and policies. Flex Gateway enforces. MCP and model calls still go through the gateway. The store of record stays the store of record.

Mermaid source

flowchart TD
  A["Agent Fabric: inventory and policy"] --> B["Flex Gateway: identity, rate limits, LLM proxy"]
  B --> C["MCP tools"]
  B --> D["Model calls"]
  C --> E["Systems of record"]

Questions

What we actually say.

Do we need Agent Fabric for one Agentforce agent?: Not yet. It pays off when several agents share ERP or CRM access and you need one policy and one audit log.
How does this relate to MCP and A2A?: Agent Fabric is the control plane. MCP is how an agent reaches a system. A2A is how agents reach each other. Flex Gateway is where those calls are identified and logged.

The brief · one email

Name the agents that already touch Salesforce.

We will tell you whether Fabric is the plane, or whether you still have one agent and a pipe. The assessment is free: a short read of the org and a written note. If you go ahead, the first build week is a fixed AED/SAR 14,900 (about USD 4,050), credited in full when you sign the build within 60 days. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.