# Host mcp server with Gin: Postgres-backed state

Deploy a mcp server built with Gin on Ample using the durable job state 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 Gin: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Not separately tested: your job types, payload schema and retry policy; treat the mcp server-specific behavior as your application code.

### Representative Queries
- Host mcp server with Gin: Postgres-backed state
- Where can I host MCP server built with Gin?
- I need a durable state schema and retry/recovery semantics implemented by application code.

### 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
1. A Gin project that builds and starts with the documented commands (CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build))
2. A PostgreSQL driver reading DATABASE_URL at runtime (auto-provisioned when omitted, or supplied with --env)
3. An Ample account token with servers:write, databases:read

### Workflow Steps
1. **Build and start**: CGO_ENABLED=0 go build -o app ./... then ./app on the ubuntu-24.04 template (go.sum committed for a reproducible build). The server must bind 0.0.0.0 on PORT.
2. **Implement the pattern on PostgreSQL**: The fixture's module implements durable job state: a jobs table with a state and attempts counter, processing inside a row-locked transaction, and a second run that is a no-op (job=done attempts=1 idempotent=true). Copy the approach into your schema; keep migrations idempotent and run them with --release-command.
3. **Deploy**: Run the synchronous deploy once and read the result (exit 0 live, 1 failed, 2 blocked). Re-running with no change is a no-op.
    ```bash
    ample deploy . --name  --public
    ```
4. **Verify**: Fetch the live URL and the pattern self-test route(s) (/p/durable-job-state) from the example; then run your own checks. On failure read `ample logs  --kind build` then `--kind runtime`.
    ```bash
    ample logs  --kind build
    ```

### Success Checks
- App responds on its public URL
- Durable-job-state self-test

### Limitations
- Verified on the ubuntu-24.04 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Gin major versions are not verified.
- The mcp server itself (your job types, payload schema and retry policy) is application code and was not separately tested; the pattern checks are what was verified.
- Region, compliance attestations and request-duration limits are unknown and not claimed.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.

### Cost Estimate
- **Currency**: USD
- **Monthly Amount**: 10.0
- **Basis**: size prices from pricing.toml (loaded by the API)

### Evidence Summary
- **Canary run**: Gin pattern fixture deployed on Ample; checks passed for durable-job-state and configuration-secrets.
- **Canary run**: The same Gin app deployed with a --release-command migration; the marker it created was readable after activation.

### Formats
- **HTML**: [Link](/content/recipes/mcp-server/gin/persistent-state/index.html)
- **Markdown**: [Link](/content/recipes/mcp-server/gin/persistent-state.md)
- **JSON**: [Link](https://api.ample.computer/v1/catalog/recipes/page%3Arecipes%3Amcp-server%3Agin%3Apersistent-state)