Put MCP at the edge; keep the agent runtime talking to boring, durable APIs.

Put MCP at the edge; keep the agent runtime talking to boring, durable APIs. Treat MCP as an adapter for tools and IDEs that need flexible discovery and structured I/O, not as the source of truth for execution, auth, retries, queues, or audit. Run MCP servers as a UI layer that invokes well-defined internal services. If you run on Azure or AWS, a practical step is to add a provider-agnostic internal tool contract behind the MCP facade so you can swap cloud harnesses without rebuilding core guarantees.