---
title: "Deploy Nuxt over MCP with while.sh"
url: https://while.sh/en/guides/deploy-nuxt/
author: "Aloïs Oddon, co-founder of Nextmap"
updated: 2026-11-02
---

# Deploy a Nuxt app from your AI agent, over MCP

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

## Prerequisites

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

```text titre="Instructions"
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:

```yaml titre="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` variable (source 2). Your app is built, its tests run, then it starts. The Nuxt 4 starter project deploys as is (source 1).

## Restrict your app to your colleagues

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

Your agent adds two lines to the service:

```yaml titre="while.yaml"
    access: internal
    email_domains: [acme.com]
```

Once your Google Workspace or Microsoft 365 is linked 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

> You, to your agent: Open the app to our customer, with a password.

Your agent 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 agent will never see.

## Add a database

> You, to your agent: Add a PostgreSQL database.

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

## Move to your own domain

> You, to your agent: Put the app on planning.acme.com.

Your agent 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 agent: Show me the new version before you deploy it.

Your agent opens a preview, at its own address, with its own data. You look at it, then your agent puts it into production.

## Go back to the previous version

> You, to your agent: 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.

## Next steps

- [Restrict your app to the people in your company](/en/guides/internal-tool-company-sign-in/)
- [Deploy a Node.js API and its PostgreSQL database](/en/guides/deploy-node-api-postgresql/)
- [Compare the hosts that have an MCP server](/en/comparisons/mcp-hosting-claude-code/)

## Sources

1. [Nuxt, the version 4 starter project (nuxt build, no start script)](https://github.com/nuxt/starter/tree/v4), 2026-11-02
2. [Nuxt, deploying to a Node.js server (.output/server/index.mjs, PORT)](https://nuxt.com/docs/4.x/getting-started/deployment), 2026-11-02

## 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.