A
licenseA
qualityA
maintenanceAI-powered VMware NSX DFW microsegmentation and security. Manage distributed firewall policies, security groups, Traceflow, and IDPS with 20 MCP tools.
22
341 PyPI
4
MIT
vmware-nsx
Related Servers
Alternatives to vmware-nsx
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAI-powered VMware vSphere with Tanzu (VKS) management. Create and manage Supervisor Namespaces and TanzuKubernetesClusters with 20 MCP tools.23434 PyPI5MIT
- AlicenseAqualityAmaintenanceAI-powered VMware storage management for vSphere. Manage datastores, iSCSI targets, and vSAN via natural language with 11 MCP tools.14499 PyPI3MIT
- 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
- AlicenseCqualityBmaintenanceEnables managing HPE Juniper Security Director Cloud through 368 MCP tools covering firewall and NAT policies, security objects, IDP, devices, licenses, templates, and tenant administration via natural language.368MIT
- 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.44623 PyPI74MIT
TDQS
A4.4/5.0
Scored across 33 tools
Disambiguation5/5
Every tool pairs a distinct NSX resource (segment, Tier-1 gateway, NAT rule, static route, IP pool, transport node, edge cluster) with a distinct action (list/get/create/update/delete/status). Even the two port-related tools are cleanly separated: get_segment_port_for_vm maps a VM to a segment, while get_logical_port_status reports realized port state on a segment.
Naming Consistency5/5
All tool names are lowercase snake_case following a consistent verb_noun pattern: list_* for collection reads, get_* for detail/status reads, and create_*/update_*/delete_* for mutations. The only slightly unusual name, configure_tier0_bgp, still follows the verb_noun convention and is unambiguous.
Tool Count3/5
At 33 tools, this is well above the ideal 3-15 range and past the 16-25 'heavy' band. However, the NSX domain is broad and every tool maps to a real resource/action with no obvious duplicates, so the large surface feels heavy rather than bloated.
Completeness4/5
Core lifecycles are covered for segments, Tier-1 gateways, NAT rules, static routes, and IP pools, with health/status reads and VM-to-segment lookup filling out the domain. Minor gaps exist: BGP neighbor creation is not exposed, NAT rules and static routes have no update operation (requiring delete+recreate), and Tier-0 gateway creation is intentionally out of scope.
Maintenance
ActivityNo data
ResponsivenessResponsive