Skip to main content
POST
Deploy your tested MCP server to production environments.

Request

string
required
ID of the MCP server to deploy
string
required
Deployment environment. Options: production, staging, development
object
Deployment configuration

Response

boolean
Whether the deployment succeeded
object

Deployment Environments

Production

  • High availability - Multiple instances across regions
  • Auto-scaling - Scales based on demand
  • Monitoring - Full observability and alerting
  • Custom domains - Use your own domain
  • SSL certificates - Automatic HTTPS

Staging

  • Pre-production testing - Test before going live
  • Shared resources - Lower cost than production
  • Limited scaling - Fewer instances
  • Temporary URLs - Auto-generated domains

Development

  • Quick iterations - Fast deploy cycles
  • Single instance - Minimal resources
  • Debug mode - Enhanced logging
  • Auto-cleanup - Removes old deployments

Deployment Status

Check deployment status:
Possible statuses:
  • deploying: Deployment in progress
  • deployed: Successfully deployed and running
  • failed: Deployment failed
  • stopped: Deployment manually stopped

Best Practices

Before Deploying

  1. Test thoroughly - Use /v1/test endpoint
  2. Check performance - Monitor response times
  3. Validate tools - Ensure all tools work correctly
  4. Review logs - Check for errors in development

Production Checklist

  • All tools tested with AI
  • Resource access permissions configured
  • Environment variables set
  • Custom domain configured (if needed)
  • Monitoring alerts configured
  • Backup strategy planned

Rollback Plan

If deployment fails:
  1. Check deployment logs
  2. Fix issues in development
  3. Redeploy with fixes
  4. Or rollback to previous version

Monitoring

Once deployed, monitor your MCP:
  • Health checks - Automatic uptime monitoring
  • Performance metrics - Response times and throughput
  • Error rates - Track failed tool calls
  • Usage analytics - See how AI agents use your MCP