Skip to content

Deploy a FastAPI API with your AI, over MCP (2026)

Your AI wrote your FastAPI API. Connected to while over MCP, it also deploys it, over HTTPS, with no Dockerfile or nginx to configure.

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

View as Markdown

Deploy a FastAPI API with your AI, over MCP: host a FastAPI API 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 FastAPI API with while, over HTTPS, PostgreSQL database included. No Dockerfile, no nginx, no server. What matters, like deleting a database, waits for a person’s approval.

Prerequisites

  • A FastAPI API, 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 API’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 API 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 API

Your AI gives you your API’s address, for example https://mon-api.while.cloud, over HTTPS.

What your AI does

It writes while.yaml at the root of your API:

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

Port 8000 is the default of uvicorn, FastAPI’s server2. Your API is installed, its tests run, then it starts, with no command to write. Render’s example FastAPI app deploys on while as is1.

What your AI does to put a FastAPI API 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 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 the set time with the same code and the same variables. If it fails, your AI is notified.

Restrict your API to your colleagues

You, to your AI: Restrict the API 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 to the API 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 API on api.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.

Fix a vulnerability in your dependencies

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

Your API’s dependencies are checked against known vulnerabilities at every deployment, then every day. Your AI is warned about a serious vulnerability, and 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, Previews and Versions and rollback.

Next steps

Sources

  1. render-examples/fastapi, an example FastAPI API published on GitHub, accessed November 2, 2026
  2. Uvicorn, server settings (--port, 8000 by default), accessed November 2, 2026

Questions

Do I need to write a Dockerfile?

No. Your Python API is detected, installed from requirements.txt and started with uvicorn when its main file, main.py for example, is at the root. Otherwise, your AI writes the command.

Do my tests run?

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

Can I call an external API without exposing its key?

Yes. You enter the key in while, and your API uses it without ever reading it.

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.

What happens if a version breaks something?

In the 30 minutes after a production release, the previous version comes back in a second, then in a few seconds.

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