Shivanath Devinarayanan · Updated
On this page
The network is the fleet: Agentforce agents, brokers, MCP tool servers, and the surfaces that call them, registered and routed as one. MuleSoft Agent Fabric is the public product name for that control plane. The work here is how you register and route the fleet.
Fragmentation: separate keys, logs, and bills. No unified audit trail. A one-person bottleneck: every new agent is bespoke. Cost blindness: tokens with no per-run budget.
The answer is one gateway, one registry, policies that make the next agent copyable, and telemetry in one place. The Agentforce hub is Agentforce that stays in production . I run this model across 200+ production agents.
In this network
Registry
Name every agent, broker, and MCP server. Identity, allowed actions, named owner, and the trail each one leaves.
Orchestration
Guided determinism. Executors, generators, subagents, and orchestrators. Pick how much LLM the path is allowed.
Agent-to-agent
Wrap Agentforce as a peer. Tasks, session reuse, context and task IDs. Do not advertise streaming or history the wrapper lacks.
Tools
MCP servers sit behind the gateway. Client ID, access control, tool mapping, spike control, logging.
Surfaces
Slack, email, web, scheduled. The surface changes. Identity, policy, and trail do not.
How to hire
Hiring starts with a governed production agent on one documented job, then a consultation.
Start at First Agent in Production , then book a consultation .
SHIVANATH DEVINARAYANAN · SALESFORCE MVP HALL OF FAME ·
SD
SHIVANATH DEVINARAYANAN · SALESFORCE MVP HALL OF FAME ·
SD
Stand up the first production agent
Hiring starts with a governed production agent on one documented job, then a consultation.
Home · About · Services · Portfolio · Success Stories · Writing · News · Events · Contact · Tools I use · Media kit · Privacy Policy