Deploy a SvelteKit app from your AI agent, over MCP

Prerequisites

• A SvelteKit app. Your agent adds the Node adapter if it’s missing.
• An AI agent that works in a terminal: Claude Code, Codex, Cursor or Gemini CLI.

Step 1: Give your agent these instructions

Open your agent in your app’s folder and paste these instructions into it:

Connect to while with my account (while.sh/agents), then deploy my app.

Without an account, your agent deploys your app as a trial, in one request. To keep it, open the link it gives you and create your account.

With your account, your agent adds while’s MCP server itself. If it asks you to, restart it. On the first call to while, a page opens in your browser. In Claude Code, if it doesn’t open, type /mcp, choose while, then Authenticate. On that page, choose your app, or “A new app”, then click Authorize.

Step 2: Open your app

Your agent gives you your app’s address, for example https://mon-appli.while.cloud, over HTTPS.

What your agent does

It writes while.yaml at the root of your app:

apiVersion: while/v1
project: mon-appli
services:
  - name: web
    port: 3000
    health:
      path: /
    env:
      ORIGIN: https://mon-appli.while.cloud

Your app is built, then started with node build, which listens on the port it receives in PORT¹. ORIGIN gives SvelteKit your app’s public address: without it, your forms would be refused as coming from somewhere else¹. If your app doesn’t have the Node adapter yet, your agent adds it.

Add a database

Your agent declares the database in while.yaml, and its address reaches your code in DATABASE_URL. It is backed up every day, and can go back to a precise moment if needed.

Restrict your app to your colleagues

Your agent adds two lines to the service:

    access: internal
    email_domains: [acme.com]

Once your Google Workspace or Microsoft 365 is connected to while, on the Pro plan, your colleagues open it with their usual account, and your code receives their name and email address, with no sign-in page to write.

Share with a customer, protected by a password

Your agent makes the app private. Then, on the app’s page in while, you create a link that lasts 1, 7 or 30 days, with a password your agent will never see.

Move to your own domain

Your agent declares the domain and updates ORIGIN. You add the DNS records it gives you, and the HTTPS certificate follows.

Go back to the previous version

In the 30 minutes after a deployment, the previous version comes back in a second. After that, it takes a few seconds. Once the previous version is back, your agent reads what broke in while’s logs, fixes it and deploys again.

In the docs: PostgreSQL databases, Internal access, Custom domain and Versions and rollback.

Next steps

• Deploy a Nuxt app
• Deploy a static site
• Deploy a Node.js API and its PostgreSQL database