# Deploy a website from Claude Code with one MCP connection

Source: https://kilat.host/articles/deploy-a-website-from-claude-code

To deploy a website from Claude Code, connect it to KilatBot's MCP server, build your site, and ask Claude to publish it. Claude creates a site, uploads the built files, and asks you before it goes live; the site runs on a KilatBot address in Jakarta, and a Free site costs nothing. This guide covers the setup, the exact tool flow, custom domains and the limits.

KilatBot hosts static sites only: finished HTML, CSS and JavaScript, Vite builds and framework static exports. Server-side rendering, API routes and background processes are not supported. If your site needs a database, it can link an existing PocketBase backend.

## How do you connect Claude Code to KilatBot?

You need a KilatBot account with a plan. Run this, then open `/mcp` in Claude Code and choose Authenticate:

```
claude mcp add --transport http kilat https://kilat.host/mcp
```

Reading your sites needs no extra permission; publishing needs **Site publish**, which the [MCP workflow guide](https://kilat.host/docs/mcp-workflow) shows how to add. If you prefer a token in a project file, the [Claude Code setup](https://kilat.host/docs/mcp#claude-code) shows a `.mcp.json` entry that reads it from your environment, so the secret never sits in the repository. Check the connection with a read-only request first: “Use KilatBot to list my sites. Do not change anything.”

## What do you ask Claude to do?

Once your site builds, one request is enough:

```
Build this site, then publish dist/ to a new KilatBot site called "launch-page".
Check the build output for secrets first. Show me the release before you deploy it.
```

Claude handles the steps below. You approve the site creation and the final deploy.

## What happens during a deploy?

1. **Create the site.** `create_site` makes a Free site in Jakarta. Each verified workspace can have up to 10 Free sites.
2. **Package the build, not the source.** Claude archives the built folder, for example `tar --format=ustar -czf site.tar.gz -C dist .`, and computes its size and SHA-256.
3. **Upload.** `prepare_site_upload` returns a one-line upload command that sends the archive straight to storage. No signed URL or token passes through the conversation.
4. **Validate.** `complete_site_upload` checks the archive on the server. Only a validated release can go live.
5. **Deploy.** `deploy_site` activates the release after you approve it. Claude then checks `get_site_deployment` and reports the URL only once the site serves over HTTPS.

Every tool and argument is in the [static website publishing reference](https://kilat.host/docs/mcp#static-sites). A later deploy works the same way, and `rollback_site` brings back an earlier release.

## Is anything in the build private?

No. Everything you ship to a browser is public, including environment values that your build tool embeds in JavaScript. Never include `.env` files, provider keys, private keys or MCP tokens. KilatBot rejects some obvious secrets automatically, but that is not a guarantee: ask Claude to inspect the build output before it uploads.

## Can you use your own domain?

Yes, on a Paid site; a Free site stays on its KilatBot address. Upgrading is done in the dashboard. Then `add_site_custom_domain` returns the A and TXT records to publish at your DNS provider, and `verify_site_custom_domain` checks them and requests the HTTPS certificate. You can also [register a domain through KilatBot](https://kilat.host/articles/how-to-find-and-register-a-domain-for-your-agents-website).

## What are the limits of a Free site?

- Uploads up to 10 MiB, with up to 500 files.
- No custom domain, and sites run in Jakarta only.
- A site is suspended after 90 days without a publish or an owner sign-in, with seven days to recover it.
- No bandwidth allowance or uptime guarantee is promised.

For single-page apps, turn on SPA fallback so navigation routes serve `index.html`; missing asset paths still return 404.

## Can an agent publish without Claude Code?

Yes. A KilatBot agent on the Coder template builds and publishes sites itself, from a chat on the web or on Telegram. Use Claude Code when the site lives in your repository; use the agent when you want to describe a page and review it. See [ask your agent for a landing page](https://kilat.host/articles/ask-your-agent-for-a-landing-page-and-publish-it) and [manage agents from Claude Code](https://kilat.host/articles/run-kilatbot-agents-from-claude-code-or-codex). [Get started](https://kilat.host/users/sign_up).

Read next: [Set up KilatBot agents from Claude Code or Codex](https://kilat.host/articles/run-kilatbot-agents-from-claude-code-or-codex) · [Ask your agent for a landing page, and publish it](https://kilat.host/articles/ask-your-agent-for-a-landing-page-and-publish-it)
