hostkey-mcp-server-ru
OfficialRelated Servers
Alternatives to hostkey-mcp-server-ru
No user-submitted related servers found.
Related Servers
AlicenseBqualityAmaintenanceEnables managing Hostkey cloud resources including servers, catalog, power, OS reinstall, network, DNS, snapshots, IPMI, ISO, S3, Remote Hands, billing, and API keys through natural language.132220 npm1MIT- AlicenseBqualityDmaintenanceEnables management of Timeweb Cloud resources including servers, databases, Kubernetes clusters, S3 storage, DNS, SSH keys, and floating IPs through natural language.976 npmMIT
- FlicenseBqualityCmaintenanceEnables deploying applications and managing cloud resources in Timeweb Cloud through natural language.1007 npm-
- FlicenseNot gradedqualityDmaintenanceEnables users to manage Hetzner Cloud resources including servers, load balancers, and volumes through natural language commands. It facilitates infrastructure operations such as resource creation, security configuration, and real-time pricing queries within AI-powered environments.69 npm1-

hostman-mcp-serverofficial
AlicenseAqualityDmaintenanceEnables deploying applications to Hostman, creating VPCs, databases, and floating IPs, and managing VCS providers through natural language prompts.127 npmMIT- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to manage Webdock.io VPS infrastructure through natural language, including provisioning servers, handling snapshots, managing SSH/shell users and scripts, configuring webhooks, and inspecting account or billing details.MIT
TDQS
Scored across 132 tools
The 132-tool surface contains several overlapping or duplicate operations: s3_get_buckets and s3_get_buckets_via_queue are explicitly the same, DNS domain vs. zone tools are subtle, and automated power tools overlap with Remote Hands power requests. Descriptions often clarify intent, but the sheer breadth and multiple delete/billing/S3 variants create real misselection risk.
Most names use readable snake_case with clear verb_noun or resource_noun_action patterns, and S3 tools are consistently namespaced with s3_. There are minor deviations such as power_on, logout, check_task, and call_api_raw, but overall naming is predictable.
132 tools is far beyond a well-scoped MCP surface and exceeds the 50+ extreme-mismatch threshold. While hosting APIs are broad, this many tools in one server is overwhelming and makes tool selection costly even with grouping.
Coverage is very broad: server lifecycle, power, network, DNS, snapshots, ISO, billing, S3, API keys, presets, stock servers, and Remote Hands are all represented. Minor lifecycle gaps remain and call_api_raw exists as a fallback, so the surface is near-complete rather than perfectly closed.