vmware-knight
Related Servers
Alternatives to vmware-knight
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables natural language interaction with VMware SDDC Manager and vCenter APIs through MCP tools, allowing users to query workload domains, VMs, clusters, and more.MIT
- AlicenseNot gradedqualityCmaintenanceEnables VMware vCenter management via MCP, adding real-time and historical performance monitoring, VM lifecycle operations, snapshots, ISO mounting, and network/host management through natural language.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants such as Claude, Gemini, and GPT to connect directly to VMware ESXi and vCenter hosts over stdio JSON-RPC. Provides full virtual machine lifecycle management (create, clone, delete, power on/off) plus real-time CPU, memory, storage, and network performance monitoring, with API key authentication and SSL/TLS support.MIT
- AlicenseCqualityBmaintenanceEnables AI assistants to query Cisco Catalyst SD-WAN Manager (vManage) in natural language for fabric inventory, control plane, OMP, BFD, routing, templates, policies, alarms, and broader REST API operations, with read-only defaults and opt-in controlled changes.832MIT
- AlicenseAqualityAmaintenanceAI-powered VMware vCenter/ESXi monitoring and operations. 20 MCP tools for inventory queries, health monitoring, VM lifecycle management, fast provisioning (Linked Clone, OVA, template deploy), snapshot management, and datastore browsing. Supports vSphere 6.5–8.0. Works with local models via Ollama/LM Studio.44361 PyPI82MIT
- FlicenseNot gradedqualityBmaintenanceEnables helpdesk operators to manage Horizon user sessions, restart or log off desktops, monitor pool health, and diagnose performance issues through natural language.-
TDQS
Scored across 60 tools
Each tool has a clearly distinct purpose, with descriptions that explicitly differentiate similar operations (e.g., deploy_vm_from_ova vs. deploy_vm_from_template vs. vm_clone). Even closely related tools like vm_guest_exec and vm_guest_exec_output are clearly separated by their output-capturing behavior.
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_vcenter_alarms, create_drs_rule, vm_power_on, vm_guest_upload). The naming is uniform and predictable across all 60 tools.
60 tools is high, but the server covers an extensive domain: VM lifecycle, snapshots, cloning, guest operations, cluster management, DRS rules, networking, datastore browsing, monitoring, TTL, and a plan system. Each tool has a specific role, so the count is defensible, though it may feel heavy for simple use cases.
The tool set provides comprehensive coverage of vSphere operations, including CRUD for VMs, snapshots, cloning, guest execution, cluster and DRS management, network portgroups and VMKs, datastore browsing, and monitoring bundles. Minor gaps exist (e.g., no explicit VM rename or vCenter host addition), but they do not block core workflows.