Both tools end at a URL, which is exactly what the throwaway case needs — a preview, a generated report, a one-page demo that has to be looked at by someone who is not you. Everything after the deploy is elsewhere: no listing of what you have already put up, no update in place, no delete.
A two-tool deploy server for Alibaba Cloud ESA Function & Pages — one call takes an HTML string, the other packages a local folder as assets.
- An HTML page deployed under a name you choose, with its access URL returned
- A local folder of static files — HTML, CSS, JS, images — packaged as assets and uploaded in one call
- A description recorded alongside a folder deployment
ALIBABA_CLOUD_ACCESS_KEY_ID and ALIBABA_CLOUD_ACCESS_KEY_SECRET, for an account that can reach ESA Function & Pages.
One command plus a key — npx -p mcp-server-esa <binary>, then supply credentials
