# Host mcp server with Hono: Postgres-backed state

Deploy a mcp server built with Hono 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 Hono: 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 Hono: Postgres-backed state
- Where can I host MCP server built with Hono?
- 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
- A Hono project that builds and starts with the documented commands (npm install and npm run start with @hono/node-server on the node-22 template)
- 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

## Tested Configuration
- **Template:** node-22
- **Runtime:** node
- **Size:** s-1vcpu-1gb
- **Install:** npm install
- **Build:** npm run build --if-present
- **Start:** npm run start

## Workflow Steps
1. **Build and start**  
npm install and npm run start with @hono/node-server on the node-22 template. 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.  
`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`.  
`ample logs  --kind build`

## Examples
**Hono pattern fixture**  
Multi-pattern Hono app whose durable job state module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

## Success Checks
- **App responds on its public URL**  
`http_get /` expect: ample canary hono patterns
- **Durable-job-state self-test**  
`http_get /p/durable-job-state` expect: job=done attempts=1 idempotent=true

## Limitations
- Verified on the node-22 template at s-1vcpu-1gb with the example fixture; other sizes, templates and Hono 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.
- Apps auto-pause when idle and wake on the next request; always-on is an operator setting, not a plan feature.
- Managed PostgreSQL 16 only; extensions, connection limits and backup or restore procedures are not verified; apps and their databases are placed together.