How J.W. Pepper centralizes and secures their MCP servers and tools early

In this customer case study, J.W. Pepper shares how its IT team put guardrails around MCP servers and tools as adoption grew across the business.

At J.W. Pepper, MCP demand grew faster than IT could keep up. MCP servers and tools started spreading across the business, creating leadership-level issues like unclear ownership, uneven access controls, and no single way to manage what was live.

In this customer case study, Marcus Dubreuil, Director of Systems Architecture at J.W. Pepper shares how his team put guardrails in place early by centralizing MCP servers and tools in one managed environment using Tray Agent Gateway.

What you’ll learn

What sprawl looks like early: The signs J.W. Pepper saw when MCP started spreading
Clear ownership: Who runs MCP servers, who ships tools, and who approves changes
The guardrails they set: The access rules and change control they’re putting in place now