Pre-production audit and checklist for FrontMCP servers. Use before go-live to verify security hardening, performance checks, observability, monitoring, and health checks. Triggers: production ready, security audit, performance check, production checklist, hardening, go live.
Router for production readiness checklists. Start with the common checklist (security, performance, reliability, observability), then follow the target-specific checklist for your deployment environment.
Decision: Use this skill when preparing for production. Start with common-checklist, then pick your deployment target.
Check the project to determine the deployment target:
package.json scripts for frontmcp build --target <target>ci/Dockerfile (node), vercel.json (vercel), wrangler.toml (cloudflare), ci/template.yaml (lambda)cli or browser in the build configAlways start with the common checklist — it covers security, performance, reliability, and observability that apply to every target.
After the common checklist, run the checklist for your deployment target.
| Scenario | Reference | Description |
|---|---|---|
| Common security, performance, reliability, observability | references/common-checklist.md | Applies to ALL targets — run this first |
| Health & readiness endpoints (/healthz, /readyz) | references/health-readiness-endpoints.md | Custom probes, Kubernetes, runtime-aware readiness |
| Standalone Node.js server with Docker | references/production-node-server.md | Docker, health checks, Redis, scaling, CI/CD |
| Node.js SDK / direct client (npm package) | references/production-node-sdk.md | create()/connect() API, disposal, npm publishing |
| Vercel serverless / edge | references/production-vercel.md | Vercel config, edge runtime, cold starts, Vercel KV |
| Cloudflare Workers | references/production-cloudflare.md | Wrangler, Workers runtime, KV, Durable Objects |
| AWS Lambda | references/production-lambda.md | SAM template, cold starts, DynamoDB, API Gateway |
| CLI daemon (local MCP server) | references/production-cli-daemon.md | Process manager, socket files, service registration |
| CLI binary (one-shot execution) | references/production-cli-binary.md | Fast startup, stdio transport, exit codes, npm bin |
| Browser SDK | references/production-browser.md | Bundle size, browser APIs, CSP, CDN distribution |
| File / Signal Found | Target |
|---|---|
ci/Dockerfile or ci/docker-compose.yml | Standalone server → production-node-server.md |
serve: false or create() API usage | SDK / direct client → production-node-sdk.md |
vercel.json | Vercel → production-vercel.md |
wrangler.toml | Cloudflare → production-cloudflare.md |
ci/template.yaml | Lambda → production-lambda.md |
frontmcp start / socket / service install usage | CLI daemon → production-cli-daemon.md |
build --target cli + bin in package.json | CLI binary → production-cli-binary.md |
build --target browser in scripts | Browser → production-browser.md |
After completing both common and target-specific checklists:
frontmcp doctor to check project configurationfrontmcp test to ensure all tests passfrontmcp build to verify production build succeedsfrontmcp-setup → references/readme-guide.md)frontmcp-config, frontmcp-deployment, frontmcp-testing, frontmcp-setup, frontmcp-observability