F
licenseB
qualityB
maintenanceEnables deploying applications and managing cloud resources in Timeweb Cloud through natural language.
100
11 npm
-
timeweb-mcp-server
by webkoth
Related Servers
Alternatives to timeweb-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables managing DigitalOcean cloud resources, including Droplets, databases, domains, and more, via natural language.12MIT
- 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.87 npm1-
- FlicenseBqualityBmaintenanceEnables natural language management of Proxmox VE VMs and containers, including lifecycle, snapshots, cloud-init, and secure multi-step automation workflows.65-
hostman-mcp-serverofficial
AlicenseAqualityDmaintenanceEnables deploying applications to Hostman, creating VPCs, databases, and floating IPs, and managing VCS providers through natural language prompts.128 npmMIT
PlugLayer MCP Serverofficial
AlicenseCqualityBmaintenanceEnables deploying and managing infrastructure via natural language, including project/domain management, compute nodes, image deployment, and CI/CD integration.70MIT
TDQS
B3.3/5.0
Scored across 97 tools
Disambiguation5/5
All 97 tools follow a clear resource+action pattern, with each tool targeting a unique combination of resource and operation. Even within similar resources (e.g., server vs app), the resource name in the tool name eliminates ambiguity. No two tools appear to perform the same function.
Naming Consistency5/5
All tool names use lowercase snake_case with the standard 'timeweb_' prefix followed by verb_noun structure (e.g., list_servers, create_database, delete_balancer). Verbs are consistently placed at the start of the action. Minor variations like 'check_domain' or 'bind_floating_ip' still follow the same pattern, making the naming highly predictable.
Tool Count2/5
With 97 tools, the server attempts to cover every aspect of the Timeweb cloud platform (servers, databases, K8s, S3, domains, networking, etc.). While each tool maps to a distinct endpoint, the sheer size is overwhelming for an agent to navigate and would likely cause context issues. The tool set would benefit from being split into smaller, focused MCP servers.
Completeness4/5
The tool set provides CRUD operations for most resources (servers, SSH keys, floating IPs, projects, firewalls, balancers, disks, VPCs, images, apps). However, there are notable gaps: databases lack update/resize and backup restore functionality; Kubernetes clusters have no update/scale operations; S3 storages lack get/update. These are minor but real dead ends.
Maintenance
ActivityInactive
ResponsivenessNo issues