Speaking twice at Dreamforce · Sept 15-17 →
MindcatConsulting, home
Find your week

Salesforce MVP Hall of Fame · Certified Partner since 2010

Reuse when it is real. A pipe when it is not.

The first week is in the org, reading what already exists. Anypoint for APIs you will call twice. Flex Gateway when agents and MCP need a front door. IDP when the work arrives as a document. 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

Agent architecture

Practice

The MuleSoft work we actually take.

Anypoint, IDP, the gateway, the fabric, and how we sequence delivery. We will tell you when a simpler pipe would do the job.

The failure

Custom glue works. It does not govern.

Hand-written mappings, identity in app code, and no trail per caller. That is the usual estate we inherit.

The split

Replace, front, or keep.

MuleSoft is not the store of record. We will not pretend it is.

  1. 01

    Replace the glue

    Callouts, DataWeave mappings, queues, gateway identity, MCP hosting, and semantic policy. This is the near-term win.

  2. 02

    Front the planes

    Connectors can query a graph, a warehouse, or object storage. The backbone stays. Fronting is not owning.

  3. 03

    Keep what already works

    Durable long jobs, existing workflow engines, and stores with no MuleSoft equivalent stay until a later cutover.

Three honest jobs for MuleSoft. Replace the glue. Front the stores you do not own. Leave long-running orchestration where it already runs until a cutover is earned.
Mermaid source
flowchart TD
  A["Sources and Salesforce"] --> B["MuleSoft: ingest, canonical model, gateway"]
  B --> C["Replace: glue, identity, MCP hosting"]
  B --> D["Front: graph, warehouse, files"]
  B --> E["Keep: long jobs that already run elsewhere"]
  C --> F["Systems of record"]
  D --> F
  E --> F

The fabric

Four pieces carry most of the work.

Where the fabric runs, how payloads are shaped, how spikes are absorbed, and how model calls are metered. Two of these are control-plane jobs and two are durable-plane jobs.

Patterns

The same pipes in more than one industry.

Intake, matching, and governed write-back are reusable shapes: documents, HR and ops, retrieval, and exceptions.

Questions

What we actually say.

Is every integration a MuleSoft project?
No. Point-to-point is honest when there is one pipe. Anypoint when you will reuse the asset. Flex Gateway when agents, MCP, or OAuth need a front door. We will say which.
How does this sit next to MCP?
MCP is how an agent reaches a tool. MuleSoft is how that tool is hosted, identified, rate-limited, and audited. Different jobs. See the MCP note if the caller is an agent.
Do you move the warehouse into MuleSoft?
No. We front it. The store of record stays the store of record.

Next

What to read next.

The brief · one email

Name the systems. Name the failure.

We will tell you MuleSoft, a simpler pipe, or neither.