A
licenseB
qualityB
maintenanceEnables managing Hostkey .ru cloud account resources via natural language, including servers, ordering, power control, OS reinstall, networking, DNS, snapshots, and billing.
132
MIT
hostkey-mcp-server
OfficialRelated Servers
Alternatives to hostkey-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables management of Timeweb Cloud resources including servers, databases, Kubernetes clusters, S3 storage, DNS, SSH keys, and floating IPs through natural language.976 npmMIT
- FlicenseBqualityBmaintenanceEnables deploying applications and managing cloud resources in Timeweb Cloud through natural language.1008 npm-
- AlicenseNot 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.85 npm1-
hostman-mcp-serverofficial
AlicenseAqualityDmaintenanceEnables deploying applications to Hostman, creating VPCs, databases, and floating IPs, and managing VCS providers through natural language prompts.128 npmMIT- AlicenseAqualityCmaintenanceEnables managing DigitalOcean cloud resources, including Droplets, databases, domains, and more, via natural language.12MIT
TDQS
B3.2/5.0
Scored across 132 tools
Disambiguation3/5
Many tools are distinct, but there are overlapping concepts like DNS zones vs. domains, and multiple tools for listing buckets (s3_get_buckets vs s3_get_buckets_via_queue). The sheer volume (132) increases the chance of misselection despite clear descriptions.
Naming Consistency4/5
Most tools follow a verb_noun pattern (e.g., get_invoice, create_api_key, delete_dns_record). However, there are inconsistencies like 'logout', 'port_on/off' vs 'power_on/off', and some tools use different verb forms (list vs get, create vs add) for similar operations.
Tool Count1/5
132 tools is extreme and overwhelming for an MCP server. Even a comprehensive hosting API would be better split into multiple focused servers. The count far exceeds practical usability and increases cognitive load for agents.
Completeness4/5
The tool surface covers a wide range of domains: server management, billing, DNS, S3, remote hands, and API key management. There is a raw API call tool for gaps, making the coverage quite comprehensive. Minor gaps exist (e.g., no direct server hostname update tool), but they are addressable.
Maintenance
ActivityMaintained
ResponsivenessNo issues