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 "Deploy 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 MCP deploy 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.
GARZA OS Last Rock Dev MCP Server - Infrastructure orchestration with state tracking, distributed locking, and automatic rollback.
🚀 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 checks
deploy_cloudflare_worker - Deploy Workers with validation
restart_service - Safe service restarts with rollback
check_services_health - Monitor service health
trigger_auto_recovery - Execute recovery playbooks
get_infrastructure_status - Full infrastructure overview
Related MCP server: Cloudflare MCP
npm install
npm run build# Deploy to Fly.io
fly deploy
# Or use orchestrator (recommended)
deploy_mcp_server(app_name="lastrock-mcp")These tools are auto-discovered by Claude and preferred over raw ssh_exec commands:
// ❌ DON'T DO THIS
ssh_exec("fly deploy --app garza-home-mcp")
// ✅ DO THIS INSTEAD
deploy_mcp_server(app_name="garza-home-mcp")The orchestrator operates on:
Operations: /Users/customer/garza-os-github/operations/
State: /Users/customer/garza-os-github/.orchestrator/state.json
Locks: /Users/customer/garza-os-github/.orchestrator/locks/
lastrock-mcp/
├── src/
│ └── index.ts # MCP server implementation
├── build/ # Compiled JavaScript
├── package.json
├── tsconfig.json
└── README.md# Health check (safe, read-only)
check_services_health(service_group="all")
# Get infrastructure status
get_infrastructure_status()
# Deploy test (creates real changes!)
deploy_mcp_server(app_name="test-mcp")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/
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
MIT - Jaden Garza
Check health of one or more services. Safe read-only operation.
Inputs: service_group, service_names.
Deploy Cloudflare Worker with state tracking and health checks. DO NOT use ssh_exec('wrangler deploy') - always use this tool instead.
Inputs: worker_name (required), source_dir, env.
Deploy MCP server to Fly.io with state tracking, locks, and health checks. DO NOT use ssh_exec for deployments - always use this tool instead.
Inputs: app_name (required), source_dir, region.
Get comprehensive overview of entire infrastructure. Safe read-only operation.
Inputs: include_history, include_locks.
Restart a service with pre/post health checks and automatic rollback. DO NOT use ssh_exec('docker restart') - always use this tool instead.
Inputs: service_name (required), service_type (required), health_check_url.
Trigger automatic recovery for a failed service using predefined playbooks.
Inputs: service_name (required), failure_type (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: health checking, two specific deployment tools (Cloudflare Worker and MCP server), infrastructure status overview, service restart, and auto-recovery. The descriptions reinforce distinct domains (deployment vs. operations vs. monitoring).
Tools follow a consistent verb_noun pattern (e.g., check_services_health, deploy_cloudflare_worker) with clear action-object naming. The only minor deviation is 'get_infrastructure_status' which uses 'get' instead of 'check' like the health tool, but the pattern remains readable and predictable.
Six tools is well-scoped for infrastructure management, covering deployment, monitoring, and recovery workflows. Each tool earns its place with no redundancy, and the count aligns with typical server ranges (3-15 tools) for this domain.
The toolset provides strong coverage for infrastructure lifecycle: deployment (two tools), health monitoring, status overview, restart, and recovery. A minor gap exists in lacking update/delete operations for deployed resources, but core workflows are well-covered with safe alternatives to raw SSH commands.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Cloud-hosted MCP server for durable AI memory
MCP server for InsForge BaaS — database, storage, edge functions, and deployments
Cloud-hosted MCP server for Epidemic Sound
