2 min

When MCP adoption outpaces IT

When MCP adoption outpaces IT, governance becomes a leadership issue fast.

Transcript

Yeah. Jw Pepper, we're a very large, sheet music retailer. We we are interested in any technical improvements. We've actually been on the bleeding edge of a lot of technology, which has kept us, sort of relevant in the industry. We're very much focused on using AI for operational efficiency improvements, and we've seen a lot of improvements internally. I think the demands of our employees and even our customers have adjusted to that of the AI landscape.

And what we found honestly was that people outside of the IT department, perhaps with a little bit less governance, were moving faster than we were within IT actually creating these useful AI agents and that IT effectively had to become a service again for this use case. So, you know, some technical folks in various departments that previously would have asked me, Do you this service that you have as an API, can we integrate it? Is now turning into this service has MCP. And I think at first I found it terrifying that anybody was even talking to me about MCP. My role is I'm I'm the director of systems architecture, which means I'm sort of trying to set technical standards for the company and how we move forward. And and I needed to figure out what was going on with this with this MCP and the AgenTik AI world.

And also, of course, add governance standardization. Just like you wouldn't want other people in the company to integrate their own APIs, you don't really want them to integrate their own MCPs either. At least you want some governance around that.

More like this