A
licenseC
qualityD
maintenanceEnables AI assistants to deploy and manage applications, databases, object storage, VMs, DNS, and infrastructure on the Liara cloud platform through natural language commands.
100
24 npm
7
MIT
ArvanCloud MCP Server
by dwin-gharibi
Related Servers
Alternatives to ArvanCloud MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform DevOps tasks including Kubernetes management, cloud provider operations, CI/CD, security scanning, and infrastructure monitoring through natural language.MIT
GreenNode MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI assistants to manage VNG Cloud infrastructure including compute, storage, networking, and Kubernetes resources through natural language commands.Apache 2.0- AlicenseNot gradedqualityCmaintenanceProvides 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.3MIT
- AlicenseCqualityDmaintenanceEnables AI assistants to manage multi-cloud resources (AWS, Azure, GCP) including resource operations, cost analysis, monitoring metrics, and security compliance checks through natural language commands.265 npm2MIT
- FlicenseCqualityDmaintenanceEnables AI assistants to manage Alibaba Cloud resources via natural language, with explicit tools for common services and a universal API invoker for full cloud coverage.92-
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