Request
ID of the MCP server to deploy
Deployment environment. Options:
production
, staging
, development
Deployment configuration
Response
Whether the deployment succeeded
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:- deploying: Deployment in progress
- deployed: Successfully deployed and running
- failed: Deployment failed
- stopped: Deployment manually stopped
Best Practices
Before Deploying
- Test thoroughly - Use
/v1/test
endpoint - Check performance - Monitor response times
- Validate tools - Ensure all tools work correctly
- 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:- Check deployment logs
- Fix issues in development
- Redeploy with fixes
- 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