Publish static site preview for 48 hours
A public HTTPS link to a temporary static site preview is generated, valid for 48 hours, allowing stakeholders to review HTML/CSS/JS content without permanent hosting.
How it works
The agent first calls get_deploy_instructions to understand the process and terms. It then prompts the user to review the public exposure risks and explicitly accept the terms via the provided approval_url. Once consent is confirmed, the agent calls create_preview with the local directory path and acceptance flag. It polls get_preview_status until the operation is complete, then returns the final viewer URL and expiration time to the user. The agent must verify the status is 'complete' before sharing the URL.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Please publish my static site in the 'dist' folder as a temporary preview. First, show me the deployment instructions and terms. I will review them and provide explicit consent. After I confirm, create the preview, wait for it to be ready, and give me the public URL.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
A ready HTML/CSS/JS directory becomes a public HTTPS review link.AIfra MCP: publish a prebuilt static site for 48 hours · AIfra