{"slug": "how-to-publish-a-site-built-with-claude-code-without-setting-up-a-server", "title": "How to publish a site built with Claude Code without setting up a server", "summary": "A developer writing as Ciro Cesar Maciel has released Hoster, an MCP server that lets Claude Code publish a static site build to HTTPS hosting with a single command, without configuring a server, certificates or a remote build pipeline. Claude Code connects to the remote MCP server via a browser sign-in, receives a short-lived deploy ticket, and then runs a local CLI command to push the dist folder; the site is served at a subdomain with HTTPS from the first request, and rollbacks switch between the last five versions without re-uploading. The tool is limited to static output and does not support API routes, server-side rendering, Git push-to-deploy or per-branch previews.", "body_md": "Claude Code built the site, it runs on `localhost`, and now you want to send the link to someone. Most tutorials jump to servers, certificates, connecting GitHub to a dashboard and configuring a remote build. For a site Claude Code generated, you need almost none of that: after the build it is a folder of finished files, and that folder only needs a place that serves it over HTTPS.\n\nThis is the path with Hoster, from the Infrastructure line (by Ciro Cesar Maciel, who writes this): an MCP server Claude Code connects to with a browser sign-in, and one command that uploads the build.\n\nAlmost always. A Vite, React, Astro or plain HTML project ends up, after the build, as a `dist` or `build` folder with HTML, CSS, JavaScript and images. Hoster publishes exactly that folder. It does not run your build: Claude Code does that locally (`npm run build`, `bun run build`, whatever `package.json` says).\n\nIf the project has API routes, server-side rendering or functions that run on every request, that part is not static, and Hoster is not for it.\n\n```\nclaude mcp add --transport http hoster https://hoster.worker.myinfrastructure.click/mcp\n```\n\nNo key in the command, no secret in a config file. The first call answers 401, Claude Code discovers the authorization server, opens the browser, and you sign in with a code sent to your e-mail. The server address is the same for the whole account; there is no project id in it. `/mcp` inside Claude Code shows whether `hoster` is connected.\n\nSay it in words: \"build and publish the dist folder to Hoster as project my-site\". Behind that:\n\n`my-site` if it does not exist. The project name is the subdomain.`hoster_deploy_ticket`, and Hoster returns a ready command: `bunx @ciromaciel/hoster-cli push ht_… --dir ./dist`.\nThe ticket is good for one project, one use and 15 minutes. If an upload fails halfway, run the same command again.\n\nWhy two parts? The MCP server is remote and cannot reach your disk, so it authorizes and the local command sends the bytes.\n\nThe site answers at `https://my-site.myhoster.click`, with HTTPS from the first second: there is no certificate to wait for.\n\nTo update, ask again. Every deploy is a new version at the same address. If the new one broke something, ask to roll back: Hoster switches the active version without re-uploading, and keeps the last 5 by default.\n\nA custom domain is one CNAME to `proxy.hoster.myinfrastructure.click`, and Hoster issues its certificate too.\n\n`404.html` at the root of the build turns that fallback off.`window.ENV`.\nNo server-side build, no functions or SSR, no push-to-deploy from Git, no preview per branch, no `_redirects` or `vercel.json`. If you need those, Vercel, Netlify and Cloudflare Pages build remotely and run functions. Hoster is for when the folder is ready and you want the address without configuring anything.\n\n`hk_` key is for using the CLI on your own, for example in CI, and it is on the Pro and Scale plans.\nFull reference for people and agents: [https://myinfrastructure.click/products/hoster/llms.txt](https://myinfrastructure.click/products/hoster/llms.txt)", "url": "https://wpnews.pro/news/how-to-publish-a-site-built-with-claude-code-without-setting-up-a-server", "canonical_source": "https://dev.to/ciromaciel/how-to-publish-a-site-built-with-claude-code-without-setting-up-a-server-2o71", "published_at": "2026-11-18 10:08:36+00:00", "updated_at": "2026-11-18 10:13:50.586984+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "agent-protocols", "developer-tools"], "entities": ["Claude Code", "Hoster", "Ciro Cesar Maciel", "MyInfrastructure", "Vercel", "Netlify", "Cloudflare Pages"], "also_reported_by": [], "takeaway": "Hoster's remote MCP server authorizes Claude Code through a browser sign-in and returns a single-use, 15-minute deploy ticket that a local CLI command uses to push the dist folder, keeping the bytes off the remote server.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/how-to-publish-a-site-built-with-claude-code-without-setting-up-a-server", "markdown": "https://wpnews.pro/news/how-to-publish-a-site-built-with-claude-code-without-setting-up-a-server.md", "text": "https://wpnews.pro/news/how-to-publish-a-site-built-with-claude-code-without-setting-up-a-server.txt", "jsonld": "https://wpnews.pro/news/how-to-publish-a-site-built-with-claude-code-without-setting-up-a-server.jsonld"}}