Nutanix MCP Server
Related Servers
Alternatives to Nutanix MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables querying Nutanix infrastructure (VMs, hosts, storage, alerts, etc.) using natural language through GitHub Copilot. Supports Prism Element, Prism Central, and Nutanix Move with secure credential storage.MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, network, high availability, replication, SDN, and node administration.10026 npmMIT
- AlicenseAqualityAmaintenanceGoverned AI-ops MCP server for Nutanix Prism Central v4 REST API, offering 47 read/write tools for clusters, VMs, storage, network, catalog, data protection, alerts, and LCM upgrades with built-in audit, budget, and risk-tier governance.51MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.MIT

Nutanix V4 API MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceExpose Nutanix V4 APIs as tools callable by AI assistants — Claude, Cursor, and any MCP-compatible client.19Apache 2.0- AlicenseAqualityDmaintenanceMCP 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
TDQS
Scored across 28 tools
Most tools target distinct resources or actions. However, list_vms and pe_list_vms both list VMs but from different scopes (Prism Central vs Prism Element), which could cause confusion if descriptions are not read carefully. Similarly, get_cluster and pe_get_cluster_info overlap, but descriptions clarify the source difference.
The naming convention is mixed: some tools use verb_noun (create_vm, list_vms), some use generate_*_report, and there's a pe_ prefix for Prism Element tools. While each sub-pattern is consistent internally, the overall set lacks a uniform style, with verbs like 'power_on' and 'generate' alongside 'get' and 'list'.
28 tools is somewhat high for an MCP server, but given the complexity of Nutanix infrastructure covering clusters, VMs, storage, networking, and both Prism Central and Element APIs, the number is justifiable. It feels slightly heavy but not excessive.
The tool set covers many core Nutanix operations (CRUD for VMs, listing resources, generating reports) but has notable gaps: no update or delete for VMs, no VM migration, no backup/restore, and limited network configuration beyond listing subnets. This leaves agents with dead ends for common tasks.