page:recipes:mcp server:fastify:persistent state

Host MCP Server with Fastify: Postgres-backed State

Summary

Deploy a MCP server built with Fastify 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 Fastify: 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 Fastify: Postgres-backed state
• Where can I host MCP server built with Fastify?
• I need a durable state schema and retry/recovery semantics implemented by application code.

Resource Requirements

• Primitive: Compute
• Primitive: Postgres

Framework

Fastify

Workload

MCP server

Release Status

Published

Support Status

Verified

Execution Status

Ready

Prerequisites

1. A Fastify project that builds and starts with the documented commands (npm install, npm run build --if-present, npm run start on the node-22 template).
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.

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, npm run build --if-present, npm run start 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. Command: ample deploy . --name <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 <project> --kind build then --kind runtime. Command: ample logs <project> --kind build

Examples

• Title: Fastify pattern fixture
  • Description: Multi-pattern Fastify app whose durable job state module was checked live; the module is under tests/deploy-canaries/_pattern-modules.
  • Source Reference: tests/deploy-canaries/fastify-patterns

Success Checks

1. App responds on its public URL.
   • Kind: http_get
   • Path: /
   • Expect: ample canary fastify patterns
2. Durable-job-state self-test.
   • Kind: http_get
   • Path: /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 Fastify 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.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.00
• Authority: true
• Basis: size prices from pricing.toml.
• Components:
  • App Server: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
  • Managed PostgreSQL Database: size s-1vcpu-1gb, quantity 1.0, monthly amount 5.0
• Note: Always-on monthly price of the tested sizes; apps and databases auto-pause when idle.

Evidence Summary

• Kind: canary_run
  • Summary: Fastify pattern fixture deployed on Ample; checks passed for durable-job-state and configuration-secrets.
  • Observed At: 2026-09-21T01:14:18Z
  • Implementation Revision: 50dbac567d2c5cc8e55e6c748a646be0025d9cfb-dirty.

Next Actions

1. Browse the Catalog Index: Action ID: browse-catalog
2. Search published recipes by intent: Action ID: search-recipes
3. Prepare a side-effect-free deployment plan for an authorized project: Action ID: plan:page:recipes:mcp-server:fastify:persistent-state
4. Read the existing agent authentication setup: Action ID: auth-setup
5. Browse MCP server: Action ID: browse:workload:mcp-server
6. Browse Fastify: Action ID: browse:stack:framework-fastify
7. Browse Durable job state: Action ID: browse:pattern:durable-job-state
8. Browse Deploy MCP server: Action ID: browse:intent:deploy-mcp-server.