Deploy a SvelteKit app with your AI, over MCP (2026)
Your AI wrote your SvelteKit app. Connected to while over MCP, it also deploys it, over HTTPS and in France, with its forms and its server routes, and without a Dockerfile.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
The short version. Over MCP, your AI deploys your SvelteKit app with while, over HTTPS and in France, with the Node adapter and no Dockerfile or server to manage. What matters, like deleting a database, waits for a person’s approval.
Prerequisites
- A SvelteKit app. Your AI adds the Node adapter if it’s missing.
- An AI that works in a terminal: Claude Code, Codex, Cursor or Gemini CLI.
Step 1: Give your AI this message
Open your AI in your app’s folder and paste this message into it:
Connect to while with my account (while.sh/agents), then put my app on while.
Without an account, your AI 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 AI 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 AI gives you your app’s address, for example https://mon-appli.while.cloud, over HTTPS.
What your AI 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 PORT1. ORIGIN gives SvelteKit your app’s public address: without it, your forms would be refused as coming from somewhere else1. If your app doesn’t have the Node adapter yet, your AI adds it.

Add a database
You, to your AI: Add a PostgreSQL database.
Your AI 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
You, to your AI: Restrict the app to people in the company.
Your AI makes the service internal:
access: internal
Then it asks for the Access role for your domain, @acme.com, on this app, and a person in your organization approves it.
Once your Google Workspace or Microsoft 365 is connected to while, on the Pro plan, your colleagues sign in 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
You, to your AI: Open the app to our customer, with a password.
Your AI 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 AI will never see.
Move to your own domain
You, to your AI: Put the app on app.acme.com.
Your AI 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
You, to your AI: Go back to the previous version.
In the 30 minutes after a production release, the previous version comes back in a second. After that, it takes a few seconds. Once the previous version is back, your AI 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
Sources
- SvelteKit, the Node adapter (node build, PORT, ORIGIN), accessed November 2, 2026