F
licenseB
qualityC
maintenanceEnables natural language management of Naver Cloud Platform infrastructure (servers, VPCs, subnets, load balancers, databases) via Claude Desktop.
23
-
ncloud-mcp-server
by sjk4425
Related Servers
Alternatives to ncloud-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables conversational management of Naver Cloud Platform infrastructure through Claude Desktop, allowing users to create, query, and manage cloud resources like servers, VPCs, load balancers, and databases using natural language.23-
- AlicenseCqualityAmaintenanceMCP server for managing Naver Cloud Platform Government Cloud infrastructure via natural language. Provides ~877 tools across compute, network, database, storage, security, and other services.10084 npm1MIT
GreenNode MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage VNG Cloud infrastructure including compute, storage, networking, and Kubernetes resources through natural language commands.Apache 2.0- AlicenseBqualityAmaintenanceEnables 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.46Apache 2.0
- 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.267 npm2MIT
TDQS
B3/5.0
Scored across 1300 tools
Disambiguation2/5
The 1300-tool surface contains many overlapping or near-duplicate operations across legacy and newer services: legacy Object Storage vs Ncloud Storage bucket tools, Certificate Manager 1.0 vs 2.0, Cloud Outbound Mailer vs SENS, and normal/force/by-id delete variants. Service-prefixed names and long descriptions help somewhat, but several tools still have unclear boundaries that invite misselection.
Naming Consistency4/5
Most tools follow a predictable snake_case ncloud_<service>_<verb>_<resource> pattern, such as ncloud_kms_create_key and ncloud_dns_list_domains. Some older/generic tools omit a service prefix, and abbreviations like ncs, cm2, ses, and cdss create minor inconsistency, but the overall convention remains readable and stable.
Tool Count1/5
A single MCP server exposing 1300 tools is an extreme mismatch for practical agent use. Even if each tool maps to a real API, the set is far too large to navigate, select from, or maintain coherently without heavy external structuring.
Completeness4/5
The surface covers an unusually broad slice of Ncloud services, including compute, networking, databases, storage, CDN/DNS, KMS, secrets, IAM, monitoring, and deployment tooling. There are some explicit gaps (e.g., IAM role target endpoints, console-only operations) and legacy paths, but core lifecycle operations are largely present.
Maintenance
ActivityActive
ResponsivenessNo issues