Skip to main content
Glama
dwin-gharibi

ArvanCloud MCP Server

by dwin-gharibi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to ArvanCloud MCP Server

No user-submitted related servers found.

    Related Servers

    • E2E Networks Cloud & TIR MCP

      vingupta3
      A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to provision and manage cloud infrastructure and AI/ML workloads—such as GPUs, nodes, storage, networking, databases, Kubernetes, and training/inference resources—through natural language. It also provides a universal REST tool for authenticated access to the underlying cloud API.
      46
      Apache 2.0
    • 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

    • 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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 232 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action, with clear naming prefixes (e.g., arvan_create_server vs arvan_create_dns_record). Despite the large number, the consistent verb_noun pattern and service-specific prefixes make overlapping purposes unlikely.

    Naming Consistency5/5

    All tools follow the arvan_<verb>_<resource> pattern, with consistent verbs (create, list, get, delete, update, etc.) and predictable resource names. Even sub-services like arvan_vod_* and arvan_s3_* adhere to the same convention.

    Tool Count2/5

    232 tools is excessively high for a single server, covering disparate domains (compute, DNS, CDN, S3, VOD, live, security, IaC, git, k8s, notifications). This broad scope would be better served by multiple specialized servers.

    Completeness4/5

    For the intended scope of managing ArvanCloud services, the tool surface is remarkably complete, offering CRUD operations and additional actions for most resources. Minor gaps exist (e.g., missing VOD update for some entities), but the generic arvan_request escape hatch covers any omitted endpoints.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources