tport-cloud-mcp
Related Servers
Alternatives to tport-cloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceEnables users to inspect and manage domains, DNS records (including A, AAAA, CNAME, MX, TXT and more), HTTP forwards, invoices and dynamic DNS through a hosting provider's API, with previewed change plans, conflict detection, backups and independent readback before writes. Offers DNS shortcuts such as website setup, verification records, bulk IP replacement, zone import/export and backup restore, exposed via local stdio or authenticated Streamable HTTP for a central gateway.27MIT

Hostodo MCPofficial
AlicenseBqualityDmaintenanceManage Hostodo VPS infrastructure from MCP clients and AI agents with scoped tokens and audit logs.471MIT- AlicenseNot gradedqualityDmaintenanceEnables management of TuxCare ePortal resources such as servers, feeds, registration keys, patchsets, and users through the ePortal API, with support for basic and API key authentication.13 npmMIT
- AlicenseAqualityBmaintenanceEnables managing Zone.ee/Zone.eu hosting through the ZoneID API v2 from Claude or any MCP client: listing and editing domains, DNS records, mail forwarders, webhosting, MySQL, cron jobs and SSL certificates, with confirmation before writes. A spec-aware generic request tool covers the remaining endpoints such as mailboxes, SSH, FTP, Redis, PM2 and cloud VPS.19MIT
- AlicenseBqualityDmaintenanceEnables management of Timeweb Cloud resources including servers, databases, Kubernetes clusters, S3 storage, DNS, SSH keys, and floating IPs through natural language.977 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to autonomously govern cloud hosting infrastructure and billing workflows, including provisioning, invoices, wallet credits, support tickets, and catalog management through 35 tools with JSON:API response hydration.35MIT
TDQS
Scored across 20 tools
Each tool targets a distinct resource+action pair, and the DNS/databases namespacing makes boundaries obvious. Minor soft spots: `power` is a generic name that could be confused with lifecycle ops like `resize_server`, and `dns_add_record` doubles as an edit tool (via `replace`), blurring add vs. update.
Two conventions coexist: unprefixed verb_noun for servers/billing/orders (list_servers, create_server, get_billing) and a resource-prefixed form for DNS and databases (dns_list_zones, databases_set_allow). `power` breaks both patterns as a bare noun with no object or verb, making the scheme only partially predictable.
Twenty tools spread across four product areas (servers, DNS, databases, billing) — roughly 4-6 per area, and each one covers a real operation rather than a redundant variant. Slightly heavy overall, but the breadth of the domain justifies the count.
Servers have full lifecycle (list/get/create/resize/power/delete plus order tracking), DNS covers zone and record create/read/delete, and databases cover create/read/allow-list/delete. Gaps remain: no server rebuild/SSH-key management despite `create_server` referencing ssh_keys, and no database scaling, backup, or user management.