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
      623 PyPI
      74
      MIT

    • VMware_MCP_SERVER

      DanilenkA
      A
      license
      Not graded
      quality
      B
      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.3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action — Supervisor, namespace, TKC, storage, kubeconfigs, VM Service — so there is no duplicate functionality. The only spots where an agent might hesitate are the two kubeconfig tools and check_vks_compatibility vs get_supervisor_status, but the descriptions draw clear boundaries.

    Naming Consistency4/5

    The dominant verb_noun pattern (list_*, get_*, create_*, delete_*) is consistent and readable. Deviations: get_supervisor_kubeconfig and get_tkc_kubeconfig are write-oriented credential actions labeled as get_, and get_tkc_available_versions returns a list rather than a single object.

    Tool Count3/5

    23 tools is a large surface and sits in the 16–25 range that feels heavy; several VM Service inspection tools could arguably be bundled. That said, the core namespace/TKC lifecycle and supporting lookups mostly justify each tool's presence.

    Completeness4/5

    The namespace and TKC lifecycles are thoroughly covered: compatibility, status, CRUD, scale/upgrade/delete, versions, VM classes, storage policies, and kubeconfigs. Gaps are peripheral — no VirtualMachine list/create/delete, no Harbor repository listing, no namespace permission management — and don't block the primary workflows.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources