Summary
A generated page becomes a link without a repository, a commit or a pipeline.
Both tools end at a URL, which is the whole point of them: deploy_html for markup that was produced a moment ago in the conversation, deploy_folder_or_zip for output a build already wrote to disk, returning project metadata with the link. It is the shortest distance between a page existing and somebody else being able to open it.
What it is
A two-tool deployment path to EdgeOne Pages: one call for a string of HTML, one for a built frontend directory or a zip.
What you get
- deploy_html takes HTML content and returns the public URL it now lives at
- deploy_folder_or_zip takes the path to a built frontend directory or a zip file and returns the deployment URL with the project metadata alongside it
Requirements
The content itself: markup as a string for deploy_html, or a path to an already-built directory or zip for deploy_folder_or_zip. MIT-licensed.
Setup effort
One command — npx @edgeone/makers-mcp@latest