hey folks - platform engineer here at the international dev sector, and I’ve been exploring ways to democratize MCP across teams. We’ve got a bunch of structured data and APIs sitting with us, and the goal is to package that into an MCP format that’s reusable across workflows - especially for devs building out agentic or orchestration-based pipelines. currently working in a multi-cloud setup (but Azure-heavy), and I’m debating how to best distribute MCP: • Remote deployment (e.g. Web App) so they can hit it like a service, or • Local dev setup (code-based MCP repo) they can pull and run locally, then connect to from their agent. Curious what’s worked for others? Open to thoughts on dev experience, scaling, and how much infra abstraction is “just enough.”

Running locally sounds like a secret-sprawl nightmare, no?

Could you not package it up into an artifact repository so people can pull the package? If it is azure based you could have it authenticate to an entra app managed by conditional access policies so it can only be called from agreed networks?