deploy_private_repo

Deploy a private SSH Git repository to one domain on one of the caller's hosting services using a pre-installed per-repo deploy key (generated via generate_deploy_key). The repository MUST contain a .cpanel.yml file at its root — the deployment is driven by it (it defines where files land); a repository without one returns no_cpanel_yml. The repository is cloned over SSH and deployed following .cpanel.yml to the target domain. Call generate_deploy_key first (which needs the cpanel:uapi scope) to provision the SSH key for this (service_id, repo_ssh_url) pair, then add the returned public key to the repository's deploy keys on GitHub/GitLab/Bitbucket before calling this tool. An omitted branch deploys the repository default branch (HEAD). This is a state-changing, destructive, non-idempotent write — it requires the write:deploy scope. Step-up auth enforcement is deferred to the Phase-2 step-up mechanism. TIP — verifying success: a subsequent "Repository not found" from get_private_repo_deploy_status can be a red herring — the status command re-contacts the remote, but the clone + .cpanel.yml deploy may have already landed; confirm by listing the docroot (list_website_domains gives its path) rather than trusting that error. TIP — a FAILED clone leaves a hidden .git under /home/<user>/repositories/<domain>/, and a later retry then fails with "directory already contains files"; cPanel VersionControl delete does NOT remove these files and Fileman cannot delete — the user must clear that directory in cPanel File Manager (enable Show Hidden Files) before retrying.

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