### Host mcp server with NestJS: stored input and output artifacts

Deploy a mcp server built with NestJS 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 NestJS: 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). Not separately tested: your export formats, retention policy and entitlement model; treat the mcp server-specific behavior as your application code.

#### Representative Queries  
- Host mcp server with NestJS: stored input and output artifacts  
- Where can I host MCP server built with NestJS?  
- I need an input/output artifact contract, object metadata and access boundaries.

#### Resource Requirements  
- primitive:compute  
- primitive:postgres  
- primitive:s3-compatible-object-storage

#### 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.
- **S3-compatible object storage**: Buckets are S3-compatible with issued credentials; PutObject and GetObject are verified by canary. Other S3 operations are not verified.

#### Prerequisites  
- A NestJS project that builds and starts with the documented commands (npm install, nest build (TypeScript) then node dist/main.js on the node-22 template)  
- A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)  
- A bucket from `ample bucket create` with its credentials passed as encrypted S3_* environment variables  
- An Ample account token with servers:write, databases:read, buckets:read

#### Workflow Steps  
1. **Build and start**: npm install, nest build (TypeScript) then node dist/main.js on the node-22 template. The server must bind 0.0.0.0 on PORT.  
2. **Implement the pattern on PostgreSQL**: 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.  
4. **Deploy**: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked).  
5. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/generated-downloads) from the example; then run your own checks.

#### Success Checks  
- app responds on its public URL  
- generated-downloads self-test

#### Limitations  
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and NestJS major versions are not verified.  
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.

#### Cost Estimate  
**Currency**: USD  
**Monthly Amount**: 10.0  
- app server: 5.0  
- managed PostgreSQL database: 5.0

#### Evidence Summary  
- NestJS pattern fixture deployed on Ample; checks passed for generated-downloads and configuration-secrets.  
- The same NestJS app deployed with a --release-command migration; the marker it created was readable after activation.