master-mcp
Related Servers
Alternatives to master-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvider-agnostic MCP server for managing heterogeneous infrastructure (SSH, Proxmox VE, Virtualizor, Hetzner Cloud, Cloudflare) via a JSON inventory, exposing tools for VM/container management, DNS, firewalls, and SSH operations.MIT
- AlicenseNot gradedqualityAmaintenanceA single MCP server that gives an AI assistant comprehensive access to manage a homelab, including SSH, Docker, Proxmox, Synology, Cloudflare, and more, with 85 tools and a centralized configuration.MIT
- AlicenseBqualityDmaintenanceEnables conversational management of Hetzner Cloud, DNS, and Storage Box infrastructure through 137 MCP tools for CRUD operations and actions like server power control, DNS zone management, and storage box snapshots.100MIT
- AlicenseNot gradedqualityCmaintenanceProvides a unified MCP interface to manage Cloudflare services including DNS, compute (Workers, KV, D1), storage (R2), AI, security, Radar, and a universal API gateway for any Cloudflare v4 endpoint.MIT
- AlicenseAqualityBmaintenanceEnables infrastructure operations through Claude Code by exposing 195 tools across 7 providers including Coolify, VPS, Hetzner, Namecheap, Cloudflare, Supabase, and GitHub for server management, DNS, cloud resources, and more.93MIT
- AlicenseAqualityCmaintenanceAn MCP server exposing 72 tools across 26 homelab services, enabling LLMs to monitor and manage infrastructure, media, storage, and networking with a single endpoint.16MIT
TDQS
Scored across 3 tools
The three tools target clearly distinct phases: discovering services/instances, discovering available actions, and executing a chosen action. There is no overlap in purpose, and the descriptions reinforce the correct order of use.
All tool names follow a consistent verb_noun snake_case pattern: list_services, list_actions, execute_action. The plural vs. singular noun choice is natural for listing multiple items versus executing one action.
Three tools are well-scoped for a generic admin-action gateway: one for service discovery, one for action discovery, and one for execution. The dynamic action surface avoids tool bloat while covering the server's purpose.
The tool set provides complete lifecycle support for the gateway pattern: list services/instances, list available actions with schemas and safety flags, and execute any action against a chosen instance. No obvious operational gaps exist for the stated domain.