MCP does not replace infrastructure. MCP replaces the interface to infrastructure.
We are seeing the same pattern with API integration testing. Once agents start wiring real systems, endpoint docs are not enough. They need a runnable execution layer: discover the workflow, run the calls, inspect state transitions, observe webhooks, and then decide what code to change.
That is the direction we are taking with FetchSandbox MCP: give coding agents a stateful API sandbox they can execute against before they edit app code.
The interesting shift is that the API stops being just documentation + endpoints. It becomes something the agent can reason through.
Great observation. I think that's exactly where infrastructure is heading. The interface becomes executable instead of descriptive. Instead of reading endpoint documentation, agents discover capabilities, plan execution, execute against real infrastructure and observe outcomes as part of the same reasoning loop. Different domains, same architectural shift.
Really like this framing:
We are seeing the same pattern with API integration testing. Once agents start wiring real systems, endpoint docs are not enough. They need a runnable execution layer: discover the workflow, run the calls, inspect state transitions, observe webhooks, and then decide what code to change.
That is the direction we are taking with FetchSandbox MCP: give coding agents a stateful API sandbox they can execute against before they edit app code.
The interesting shift is that the API stops being just documentation + endpoints. It becomes something the agent can reason through.
Related: https://fetchsandbox.com/mcp