If you serve many environments you don’t get to bet on what protocol wins. You serve the way each consumer can actually consume
This is why deBridge has MCP, CLI, SDK, RestAPI, OAS, swagger, curl snippets, docs, skills - because our consumers aren’t the same person.