Skip to main content
Glama
ZSvirt

zsvirt-mcp-server

Official
by ZSvirt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to zsvirt-mcp-server

No user-submitted related servers found.

    Related Servers

    • ZStack MCP Server by zstackio

      ZStack MCP Serverofficial

      zstackio
      A
      license
      A
      quality
      D
      maintenance
      Enables AI to dynamically search, describe, and execute 2000+ ZStack Cloud APIs, plus query monitoring metrics and data.
      6
      11
      MIT

    • CloudStack MCP Server

      mozg31337
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive management of CloudStack infrastructure through natural language, providing access to over 735 API methods for virtual machines, networking, and storage. It features enterprise-grade security with a safety confirmation system for destructive operations and extensive API coverage.
      -
    • PlugLayer MCP Server by pluglayer

      PlugLayer MCP Serverofficial

      pluglayer
      A
      license
      C
      quality
      B
      maintenance
      Enables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.
      70
      MIT
    • GreenNode MCP Server by vngcloud

      GreenNode MCP Serverofficial

      vngcloud
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage VNG Cloud infrastructure including compute, storage, networking, and Kubernetes resources through natural language commands.
      Apache 2.0

    • 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

    A4.1/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search_api/describe_api/execute_api form an API discovery-to-execution pipeline, while search_metric/get_metric_data/get_metric_summary form a metrics retrieval pipeline. Even the two 'search' tools are unambiguously separated by their targets (APIs vs metrics).

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern: search_, describe_, execute_, get_. The repetition of 'search' and 'get' is intentional and predictable, with the noun disambiguating the target.

    Tool Count5/5

    Six tools is a well-scoped count for a server focused on two complementary workflows: API introspection/execution and metric querying. Each tool earns its place without redundancy or bloat.

    Completeness5/5

    The API workflow is complete with search, describe, and execute, covering discovery through invocation. The metrics workflow is also complete with search, raw data retrieval, and aggregated summary, with no obvious dead ends or missing operations.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources