PRODUCTION SCENARIO
A platform team owns the service that grants, revokes and audits footage licensing rights for a broadcaster archive. Six product teams want their Claude applications to use it, the operation set changes most months, and only two of those teams may revoke a license.
How should the platform team expose the capability?
Answering here is anonymous. Nothing is saved unless you sign in.
Show answer and explanation
Answer: Run one MCP server exposing the operations as versioned tools, with scopes enforced server-side.
One MCP server gives all six applications the same tools, with names, descriptions and schemas as the versioned contract, and it is the single place the revoke scope is enforced, since the tool set a server returns may vary by the authorization on the request. A published OpenAPI spec leaves six generated toolsets to drift and six scope checks to write. Monthly change notices make six teams repeat the same migration. And a natural-language front door offers no schema contract and no reliable place to enforce who may revoke.