Skip to content

Deploy an ASP.NET Core app with your AI, over MCP (2026)

Your ASP.NET Core API or app is ready. Connected to while over MCP, your AI deploys it in France, with a ready-made .NET Dockerfile and 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 an ASP.NET Core app with your AI, over MCP: host an ASP.NET Core 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 ASP.NET Core app with while, in France, with a .NET Dockerfile ready to build and its PostgreSQL database. What matters, like deleting a database, waits for a person’s approval.

Prerequisites

  • An ASP.NET Core app, with its .csproj file at the root of the repository.
  • 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: 8080
    health:
      path: /health
databases:
  - name: main

ASP.NET Core is detected from its .csproj, and your AI receives a Dockerfile ready to build: dotnet publish, your project’s .NET version, and while’s port passed to Kestrel. Your AI adds it to your app, along with a two-line health check1:

Program.cs
builder.Services.AddHealthChecks();
var app = builder.Build();
app.MapHealthChecks("/health");
What your AI does to put an ASP.NET Core 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.

Read your database in SQL

You, to your AI: How many people signed up today?

Your AI reads your database in SQL through while’s MCP server, with your permissions on the data, and it can’t write to it.

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. Microsoft, health checks in ASP.NET Core, accessed November 2, 2026

Questions

Do I need to write a Dockerfile?

No. ASP.NET Core is detected, and your AI receives a Dockerfile ready to build. If your project already has its own, it is used to build the image.

Which version of .NET?

The one in your .csproj: the Dockerfile uses it.

Does it work with Entity Framework Core and PostgreSQL?

Yes, with Npgsql: your AI connects while’s database and runs your migrations.

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