folder_deploy
Deploy a local folder of static files (HTML/CSS/JS/images etc.) to ESA Function & Pages and return a default access URL. The folder will be packaged as assets and uploaded.
Get a page online from inside the conversation: hand over HTML or a local folder of static files and receive a working URL on ESA Function & Pages.
LABSCO SUMMARY
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. In the Pages module everything after the deploy is elsewhere — no listing of what you have already put up, no update in place, no delete; listing, updating and deleting live in the Edge Routine and Site modules, for routines, routes and DNS records rather than Pages deployments.
Alibaba Cloud's ESA server, split into modules you pick by binary: mcp-server-esa-pages holds the two deploy tools — one takes an HTML string, the other packages a local folder as assets — while the README lists 16 Edge Routine tools and 26 Site tools behind mcp-server-esa-er and mcp-server-esa-site, and mcp-server-esa loads all three.
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 -y -p mcp-server-esa mcp-server-esa-pages, then supply credentials
USE CASES
Hand the HTML straight over with a name and get the access URL back, so what was a code block in the conversation becomes a link the person who asked for it can open.
Point the deploy at the output directory and the whole folder — HTML, CSS, JS and images — is packaged as assets and uploaded in one call, with a description recorded alongside it.
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
folder_deployDeploy a local folder of static files (HTML/CSS/JS/images etc.) to ESA Function & Pages and return a default access URL. The folder will be packaged as assets and uploaded.
html_deployQuickly deploy an HTML page to ESA Function & Pages and return a default access URL to the user.
BEFORE YOU INSTALL
2 tools when we connected; the project documents 44. The package ships four binaries: mcp-server-esa-pages gives 2 tools, mcp-server-esa-er 16, mcp-server-esa-site 26, and mcp-server-esa loads all of them. Change the binary in args to change the set.
All 8 documented setups run the server on your machine.
INSTALLATION
npx -y -p mcp-server-esa mcp-server-esa-pages{
"mcpServers": {
"esa-pages": {
"command": "npx",
"args": [
"-y",
"-p",
"mcp-server-esa",
"mcp-server-esa-pages"
],
"env": {
"ALIBABA_CLOUD_ACCESS_KEY_ID": "<YOUR_ALIBABA_CLOUD_ACCESS_KEY_ID>",
"ALIBABA_CLOUD_ACCESS_KEY_SECRET": "<YOUR_ALIBABA_CLOUD_ACCESS_KEY_SECRET>"
}
}
}
}{
"mcpServers": {
"esa-mcp-server": {
"command": "npx",
"args": [
"-y",
"mcp-server-esa"
],
"env": {
"ALIBABA_CLOUD_ACCESS_KEY_ID": "<YOUR_ALIBABA_CLOUD_ACCESS_KEY_ID>",
"ALIBABA_CLOUD_ACCESS_KEY_SECRET": "<YOUR_ALIBABA_CLOUD_ACCESS_KEY_SECRET>"
}
}
}
}If you authenticate with an STS token, also add ALIBABA_CLOUD_SECURITY_TOKEN to env with that token; the project marks it optional and needed only for STS.
{
"mcpServers": {
"esa-er": {
"command": "npx",
"args": [
"-y",
"-p",
"mcp-server-esa",
"mcp-server-esa-er"
],
"env": {
"ALIBABA_CLOUD_ACCESS_KEY_ID": "<YOUR_ALIBABA_CLOUD_ACCESS_KEY_ID>",
"ALIBABA_CLOUD_ACCESS_KEY_SECRET": "<YOUR_ALIBABA_CLOUD_ACCESS_KEY_SECRET>"
}
}
}
}{
"mcpServers": {
"esa-site": {
"command": "npx",
"args": [
"-y",
"-p",
"mcp-server-esa",
"mcp-server-esa-site"
],
"env": {
"ALIBABA_CLOUD_ACCESS_KEY_ID": "<YOUR_ALIBABA_CLOUD_ACCESS_KEY_ID>",
"ALIBABA_CLOUD_ACCESS_KEY_SECRET": "<YOUR_ALIBABA_CLOUD_ACCESS_KEY_SECRET>"
}
}
}
}