Speaking twice at Dreamforce · Sept 15-17 →

MuleSoft Agent Fabric

See and govern every agent that touches Salesforce.

The first week is in the org, reading what already exists. Agent Fabric inventories agents, MCP, and policies. Flex Gateway is still the front door. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.

Get the written assessment

Certified Partner since 2010 · MVP Hall of Fame · 200+ agents in production · UAE and US desks

Dreamforce session

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.

The split

Fabric is the plane. Flex Gateway is the edge.

  1. 01

    Fabric

    Who exists, what they may call, which policy family applies.

  2. 02

    Gateway

    Enforce it. On-behalf-of, MCP hosting, LLM proxy, semantic checks.

  3. 03

    Tools and models

    Hosted and proxied. Not a shared key in the agent prompt.

  4. 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.