Hosted MCP Edge Regions#

MCPSail Host turns a generated MCP server into one global logical deployment. In production and PR preview environments, MCPSail deploys one runtime target in every enabled Host edge region and keeps the public MCP URL stable. Regions are platform infrastructure, not a customer-facing deployment choice.

Production Routing#

Each hosted MCP server receives one public hostname:

TEXT

https://your-server.mcp.mcpsail.com/mcp

Azure Front Door routes traffic to the nearest healthy MCPSail regional gateway. The gateway resolves the hosted server route and prefers the healthy runtime target in its own region before falling back to another healthy target.

TEXT

MCP client
  -> Azure Front Door
  -> closest healthy MCPSail gateway
  -> regional runtime target

The MCPSail API is the control plane. It creates containers in every enabled edge region, stores deployment logs, and exposes the API used by the dashboard and CLI. It is not in the production data path for hosted MCP runtime traffic.

PR And Local Environments#

PR previews use the same regional-gateway model as production, backed by the preview edge region catalog. Local developer environments are the exception: they use one direct Container Apps runtime region and no Front Door or regional gateway layer.

Runtime Scale#

Each edge target uses the same self-service runtime shape:

fixed small CPU and memory preset
minReplicas=0
maxReplicas=10
HTTP concurrency autoscale rule

Always-on replicas, larger compute, and higher replica caps require operator-approved custom limits.

Deployment Runs#

Every deploy creates a deployment run with one target per enabled edge region. A run records:

build status
each regional runtime target
revision names
health checks
Azure routing operations
saved logs

The public MCP URL is only updated after the deployment and routing checks pass.

API And CLI Shape#

The dashboard uses the same API surface intended for CLI:

BASH

mcpsail deploy mcp_123

The CLI command uses the platform edge catalog in regional-gateway environments. Region fields may remain in DTOs for compatibility, but they are not a customer-facing deployment choice.