Deploy a Rust API with your AI, over MCP (2026)
Your Rust API compiles. Connected to while over MCP, your AI deploys it in France, with a Dockerfile ready to go: built in release mode, run in a minimal image, without admin rights.
By Aloïs Oddon, co-founder of Nextmap. Facts checked on November 19, 2026.
The short version. Over MCP, your AI deploys your Rust API, Axum or Actix, with while, in France, with a Dockerfile ready to build and a minimal image. What matters, like deleting a database, waits for a person’s approval.
Prerequisites
- A Rust API, with its Cargo.toml.
- 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:
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:
apiVersion: while/v1
project: mon-api
services:
- name: web
port: 8080
health:
path: /health
while recognizes Rust by its Cargo.toml, and your AI gets a Dockerfile ready to build: cargo build --release, then your binary in a minimal Debian image, without admin rights. Your API listens on the port it receives in PORT, like this Axum API1:
use axum::{routing::get, Router};
#[tokio::main]
async fn main() {
let port = std::env::var("PORT").unwrap_or_else(|_| "8080".into());
let app = Router::new()
.route("/", get(|| async { "Bonjour" }))
.route("/health", get(|| async { "ok" }));
let listener = tokio::net::TcpListener::bind(format!("0.0.0.0:{port}")).await.unwrap();
axum::serve(listener, app).await.unwrap();
}

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.
Speed things up with a cache
You, to your AI: Add a cache for the most-read pages.
Your AI declares a Redis-compatible cache, connected to your code with its password.
Restrict your API to your colleagues
You, to your AI: Restrict the API 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 connected 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.
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 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, Valkey cache (Redis), Internal access, Custom domain, Versions and rollback and Dependency vulnerabilities.
Next steps
Sources
- Axum, the documentation, accessed November 2, 2026