Skip to main content
Glama
zstackio

ZStack MCP Server

Official
by zstackio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ZStack MCP Server

No user-submitted related servers found.

    Related Servers

    • zsvirt-mcp-server by ZSvirt

      zsvirt-mcp-serverofficial

      ZSvirt
      A
      license
      A
      quality
      B
      maintenance
      Enables natural language discovery, inspection, and execution of ZStack's 2000+ cloud management APIs, plus searching and retrieving monitoring metrics, with read-only safety controls and multi-tenant authentication support.
      6
      4
      MIT

    • Cloud Pilot MCP

      vitalemazo
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with natural language control over AWS, Azure, GCP, and Alibaba Cloud infrastructure through dynamic API discovery and execution. Supports 51,900+ cloud operations and includes OpenTofu integration for complete infrastructure lifecycle management.
      3
      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.
      -
    • GreenNode MCP Server by vngcloud

      GreenNode MCP Serverofficial

      vngcloud
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to manage VNG Cloud infrastructure including compute, storage, networking, and Kubernetes resources through natural language commands.
      Apache 2.0
    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.2/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: describe_api provides API details, execute_api calls APIs, search_api finds APIs, and similarly for metrics (get_metric_data, get_metric_summary, search_metric). There is no overlap or ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., describe_api, get_metric_data, search_metric). No deviations or mixed conventions.

    Tool Count5/5

    With 6 tools covering API exploration/execution and metric data retrieval/aggregation/search, the count is well-scoped for a ZStack server. No tool feels extraneous, and the set is not overly sparse.

    Completeness5/5

    The tool set fully covers the domain: users can explore APIs (search, describe), execute any API (including write operations if configured), and access monitoring metrics (raw data, summary/aggregation, search). No obvious gaps hinder common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources