### Host MCP Server with Spring Boot: Streamed Responses

Deploy a MCP server built with Spring Boot on Ample using the streaming response service 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. Verified on Spring Boot: a Server-Sent Events endpoint read incrementally through the public HTTPS gateway: five one-second chunks arrived spread over time with the first within seconds (not buffered), a 70-second stream of 36 chunks completed past common 60-second idle timeouts, and a client that disconnected after two chunks was observed and recorded by the server (disconnected=true). Not separately tested: your event schema, reconnection strategy and any per-request duration ceiling beyond the 70 seconds measured; treat the MCP server-specific behavior as your application code.

#### Summary
- Deploy a MCP server with auto-provisioned PostgreSQL.
- Verify server behavior and response streaming pattern.

### Representative Queries
- Host MCP server with Spring Boot: streamed responses.
- Where can I host the MCP server built with Spring Boot?
- I need a tested end-to-end streaming transport, timeout behavior and client disconnect handling.

### Resource Requirements
- **Compute**
- **Postgres**

### Infrastructure Requirements
**Compute**:  Apps run in isolated x86_64 Firecracker microVMs that auto-pause when idle and wake on request; sizes are the priced VM sizes.

**Postgres**: Managed PostgreSQL 16 runs in its own microVM and is auto-provisioned when an app needs a database and no DATABASE_URL is supplied.

### Prerequisites
- A Spring Boot project that builds and starts with the documented commands (./mvnw -q -DskipTests package or the Gradle wrapper) producing one application jar, then `java -jar` on the jvm-21 template (Temurin JDK 21) with server.port read from PORT.
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env).
- An Ample account token with `servers:write`, `databases:read`.

### Workflow Steps
1. **Build and start**:
   - `./mvnw -q -DskipTests package` (or the Gradle wrapper) producing one application jar, then `java -jar` on the jvm-21 template (Temurin JDK 21) with server.port read from PORT.

2. **Implement the pattern on PostgreSQL**:
   - The fixture's module implements streaming response service: a Server-Sent Events endpoint.

3. **Deploy**:
   - Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).
   - `ample deploy . --name <yourAppName> --public`

4. **Verify**:
   - Fetch the live URL and the pattern self-test route(s) from the example; then run your own checks.
   - `ample logs --kind build`

### Examples
- **Spring Boot pattern fixture**:
  - Multi-pattern Spring Boot app whose streaming response service module was checked live.

### Success Checks
- App responds on its public URL.
- Streaming-response-service self-test: checks for outcomes of data transmission.

### Limitations
- Verified on the jvm-21 template; other sizes and versions not verified.
- MCC server checks are application code and not tested separately.

### Cost Estimate
- **Monthly Amount**: $10.00
  - Breakdown:
    - App server: $5.00
    - Managed PostgreSQL database: $5.00

### Evidence Summary
- Spring Boot pattern fixture deployed on Ample with passed checks for streaming-response-service and configuration-secrets.

### Unknowns
- Region availability and compliance attestations are unknown.