Deploy a Spring Boot app with your AI, over MCP (2026)
Your Spring Boot app runs locally. Connected to while over MCP, your AI deploys it in France, with its PostgreSQL database backed up every day, and a ready-made Java Dockerfile, for Maven or Gradle.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
The short version. Over MCP, your AI deploys your Spring Boot app with while, in France, with its PostgreSQL database and a Java Dockerfile ready to build. What matters, like deleting a database, waits for a person’s approval.
Prerequisites
- A Spring Boot app, built with Maven or Gradle.
- 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:
Connect to while with my account (while.sh/agents), then put my app on while.
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 “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:
apiVersion: while/v1
project: mon-appli
services:
- name: web
port: 8080
health:
path: /actuator/health
resources:
memory: 512Mi
databases:
- name: main
Spring Boot is recognized by its pom.xml or its build.gradle, and your AI receives a Dockerfile ready to build: your project’s Java version, and the jar built by Maven or Gradle, started on while’s port. Your AI adds it to your app. Actuator’s /actuator/health route tells while that your app is ready1: your AI adds Actuator if it’s missing. It also connects Spring to the database: the address from DB_MAIN_URL, rewritten as jdbc:postgresql://, with the user and password received in DB_MAIN_USER and DB_MAIN_PASSWORD.

Read your database in SQL
You, to your AI: How many orders this week?
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 the set 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:
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 on every deployment, then every day. Your AI is notified of 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, Versions and rollback and Dependency vulnerabilities.
Next steps
Sources
- Spring Boot, Actuator endpoints (health), accessed November 2, 2026