Fourteen product teams are each building agents that need to look up customer entitlements from the same licensing system. Three teams have already written their own integrations, with different schemas and authentication approaches, and a licensing API change last month broke two of them. Which integration approach is most appropriate going forward?

Answer: D — Publish one MCP server for entitlements, owned by the licensing team, over HTTP with per-caller authorization

A capability shared by many clients and owned by one team fits a single MCP server that the owner maintains, versions and secures; an HTTP transport with real auth suits a shared network service. (a) keeps duplicated integrations that drift and break. (c) turns a deterministic lookup into a non-deterministic agent with extra cost. (b) gives every team its own copy to keep updated and skips the shared auth model a central service needs.