01
Overview
cPanel Meridian can deploy Node.js applications from Git, a ZIP archive or an authenticated WebPros MCP connection. The MCP path is especially relevant to AI-built applications because a coding agent can move from working on the repository to initiating the hosting deployment without a separate SSH workflow.
02
Step 1: Choose the website/subdomainnnIn Meridian's Websites hub, add a website and create the subdomain the application will use. cPanel warns that after deployment the app's subdomain cannot be renamed, so choose the production target deliberately.
The initial v138 Node.js deployment workflow is subdomain-oriented. Do not promise arbitrary apex-domain behavior without checking the current release.
03
Step 2: Choose Node.jsnnSelect Node.js as the website type. Meridian then lets you choose the source: a Git repository, ZIP upload or WebPros MCP.
Git is useful when you want normal redeploy/rollback behavior; ZIP fits a relatively static package; MCP fits an agent-driven workflow.
04
Step 3: Connect WebPros MCPnnChoose the MCP deployment option. If the WebPros account is not already linked, complete that connection first. Download the generated `mcp.json`, add it to your AI client and authenticate.
Use cPanel's generated configuration rather than copying endpoints or credentials from third-party tutorials.
05
Step 4: Ask the agent to deploy the projectnncPanel's official documentation gives a prompt pattern that asks the agent to use the `webpros-mcp` connector, deploy the Node.js app in the current project and return the live HTTPS URL when reachable.
Before running a production deployment, review the repository, build scripts, package manager and any secret requirements. An agent executing the deployment does not validate the business logic or security of the application for you.
06
Step 5: Review runtime settingsnnMeridian can detect the package manager and lets you choose a Node.js version and configure environment variables. Store secrets as environment variables rather than hard-coding them into the repository or prompt.
Changing runtime versions can affect dependency compatibility, so use the version the application actually supports.
07
Step 6: Deploy and verify HTTPSnnMeridian installs dependencies, deploys the application and starts its process. Verify the returned URL yourself: check that HTTPS loads, the expected application is running and critical routes work.
Do not equate a successful deployment command with a successful production application.
08
Managing the app after deploymentnnThe Websites hub exposes Start, Stop, Restart and Redeploy controls for apps that run a server process. It also exposes recent app logs and environment-variable management.
For Git-backed apps, Redeploy rebuilds and restarts after code changes. If a deployment fails, inspect the app logs before repeatedly asking an agent to retry.
09
FAQ
Can Claude Code deploy directly to cPanel?
With Meridian and WebPros MCP enabled, cPanel documents an agent-driven deployment workflow and uses Claude Code in its MCP setup documentation.
Can I deploy from Git instead of MCP?
Yes. Meridian also supports public/private Git repositories and ZIP uploads.
Does cPanel manage the Node.js process?
Yes. The current docs say Meridian installs dependencies, starts the app and provides process controls, logs and environment-variable management.
Is every cPanel account eligible?
No universal availability should be assumed. Node.js and AI/MCP capabilities depend on hosting-provider configuration and feature enablement.
Sources
Primary and supporting sources
Use the linked documentation to check current pricing, access and product behaviour. The dates above describe this article; they do not guarantee that every vendor claim remains current.