Your coding agent can deploy it too
Add cloud71 to Claude Code, Cursor, or VS Code as an MCP server. When the build is done, ask the agent to deploy it — the site goes live on a global edge and the URL comes back in the same session.
https://mcp.cloud71.host/mcpyou › Deploy the dist folder to cloud71 as acme-launch.
Claude Code › calling deploy_files…
✓ live at https://acme-launch.cloud71.site
Coding agents can scaffold, build, and test a static site in one sitting. Then deploying turns into another chore: a hosting account, a config file, a tool to install. cloud71 gives the agent a deploy tool instead. It calls deploy_files with your build output and gets back a live https URL — nothing new to add to the project.
It's made for static output: hand-written HTML, a Vite or Astro build, a docs site, a prototype. Give the site a name and every redeploy updates the same URL while you iterate. The agent can also read the live files back, list your sites, or attach a custom domain. For CI and scripts, the same account works over the REST API with a token and one curl command.
Try saying
- “Deploy the dist folder to cloud71 as acme-launch.”
- “Read my site ‘docs’, fix the broken nav link, and redeploy.”
- “List my cloud71 sites.”
- 1
Add the MCP server
Claude Code: run the command below. Cursor and VS Code: add the URL to your mcp.json.
- 2
Sign in once
Your browser opens to log in to cloud71 and approve access. No keys to paste into the project.
- 3
Build, then deploy
Say “Deploy the dist folder to cloud71 as acme-launch.” The agent uploads the files and replies with the live URL.
Claude Code
claude mcp add --transport http cloud71 https://mcp.cloud71.host/mcpCursor · .cursor/mcp.json
{
"mcpServers": {
"cloud71": { "url": "https://mcp.cloud71.host/mcp" }
}
}VS Code · .vscode/mcp.json
{
"servers": {
"cloud71": { "type": "http", "url": "https://mcp.cloud71.host/mcp" }
}
}Everything the link needs
No deploy config
No build settings, environment variables, or pipeline. The agent sends the files you already built.
Stable URLs
Deploy to a named site and every redeploy updates the same URL. The last 5 versions are kept for rollback.
Read, edit, redeploy
read_site returns the live files, so the agent can patch one page and republish.
Custom domains from the chat
manage_site attaches your domain and returns the DNS records to add (Starter and up).
Scoped access
OAuth sign-in limited to deploying and managing your sites. Revoke it anytime.
Works in CI too
Use a token and curl against the REST API from scripts and pipelines.
Common questions
Run claude mcp add --transport http cloud71 https://mcp.cloud71.host/mcp, sign in when the browser opens, then ask Claude Code to deploy your build folder to cloud71. It replies with the live URL.
Add cloud71 to your Cursor mcp.json — {"mcpServers":{"cloud71":{"url":"https://mcp.cloud71.host/mcp"}}} — sign in when prompted, and ask the agent to deploy the folder.
Yes. Add {"servers":{"cloud71":{"type":"http","url":"https://mcp.cloud71.host/mcp"}}} to .vscode/mcp.json, sign in, and ask the agent to deploy. Cline and Goose connect to the same URL.
MCP (Model Context Protocol) is an open standard for giving AI tools access to services. cloud71's MCP server exposes four tools — deploy_files, list_sites, read_site, and manage_site — so any MCP client can deploy without a custom integration.
Static output: HTML, CSS, JavaScript, images, fonts, and files. Single-page apps and static-site-generator builds work. There's no server runtime — no Node server, PHP, or database — so call an external API for dynamic data.
Yes. Create a token at app.cloud71.host/dashboard/tokens and POST a ZIP of your build to the REST API. The API docs have a copy-paste curl example.
No. The agent uses the MCP server, and scripts use curl against the REST API. There's nothing to add to your project.
Yes, when you name the site (“as acme-launch”). Each deploy replaces that site's content, and the free plan can redeploy its one site as often as you like.