Skip to content

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

Your Flask app runs locally. Connected to while over MCP, your AI deploys it in France, served by gunicorn rather than the development server, with its PostgreSQL database backed up every day.

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

View as Markdown

Deploy a Flask app with your AI, over MCP: host a Flask 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 Flask app with while, in France, served by gunicorn, with its PostgreSQL database and no Dockerfile. What matters, like deleting a database, waits for a person’s approval.

Prerequisites

  • A Flask app, with a requirements.txt file.
  • 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: 8000
    health:
      path: /

Then it adds gunicorn to requirements.txt1, and a Procfile that starts it on the port received in PORT. The name app:app follows your file, and your AI adapts it:

Procfile
web: gunicorn app:app --bind 0.0.0.0:$PORT

Your app is installed, your pytest tests run, and then it starts.

What your AI does to put a Flask 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.

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 it can go back to a precise moment if needed.

Run a job every night

You, to your AI: Run the data import every night at 3 am.

Your AI declares a scheduled job, which starts at that time with the same code and the same variables. If it fails, your AI is notified.

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.

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.

Fix a vulnerability in your dependencies

You, to your AI: Fix the vulnerabilities in our dependencies.

Your app’s dependencies are checked against known vulnerabilities at every deployment, then every day. Your AI is warned of a serious vulnerability, and it updates the package involved.

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, Scheduled jobs, Internal access, Custom domain, Versions and rollback and Dependency vulnerabilities.

Next steps

Sources

  1. Flask, serving the app with gunicorn, accessed November 2, 2026

Questions

Do I need to write a Dockerfile?

No. Your Python app is detected, installed from requirements.txt and started by the web line of the Procfile.

Why not flask run?

That’s the development server: once deployed, gunicorn serves your pages, as Flask recommends1.

Do my tests run?

Yes, pytest runs at every deployment, and a version that fails doesn’t replace the previous one.

Where is my app hosted?

In France, by Nextmap, a French company.

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