How to Publish an AI-Built Website With an MCP (No Git, No Terminal)

A static site is a folder: index.html at the root, any other pages beside it, and CSS, JavaScript, images and fonts in subfolders referenced by relative paths. Ask the AI that built the site to write it that way, or to zip that folder — Hostinger's deploy takes an archive, Vercel's takes the files themselves, and Netlify publishes the folder the client is working in. Anything that needs a build step (a React app, a framework) still works on Vercel, which detects the framework and builds; the other two paths want the finished output.

Put the whole site in a folder called "site": index.html at
the root, styles in site/css, scripts in site/js, images in
site/img, all linked with relative paths. Then zip it to
site.zip and tell me where both are.

Files and no account anywhere in particular: the Vercel MCP's create_deployment accepts the files in its request body, creates the project, detects the framework and builds; the first deployment is a preview URL you can share while it finishes. A Hostinger hosting plan: hosting_deploy-static-website (found with search, run with execute) uploads a static site from an archive with no build step, and hosting_deploy-js-application builds a JavaScript app from a source archive. A Netlify account and the folder on the machine your client runs on: the deploy-site operation in Netlify's deploy-services updater publishes it. A Claude Design bundle: Vercel's import-claude-design-from-url takes the public HTTPS URL directly.

Vercel is a hosted server: add https://mcp.vercel.com to your client and approve one team. Its first deployment is a preview by default; production needs target: "production", which is the call to keep behind your confirmation. Hostinger and Netlify have no preview inside the tool: a deploy is the live site, and Hostinger's own operation text warns that it overwrites the website's existing contents and cannot be undone. Netlify's deploy-site publishes to the live project the same way. Treat both as production writes, and confirm before each.

Deploy the "site" folder to Vercel as a preview deployment
in my team "acme". Create the project "acme-site" if it
does not exist. Give me the preview URL and the build log
once it finishes. Do not deploy to production.

On Vercel the agent can read the deployment state with get_deployment, follow the build output with list_deployment_events, and fetch the page itself with web_fetch_vercel_url — including a protected preview. On Hostinger and Netlify, open the URL the deploy returned and ask the agent to fetch it with any web-fetch tool. Check the home page, one inner page, and one image path; a broken relative path is the most common first-deploy bug.

Fetch the preview URL and confirm the home page renders,
the link to /about works, and /img/hero.png returns an
image. Report anything that 404s with the exact path.

When the preview is right, ask for the production deployment (Vercel) or accept that the deploy you just made is live (Hostinger, Netlify). Then give the site its name: on Vercel, add_project_domain attaches it and the DNS half follows the connect-a-custom-domain tutorial; on Hostinger the same server writes the zone. Every later change is a new deploy of the whole folder, so keep the source folder — there is no "edit one file on the server" in this workflow.

The preview looks right. Deploy the same files to
production, then add the domain www.example.com to the
project and tell me which DNS record it expects.