Skip to main content
Glama
veg-salad

vcenter-mcp

by veg-salad
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to vcenter-mcp

No user-submitted related servers found.

    Related Servers

    • nutanix-mcp

      veg-salad
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Nutanix infrastructure (VMs, hosts, storage, alerts, etc.) using natural language through GitHub Copilot. Supports Prism Element, Prism Central, and Nutanix Move with secure credential storage.
      MIT

    • vmware-knight

      CyberKnightLabs
      A
      license
      A
      quality
      A
      maintenance
      Enables AI-assisted management of vCenter Server and standalone ESXi hosts, including lifecycle, deployment, guest operations, cluster management, datastore browsing, alarms, and investigations through natural language.
      60
      MIT

    • 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
      980 PyPI
      74
      MIT

    • vcf-mcp-sddc-vc

      rajuatmakuri5
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language interaction with VMware SDDC Manager and vCenter APIs through MCP tools, allowing users to query workload domains, VMs, clusters, and more.
      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

    B3/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools target distinct resources with clear prefixes (get_ vs list_), though the cluster CPU/memory tools have overlapping scopes (rollups, periods, windows) that could cause confusion despite different time dimensions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (get_<resource>, list_<resources>), using snake_case throughout. Suffixes like _ws are used uniformly for web services endpoints, maintaining predictability.

    Tool Count4/5

    33 tools is slightly above the typical range for a focused server, but the vSphere domain has many resource types, making the count justifiable. Each tool appears necessary for comprehensive inventory coverage.

    Completeness3/5

    The tool set is entirely read-only (get/list), lacking any create, update, or delete operations. For an inventory or monitoring server this may be complete, but for full vCenter management, significant lifecycle operations are missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources