cpanel_uapi

Run one cPanel operation against the cPanel account behind one of the caller's hosting services and return a normalized result { ok, data, errors[], warnings[] }. Discovery flow: list_cpanel_operations (optionally with `search`) to find the module, then get_cpanel_module to see its functions and parameters, then this tool to execute one. module is a cPanel UAPI module (e.g. "Email"); function is an operation in that module (e.g. "list_pops"); params is a JSON object of that operation's parameters. Only modules JetHost has enabled are available — an unknown or disabled module returns an error. A module the caller's key does not grant returns error="module_not_granted" together with granted_modules, the modules that key MAY use on that service. get_cpanel_module's listing marks each function with a leading "!" for mutating (write/delete) functions or a leading space for read-only ones — check that marker and confirm with the user before running a mutating call. The cPanel account is resolved from the owned service; a service the caller does not own returns error=not_found. Requires the cpanel:uapi scope. data is the UAPI payload; cPanel base64-encoded fields (e.g. DNS::parse_zone dname_b64/data_b64/text_b64) are decoded to readable values under the same key without the _b64 suffix. TIP — writing PHP source: a WAF on the request path rejects any params carrying the literal "<?php" (case-insensitive; e.g. Fileman::save_file_content writing a .php file). It surfaces as a transport-level error, NOT an {ok:false} payload. Plain text and PHP files using the short tag "<?" / "<?=" pass through the WAF and execute normally on JetHost shared hosting, since short_open_tag is on across the fleet. To deploy PHP files reliably prefer deploy_private_repo (git + .cpanel.yml), which clones over SSH and bypasses this path. NOTE — Fileman has no delete/copy/move/mkdir function; save_file_content cannot create parent directories.

Invoked over the MCP transport with a tools/call request naming this tool.