A
licenseA
qualityD
maintenanceMCP server for deploying projects to multiple cloud platforms (Vercel, Railway, Neon, MongoDB Atlas, Docker) and running local dev servers, with orchestration for full-stack deployments.
8
MIT
Last Rock MCP
by itsablabla
Related Servers
Alternatives to Last Rock MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server that orchestrates image generation across multiple pipelines (OpenAI, Recraft, Midjourney) with durable memory for project context, running on Cloudflare Workers.1Apache 2.0
- AlicenseAqualityDmaintenanceMCP server that wraps Docker, Caddy, and GitHub Actions operations on a remote VPS, enabling Claude to take read-then-write-with-confirmation infrastructure actions over SSH with a service allowlist and audit-trail-friendly responses.8MIT
- FlicenseNot gradedqualityCmaintenanceA Cloudflare Workers-based MCP server that enables secure remote connections using built-in OAuth authentication via Cloudflare Access. It provides identity-based access control for MCP tools and supports persistent state management through Durable Objects and SSE.-
- AlicenseNot gradedqualityDmaintenanceEnables creation and deployment of MCP servers on Cloudflare Workers, with local testing and one-command deployment.10 npm5MIT
- AlicenseNot gradedqualityNot gradedmaintenanceAn interactive MCP server for controlling a live dashboard deployed on Cloudflare Workers, enabling real-time updates to features, stats, and messages via MCP tools.MIT
TDQS
A3.8/5.0
Scored across 6 tools
Disambiguation5/5
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).
Naming Consistency4/5
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.
Tool Count5/5
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.
Completeness4/5
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.