Deploy a React app built with Vite with your AI, over MCP (2026)
Your AI wrote your React app with Vite. Connected to while over MCP, it also deploys it, over HTTPS and in France, and every page opens from its link, even after a reload.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
The short version. Over MCP, your AI deploys your Vite and React app with while, over HTTPS and in France. With React Router, your links work on reload. What matters, like deleting a database, waits for a person’s approval.
Prerequisites
- A React app built with Vite, and its package.json.
- 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
type: static
root: dist
Your app is built with npm run build at every deployment1, then the dist folder is served, with an HTTP cache. A path like /dashboard, opened from a link or reloaded, returns your app, and React Router shows the right page.

Pass your API’s address at build time
You, to your AI: Connect the app to our API, at api.acme.com.
Your AI adds the address to the service, in while.yaml:
build:
args:
VITE_API_URL: https://api.acme.com
Vite writes it into your app at build time, and your code reads it from import.meta.env.VITE_API_URL2. Anyone can read these values in the browser, so a secret key stays on your API’s side.
Add an API and its database
You, to your AI: Add a Node.js API and a PostgreSQL database for the bookings.
Your AI adds a service to while.yaml, next to your app, with its PostgreSQL database backed up every day. The details are in the guide for a Node.js API and its PostgreSQL database.
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, 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, you add the DNS records it gives you, and the HTTPS certificate follows.
See a new version before you deploy it
You, to your AI: Show me the new version before you deploy it.
Your AI opens a preview, at its own address, with its own data. You look at it, then your AI puts it into production.
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: Static site, Internal access, Custom domain, Previews, Versions and rollback and Variables and secrets.
Next steps
Sources
- Vite, deploying a static site (npm run build, the dist folder), accessed November 2, 2026
- Vite, environment variables (VITE_), accessed November 2, 2026