timeweb-mcp-server
Related Servers
Alternatives to timeweb-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.973 npmMIT

hostman-mcp-serverofficial
AlicenseAqualityDmaintenanceEnables deploying applications to Hostman, creating VPCs, databases, and floating IPs, and managing VCS providers through natural language prompts.1211 npmMIT
hostkey-mcp-serverofficial
AlicenseBqualityBmaintenanceEnables 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.1320MIT
PlugLayer MCP Serverofficial
AlicenseCqualityBmaintenanceEnables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.70MIT- AlicenseCqualityDmaintenanceEnables AI assistants to deploy and manage applications, databases, object storage, VMs, DNS, and infrastructure on the Liara cloud platform through natural language commands.10024 npm7MIT
- AlicenseAqualityCmaintenanceEnables managing DigitalOcean cloud resources, including Droplets, databases, domains, and more, via natural language.12MIT
TDQS
Scored across 245 tools
With 245 tools, several groups have ambiguous boundaries: list_all_project_servers vs list_project_servers, v1/v2 pairs like list_mailboxes/list_mailboxes_v1, and create_database vs create_database_instance. Despite descriptions, the sheer scale and near-identical names make misselection likely.
Most tools follow verb_noun, but inconsistencies exist: get_vpcs (a list), edit_api_key instead of update_, and preset getters mix get_ and list_ (get_allowed_presets vs list_balancer_presets). The pattern is readable but not uniform.
245 tools is extreme and far beyond typical MCP servers. Many are redundant (v1/v2, list_all_project vs list_project), inflating the count without adding distinct capability.
The toolset covers the lifecycle of most resource types (servers, DB, K8s, S3, domains, mail, networking). Minor gaps exist (e.g., delete_database_instance, reinstall server, get_dns_record singular), but core workflows are largely supported.