Deploy an MCP Server to Production

For a shared remote server, use Streamable HTTP rather than treating a development stdio process as a web service.

Deployment checklist

• HTTPS and a stable hostname.
• Authentication/authorization at the MCP boundary.
• Secrets from a deployment secret store.
• Health/readiness endpoints at the infrastructure layer.
• Request, result, timeout, and concurrency limits.
• Structured logs/traces with secret redaction.
• Staging environment and rollback plan.

Separate protocol from business services

Keep MCP handlers thin. Deployment should not force your domain logic to depend on transport details.

Roll out gradually

Start with read-only tools and a limited caller set. Add mutations only after authorization, observability, and approval behavior have been exercised.