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.
This 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.
Almost 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).
If 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.
claude mcp add --transport http hoster https://hoster.worker.myinfrastructure.click/mcp
No 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.
Say it in words: "build and publish the dist folder to Hoster as project my-site". Behind that:
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.
The ticket is good for one project, one use and 15 minutes. If an upload fails halfway, run the same command again.
Why two parts? The MCP server is remote and cannot reach your disk, so it authorizes and the local command sends the bytes.
The site answers at https://my-site.myhoster.click, with HTTPS from the first second: there is no certificate to wait for.
To 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-up, and keeps the last 5 by default.
A custom domain is one CNAME to proxy.hoster.myinfrastructure.click, and Hoster issues its certificate too.
404.html at the root of the build turns that fallback off.window.ENV.
No 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.
hk_ key is for using the CLI on your own, for example in CI, and it is on the Pro and Scale plans.
Full reference for people and agents: https://myinfrastructure.click/products/hoster/llms.txt