frontmcp-deployment

name	frontmcp-deployment
description	Use when deploying, building for production, packaging, or shipping a FrontMCP server. Covers build targets (node, cli SEA binary, browser, embeddable SDK, mcpb archive for Claude Desktop, serverless) and deploying to Vercel (with Vercel KV), AWS Lambda (API Gateway, SAM, CDK), Cloudflare Workers (KV, D1, Durable Objects, v1.3 skills-only), and Node (multi-stage Docker, docker-compose, PM2, nginx). Also the frontmcp.deploy.yaml manifest plus GitHub Action push-resync, MCP client integration / .mcp.json for Claude Desktop, Claude Code, Cursor, and VS Code over stdio or HTTP, and MCP protocol revisions (serving 2026-07-28 alongside 2024-11-05 through 2025-11-25). Triggers: deploy, build for production, dockerize, containerize, serverless, edge runtime, go live, ship it.
tags	["router","deployment","node","vercel","lambda","cloudflare","cli","browser","sdk","guide"]
category	deployment
targets	["all"]
bundle	["recommended","minimal","full"]
priority	10
visibility	both
license	Apache-2.0
metadata	{"docs":"https://docs.agentfront.dev/frontmcp/deployment/runtime-modes"}

FrontMCP Deployment Router

Entry point for deploying and building FrontMCP servers. This skill helps you choose the right deployment target or build format based on your infrastructure requirements.

When to Use This Skill

Must Use

• Choosing between deployment targets (Node vs Vercel vs Lambda vs Cloudflare) for a new project
• Deciding on a build format (server vs CLI vs browser vs SDK) for distribution
• Planning infrastructure and need to understand trade-offs between deployment options

Recommended

• Comparing serverless platforms for cost, cold-start, and feature support
• Understanding which transport protocol and storage provider each target requires
• Migrating from one deployment target to another

Skip When

• You already know your deployment target (go directly to deploy-to-node, deploy-to-vercel, etc.)
• You need to configure server settings, not deploy (see frontmcp-config)
• You need to build components, not ship them (see frontmcp-development)

Decision: Use this skill when you need to figure out WHERE to deploy. Open the matching reference under references/ directly when you already know.

Prerequisites

• A working FrontMCP server with at least one @App and one @Tool (see frontmcp-development)
• Server configuration completed (see frontmcp-config)
• Tests passing locally (see frontmcp-testing)

Steps

1. Review the Scenario Routing Table and Target Comparison below to choose a deployment target
2. Run frontmcp build --target <target> to produce the build output
3. Follow the specific deployment reference (e.g., references/deploy-to-node.md, references/deploy-to-vercel.md) for platform instructions
4. Verify with the Post-Deployment checklist at the end of this skill

Scenario Routing Table

Scenario	Reference	Description
Long-running server on VPS, Docker, or bare metal