plesk-mcp
Related Servers
Alternatives to plesk-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables automated cPanel management including subdomain provisioning, FTPS deployment, MySQL database management, snapshot backups, and remote file operations via MCP.1MIT
- AlicenseNot gradedqualityFmaintenanceA comprehensive MCP server for managing cPanel web hosting accounts via UAPI, enabling file, database, email, domain, cron, backup, and system monitoring operations.21 npm3MIT
- AlicenseBqualityCmaintenanceEnables file operations, npm package management, and configuration checking through MCP.106 npm1MIT
- AlicenseAqualityDmaintenanceEnables reading, writing, editing, searching, running commands, transferring files, and using git on a remote Linux server over SSH via MCP tools.223AGPL 3.0
- AlicenseAqualityDmaintenanceMCP server for managing remote servers via SSH, enabling command execution, file transfer, rsync, tunnels, health checks, backups, and database operations.172,541 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for managing cPanel accounts and WHM servers via UAPI/WHM APIs. Supports domains, DNS, email, MySQL, files, cron, SSL, PHP, backups, and hosting accounts across multiple environments with read-only mode and security controls.MIT
TDQS
Scored across 3 tools
The three names hint at different intents (listing servers, project metadata, diagnostics), but every description is the identical 'No configuration is loaded. Returns the configuration error.', giving an agent no way to know what each tool actually returns or when to prefer one over another. `project_info` in particular is ambiguous in a Plesk context (which project? which info?).
`servers_list` uses a noun_plural + verb suffix, `project_info` is noun + attribute, and `doctor` is a bare noun with no resource qualifier. Three tools, three different conventions, with no shared verb_noun pattern to predict new tools from.
Three tools is borderline thin: a Plesk management server would need domain, mail, database, and subscription operations, and these three read more like bootstrap/diagnostic utilities than a scoped surface. The count itself isn't extreme, but it feels undersized for the apparent domain.
The implied domain is Plesk hosting administration, yet the surface offers no create/update/delete or even read operations for domains, websites, mailboxes, or databases — only a health check, a server list, and an info call. There are significant gaps that would block any real management workflow.