Skip to main content
Glama
Sign In
vmware-vks

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
      398 PyPI
      87
      MIT

    • VMware_MCP_SERVER

      DanilenkA
      A
      license
      Not graded
      quality
      D
      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 25 tools

    Disambiguation5/5

    Every tool targets a distinct resource+action pair: TKC vs Namespace vs Supervisor vs VM Service vs Harbor vs access introspection are cleanly separated, and the near-neighbours (list_supervisor_storage_policies vs list_namespace_storage_usage, issue_supervisor_kubeconfig vs issue_tkc_kubeconfig, check_vks_compatibility vs get_supervisor_status) are explicitly disambiguated in their descriptions. The heavy cross-referencing ('run X first', 'use Y instead') actively steers an agent away from misselection.

    Naming Consistency5/5

    All 25 names are snake_case and verb-led (list_/get_/create_/update_/delete_/scale_/upgrade_/issue_/check_), with resource prefixes that group the surface predictably (tkc, namespace, supervisor, vm_service, vm_class). The only mild deviation is get_access_info, which still follows verb_noun.

    Tool Count3/5

    25 tools sits at the top of the 'feels heavy' band, driven by four distinct sub-domains (TKCs, namespaces, Supervisor, VM Service) plus Harbor and access introspection. Each tool is defensible on its own, but the surface is large enough that discovery and selection cost is real for an agent.

    Completeness4/5

    TKC and namespace lifecycles are essentially complete (list/get/create/scale/upgrade/delete and list/get/create/update/delete respectively), with sensible preview-confirm semantics on destructive writes. Gaps are secondary: the VM Service surface is read-only (no create/snapshot/delete), Harbor exposes only status (no repositories/images), and there is no node-pool add/remove beyond worker-count scaling.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources