Host mcp server with Hono: streamed responses

Deploy a mcp server built with Hono 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 Hono: 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.

Representative Queries

• Host mcp server with Hono: streamed responses
• Where can I host MCP server built with Hono?
• 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 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

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: 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/streaming-response-service) 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 streaming response service module was checked live; the module is under tests/deploy-canaries/_pattern-modules.

Success Checks

• App responds on its public URL: Check path / expecting ample canary hono patterns
• Streaming-response-service self-test: Check path /p/streaming-response-service expecting an SSE stream: data: id=, then chunk events one interval apart (read incrementally: first chunk within seconds, chunks spread over the interval), then data: done; /status?id= reports sent=N disconnected=true|false done=true|false

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 event schema, reconnection strategy and any per-request duration ceiling beyond the 70 seconds measured) is application code and was not separately tested.
• Region, compliance attestations and request-duration limits are unknown and not claimed.

Cost Estimate

• Currency: USD
• Monthly Amount: 10.0
• Basis: size prices from pricing.toml (loaded by the API)

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

Evidence Summary

• Hono pattern fixture: Deployed on Ample; checks passed for streaming-response-service and configuration-secrets.

Last Verified At

• 2026-09-21T01:14:18Z

Next Actions

• Browse the catalog index: [GET /v1/catalog]
• Search published recipes: [POST /v1/catalog/search] with query Host mcp server with Hono: streamed responses.