panelica-mcp
OfficialRelated Servers
Alternatives to panelica-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for managing cPanel hosting accounts via UAPI. Enables domains, DNS, email, MySQL, file management, and arbitrary UAPI calls through natural language.1629 npmMIT
- AlicenseCqualityBmaintenanceEnables conversational management of hosting account resources such as apps, domains, databases, files, PHP, SSL, and more through MCP-compatible clients.19414 npmMIT

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.-- AlicenseCqualityBmaintenanceConnect any MCP-compatible AI agent to the full Hostinger platform. Manage VPS, domains, DNS, hosting, WordPress, email, ecommerce, and more through natural language.1006 npmMIT
- AlicenseAqualityDmaintenanceA complete MCP server enabling AI assistants to manage cPanel hosting through natural language, including file, database, email, subdomain, and system operations.161MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage cPanel hosting accounts including DNS, email, databases, SSL, files, security, and more through natural language using cPanel's UAPI and API2.-
TDQS
Scored across 404 tools
Most tools are distinct because names encode the resource category, HTTP method, and endpoint path, so account tools are not easily confused with domain or git tools. However, hundreds of terse generated descriptions like 'List stats' or 'Create disable', opaque hashed suffixes, and a generic `:action` container endpoint create genuine ambiguity in a 404-tool surface.
The naming convention is structurally consistent: `panelica_<category>_<http_verb>_<endpoint_path>` with snake_case throughout. It is not a clean semantic verb_noun scheme, and generated hash suffixes such as `_ht_602debf0` or `_abb3a8b2`, plus an `id_action` placeholder, make some names effectively unreadable.
404 tools is an extreme mismatch for an MCP surface; an agent cannot reasonably browse, compare, or reliably select among this many tools. Even for a comprehensive hosting control panel, the API should be split into focused sub-servers or exposed as curated high-level operations.
The tool surface is remarkably comprehensive, covering CRUD and lifecycle operations across accounts, domains, email, files, git, databases, apps, backups, security, and more. Minor gaps exist—such as redirects and mailing lists lacking full update endpoints and mail queue exposure being limited to stats—but these are not severe relative to the enormous breadth.