Skip to content

Deploy a Nuxt app with your AI, over MCP (2026)

Your AI wrote your Nuxt app. Connected to while over MCP, it deploys it too, over HTTPS, and you choose who can open it.

By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.

View as Markdown

Deploy a Nuxt app with your AI, over MCP: host a Nuxt app in France, put in production by Claude Code, Cursor or Codex over HTTPS, with the database backed up every day

The short version. Over MCP, your AI deploys your Nuxt app with while, over HTTPS, open to everyone or to your colleagues. No Dockerfile, no server. What matters, like deleting a database, waits for a person’s approval.

Prerequisites

  • A Nuxt app that builds with nuxt build.
  • 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:

The message to give your AI
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:

while.yaml
apiVersion: while/v1
project: mon-appli
services:
  - name: web
    port: 3000
    health:
      path: /

Port 3000 is the one used by Nuxt’s Node server, which reads the PORT variable2. Your app is built, its tests run, then it starts. The Nuxt 4 starter project deploys as is1.

What your AI does to put a Nuxt app in production on while: the while.yaml file, the build and tests, the HTTPS address, the PostgreSQL database backed up every day and a person's approval, in France
Your AI writes while.yaml, while builds and serves the app over HTTPS, and the previous version stays ready.

Restrict your app to your colleagues

You, to your AI: Restrict the app to people in the company.

Your AI makes the service internal:

while.yaml
    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 linked 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 valid for 1, 7 or 30 days, with a password your AI will never see.

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. The database is backed up every day, with a way back to a precise moment over 14 days.

Move to your own domain

You, to your AI: Put the app on planning.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: PostgreSQL databases, Internal access, Custom domain, Previews and Versions and rollback.

Next steps

Sources

  1. Nuxt, the version 4 starter project (nuxt build, no start script), accessed November 2, 2026
  2. Nuxt, deploying to a Node.js server (.output/server/index.mjs, PORT), accessed November 2, 2026

Questions

Do I need a start script?

No, the server that nuxt build produces starts as is.

Does my app receive the signed-in person’s name?

Yes. When it’s restricted to your company, it receives the signed-in person’s name and email address.

What about a statically generated Nuxt site?

It deploys too, served with an HTTP cache.

Where do my app and its data run?

In France, at Nextmap. The database is backed up every day, with a way back over 14 days, once a person approves.

Does my AI see my credentials?

No. You paste them into while, the app uses them, and your AI never sees them. Every call is logged.

Give your AI the message, and it takes care of the rest

Give this to your AI

Read while.sh/agents and help me get started with while.

Copy the message

In 3 minutes, with no sign-up, the tool has its own address. To keep it, create your account.

For a company project, write to the while team: hello@while.sh