Skip to main content
Glama
vmware-skills

vmware-vks

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vmware-vks

No user-submitted related servers found.

    Related Servers

    • VMware-AIops

      vmware-skills
      A
      license
      A
      quality
      A
      maintenance
      AI-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.
      44
      1,073 PyPI
      78
      MIT

    • VMware_MCP_SERVER

      DanilenkA
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides AI agents with comprehensive access to VMware vSphere operations, including VM management, monitoring, and vSAN read-only monitoring, through a secure Docker environment.
      Apache 2.0

    • vsphere-mcp-extended

      999yurik666
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 24 tools

    Disambiguation5/5

    Every tool targets a distinct resource+action: namespace CRUD vs TKC CRUD are clearly separated, the two kubeconfig tools are explicitly distinguished (Supervisor vs TKC), and storage-policy listing vs PVC storage usage are called out against each other. The three VM Service list tools cover distinct CRDs (snapshots, groups, NICs), and descriptions include 'use X instead' cross-references that remove residual overlap.

    Naming Consistency5/5

    Names follow a predictable snake_case verb_noun pattern: get_*, list_*, create_*, update_*, delete_*, scale_*, upgrade_*, issue_*, check_*. Resource-first nouns (namespace, tkc_cluster, vm_service_*) are used consistently, and the READ/WRITE annotations reinforce the pattern.

    Tool Count4/5

    24 tools sits at the upper end of the ideal range, but the domain genuinely spans compatibility checks, Supervisor health, namespace lifecycle, TKC lifecycle, storage, VM classes, kubeconfigs and VM Service reads, so most tools earn their place. The VM Service list trio is the only area that feels like partial feature creep.

    Completeness4/5

    Namespace and TKC lifecycle coverage is complete (create/read/update/delete plus scale/upgrade), with supporting reads for compatibility, versions, VM classes and storage. Gaps are minor: VM Service is read-only (no snapshot/group creation or deletion), and there is no standalone VM inventory tool despite references to 'your own VM inventory'.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources