# How J.W. Pepper uses Tray.io

As published on [tray.ai](https://tray.ai/customers/jw-pepper/), January 2026. Captured by usedby on 2026-10-16.

- Company: [J.W. Pepper](https://www.usedby.ai/companies/j-w-pepper.md)
- Tool: [Tray.io](https://www.usedby.ai/tools/tray-io.md)
- Teams: IT

## What the story says

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.

> 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

Source: [tray.ai](https://tray.ai/customers/jw-pepper/), captured 2026-10-16.

## What usedby checked

We compared the story with its live page on 2026-10-16.

- Checked: the passage quoted above is copied word for word from the page, near the name of J.W. Pepper.
- Checked: the publication date is read from the page’s own metadata, never guessed.
- Checked: J.W. Pepper uses Tray.io. Confirmed line. Latest check across sources: 2026-10-16.
- Not checked: the result itself. We quote it; we did not measure it.

---
Source: https://www.usedby.ai/case-studies/j-w-pepper-tray-io · How we check: https://www.usedby.ai/methodology