Host mcp server with Axum: stored input and output artifacts · Ample Computer

Host mcp server with Axum: stored input and output artifacts

Deploy an MCP server built with Axum on Ample using the generated downloads pattern. Compute runs the app in an isolated microVM behind a public HTTPS URL, a managed PostgreSQL 16 database is auto-provisioned and injected as DATABASE_URL, a private S3-compatible bucket holds objects with credentials delivered as encrypted environment variables. Verified on Axum: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). The MCP server-specific behavior (your export formats, retention policy and entitlement model) is your application code on that verified basis.

Verified November 5, 2026

What it runs on

You need

Exact tested configuration

build cargo build --release

run time rust

sizes - 1vcpu - 2gb

start ./$(ls target/release/*.d | grep -v '/lib' | head -n 1 | sed 's/.d$//')

template ubuntu-24.04

Steps

  1. Build and start. cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL. The server must bind 0.0.0.0 on PORT.

  2. Implement the pattern on PostgreSQL. The fixture's module implements generated downloads: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.

  3. Wire object storage. Create the bucket(s), then pass endpoint, region, bucket and keys as --env values. Use path-style addressing. Keep private data in an unpublished bucket.

  4. Deploy. Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 needs an answer first). Re-running with no change is a no-op.

$ ample deploy . --name <app-name> --public --env S3_ENDPOINT=... --env S3_REGION=... --env S3_BUCKET=... --env S3_ACCESS_KEY_ID=... --env S3_SECRET_ACCESS_KEY=...
  1. Verify. Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks. On failure read ample logs <deployment_id> --kind build then --kind runtime.
$ ample logs <deployment_id> --kind build

How it was checked

✓ app responds on its public URL · http get/ → “ample canary axum patterns”
✓ generated-downloads self-test · http get/p/generated-downloads → “export=ok rows=3 (with ?token=...; 401 without)”

Evidence

  1. November 5, 2026 · canary run
    Axum pattern fixture deployed on Ample (cargo build --release in the rust builder image (stable toolchain, Cargo.lock committed, pure-Rust dependencies), then the release binary on the ubuntu-24.04 template reading PORT and DATABASE_URL); checks passed for generated-downloads and configuration-secrets. Pattern proof: an export query rendered to a CSV artifact stored with metadata in a private bucket and returned only to an authorized caller (401 without token, export=ok rows=3).

  2. November 6, 2026 · canary run
    The same Axum app deployed with a --release-command migration; the marker it created was readable after activation.

Tested examples

What it doesn’t cover