Skip to main content
usedby

As published on tray.ai, January 2026. Checked by usedby on Oct 16, 2026.

What happened

J.W. Pepper's IT team centralized its MCP servers and tools in Tray Agent Gateway for MCP, controlling which tools are exposed to AI agents and under what conditions. They built small, purpose-built workflows for specific business actions and made them available to employees through Microsoft Copilot.

Summary written by usedby from the source page, in English. The figures are those of Tray.io and J.W. Pepper, not ours.

To support this shift, J.W. Pepper centralized its MCP servers and tools using Tray Agent Gateway for MCP. This allowed IT to control which tools were available, how they were exposed, and under what conditions they could be used.

From the page. tray.ai

As I've begun transitioning our use of Tray into MCP, I'm finding our workflows are becoming almost like microservices. Instead of us trying to build this whole robust all-in-one iPaaS solution, we're just adding these little drops of determinism into what the agent can do.

Marcus Dubreuil, Director of Systems Architecture, J.W. Pepper. Source

What the story claims, and what we checked

What we compared with the page.

  • The passage quoted aboveCheckedCopied word for word from the page, near the name of J.W. Pepper.
  • The publication dateCheckedRead from the page’s own metadata, never guessed.
  • J.W. Pepper uses Tray.ioCheckedConfirmed line.
  • The result itselfNot checkedWe quote it; we did not measure it.

Same company, same tool or same industry.

Weeks, not monthsTo overhaul Salesforce securityAbridge uses Tray.io. Another customer of Tray.io23 hours“What previously took 23 hours now takes under five minutes.”Zuora uses Tray.io. Another customer of Tray.io2,500+“Slack lifecycle automation across 2,500+ channels makes it safe to allow user-requested creation”Life360 uses Tray.io. Another customer of Tray.io