Enables deployment of Cloudflare Workers with validation and health checks, including automatic rollback on failure.
Provides infrastructure orchestration for deploying MCP servers to Fly.io with state tracking, distributed locking, health monitoring, and automatic rollback capabilities.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Last Rock MCPdeploy the new analytics worker to Cloudflare"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Last Rock MCP
GARZA OS Last Rock Dev MCP Server - Infrastructure orchestration with state tracking, distributed locking, and automatic rollback.
Features
π Infrastructure Orchestration
Deploy MCP servers to Fly.io with state tracking
Deploy Cloudflare Workers with health checks
Restart services with automatic rollback
Comprehensive health monitoring
Auto-recovery playbooks
π Safety & Reliability
Distributed locking prevents concurrent operations
State tracking in deployments.json
Pre/post deployment health checks
Automatic rollback on failure
Full operation audit trail
π οΈ Tools Included
deploy_mcp_server- Deploy to Fly.io with safety checksdeploy_cloudflare_worker- Deploy Workers with validationrestart_service- Safe service restarts with rollbackcheck_services_health- Monitor service healthtrigger_auto_recovery- Execute recovery playbooksget_infrastructure_status- Full infrastructure overview
Installation
For Development
For Production (Fly.io)
Usage in Claude
These tools are auto-discovered by Claude and preferred over raw ssh_exec commands:
Configuration
The orchestrator operates on:
Operations:
/Users/customer/garza-os-github/operations/State:
/Users/customer/garza-os-github/.orchestrator/state.jsonLocks:
/Users/customer/garza-os-github/.orchestrator/locks/
Architecture
Testing
Integration
This MCP server integrates with GARZA OS orchestrator:
Orchestrator:
/Users/customer/garza-os-github/orchestrator/Operations:
/Users/customer/garza-os-github/operations/Documentation:
/Users/customer/garza-os-github/docs/
Why This Matters
Before:
Raw SSH commands
No state tracking
No safety checks
No rollback capability
Manual recovery
After:
Managed orchestration
Full state tracking
Automatic health checks
Automatic rollback
Auto-recovery playbooks
Related
License
MIT - Jaden Garza