A
licenseA
qualityD
maintenanceMCP server for managing cPanel hosting accounts via UAPI. Enables domains, DNS, email, MySQL, file management, and arbitrary UAPI calls through natural language.
16
34 npm
MIT
ecp-mcp-server
by EpicLabs23
Related Servers
Alternatives to ecp-mcp-server
No user-submitted related servers found.
Related Servers
panelica-mcpofficial
AlicenseCqualityAmaintenanceEnables natural language interaction with a Panelica hosting panel to manage domains, SSL, databases, services, and more through any MCP client.404241 npm2MIT
agenthost MCP serverofficial
FlicenseNot gradedqualityCmaintenanceAgent-first web hosting driven entirely through a remote MCP server, enabling full hosting management via natural language with OAuth or token authentication.-- AlicenseCqualityDmaintenanceConnect any MCP-compatible AI agent to the full Hostinger platform. Manage VPS, domains, DNS, hosting, WordPress, email, ecommerce, and more through natural language.1000MIT
- AlicenseAqualityDmaintenanceA complete MCP server enabling AI assistants to manage cPanel hosting through natural language, including file, database, email, subdomain, and system operations.161MIT
- AlicenseBqualityCmaintenanceA comprehensive MCP server for managing cPanel hosting accounts through AI assistants. It supports DNS, email (DKIM/SPF), databases, domains, SSL, PHP, cron jobs, security, Git deployment, and more.10026ISC
TDQS
C2.9/5.0
Scored across 194 tools
Disambiguation4/5
Most tools are clearly distinct by resource area and action, and the descriptions carefully call out subtle differences (e.g. ecp_apps_directory_tree vs ecp_files_directory_tree, ecp_ssl_request vs ecp_ssl_update vs ecp_ssl_apply). A few near-duplicates exist—ecp_files_copy vs ecp_files_copy_multiple and ecp_files_move vs ecp_files_move_multiple—but they are rare and understandable.
Naming Consistency4/5
The ecp_<area>_<verb>_<noun> pattern is followed almost everywhere, making names very predictable. Minor deviations include ecp_network_port_maps (noun-first), ecp_network_domain_port_maps, and ecp_files_is_directory_exists (awkward verb phrase), but these do not undermine the overall uniformity.
Tool Count1/5
194 tools is an extreme count for a single MCP server. Even accounting for the broad hosting-panel domain (files, four database engines, SSL, nginx, git, supervisor, cron, notifications, backups), this volume creates a massive selection surface and will overwhelm agents. The count alone warrants the lowest score.
Completeness4/5
The tool surface is remarkably comprehensive: apps, domains, DNS, nginx, files, four database engines with user/privilege/backup/restore operations, SSL, supervisor, crontab, asdf, git webhooks, notifications, and storage. The only notable gap is the explicitly blocked ability to run custom commands directly (ecp_apps_save_custom_command mentions 'run' isn't exposed yet), which is a stated intentional limitation rather than an oversight.
Maintenance
ActivityActive
ResponsivenessNo issues