websupport-mcp
Related Servers
Alternatives to websupport-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for the adm.tools / ukraine.com.ua hosting API, providing tools to manage hosting services, accounts, sites, and web apps.51MIT
- AlicenseBqualityBmaintenanceMCP server to help manage a WHMCS installation.6225 npm20MIT
- AlicenseBqualityCmaintenanceMCP server for All-Inkl KAS API to manage DNS, domains, mailboxes, mail forwards, and databases, including database dumps via SSH+mysqldump.25MIT
- AlicenseAqualityCmaintenanceMCP server for the DreamHost API that enables DNS management (list, add, remove records) and API metacommands.51MIT
- AlicenseNot gradedqualityFmaintenanceA comprehensive MCP server for managing cPanel web hosting accounts via UAPI, enabling file, database, email, domain, cron, backup, and system monitoring operations.26 npm3MIT
- AlicenseBqualityAmaintenanceMCP server that exposes the Subreg.cz domain registrar SOAP API as tools for LLM agents, enabling domain, DNS, contact, and billing management. Read-only by default, with optional mutating operations.20MIT
TDQS
Scored across 30 tools
Each tool targets a distinct resource-action pair (e.g., list vs. get for hosting, databases, mailboxes, VPS, invoices). Even similar-sounding tools like ws_dns_zone_get and ws_zone_get differ by lookup key (service vs. domain), and ws_service_get vs. ws_hosting_get are clearly scoped by description.
All tools follow the consistent ws_verb_noun snake_case pattern (e.g., ws_dns_record_list, ws_hosting_vhost_get, ws_vps_snapshot_list). No style mixing or vague verbs.
With 30 tools, the surface is heavily over-populated for a typical MCP server. While the scope spans many resource types (DNS, FTP, hosting, DBs, mail, VPS, invoices), the count exceeds the 'heavy' 16-25 band and feels excessive even for a broad control-panel API.
The tool set is almost entirely read-only; there are no create, update, or delete operations for any resource (DNS records, FTP accounts, databases, mailboxes, VPS snapshots, etc.). The descriptions explicitly exclude actions like paying invoices and v1 record CRUD, leaving significant gaps for an expected management surface.