hmc-mcp
Related Servers
Alternatives to hmc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceMCP server for IBM Concert Operate that exposes the full v2 REST API as callable tools, enabling AI assistants to manage alerts, incidents, policies, runbooks, and more.975 npm1MIT
- AlicenseAqualityCmaintenanceMCP server for Nutanix Prism Central v4 REST API, enabling AI agents to list and inspect VMs, control VM power state, list clusters, read alerts, and list subnets.8MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with QUADS infrastructure systems via API, enabling resource management and automation through LLM applications.MIT
- FlicenseAqualityDmaintenanceAI-powered MCP server for enterprise OpenShift/Kubernetes cluster management, providing diagnostic tools, RAG knowledge retrieval, and autonomous remediation recommendations.9-
- AlicenseNot gradedqualityCmaintenanceAn MCP server for managing home lab VMs and PNETLab topologies, enabling AI agents to power VMs, handle snapshots, and verify device configurations with explicit allowlists and confirmation gating.MIT
- 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
TDQS
Scored across 101 tools
Most tools have clearly distinct purposes, but minor overlaps exist: hmc_find_system duplicates hmc_systems(name=...), hmc_provision_lpar overlaps with the create+adapter+storage sequence, and hmc_list_resources is a generic catch-all. Detailed descriptions mitigate most confusion.
The vast majority follow hmc_<verb>_<noun> (list, create, delete, modify, power, add, remove, backup, restore, install, migrate, get, set). A few tools use bare plural nouns (hmc_systems, hmc_lpars, hmc_vios) or noun phrases (hmc_console_info, hmc_capacity_report), creating minor inconsistency, but the pattern remains predictable.
At 101 tools, this is far beyond the 3-15 tool sweet spot. Even for a complex domain like HMC management, the sheer number overwhelms agents and makes tool selection costly. The server would benefit from consolidation, e.g., merging some list/get operations into single parameterized tools.
The tool set covers a remarkably broad range: LPAR/VIOS lifecycle, power, storage, networking, users, updates, metrics, migrations, and profiles. However, there are obvious gaps: no delete/modify for volume groups or virtual disks, no create for shared memory pools, no management for virtual switches beyond listing, and no CRUD for clusters/SSPs themselves.