How to Connect Claude Code to cPanel With MCP

01

Overview

cPanel Meridian can connect an MCP-capable AI client to a hosting account through the WebPros MCP server. cPanel's official documentation uses Claude Code as the concrete setup example, making this one of the clearest new workflows in cPanel AI.

02

Before you startnnYou need access to the Meridian interface with MCP enabled by your hosting provider, a WebPros account, and a compatible MCP client. cPanel notes that AI feature availability varies by hosting provider, enabled features and release tier.

If the MCP Connection section is absent, do not assume your local client is broken; first confirm that your provider/account has the feature.

03

Step 2: Get the MCP configurationnnAfter linking, cPanel lets you download an `mcp.json` file or copy the connection configuration. Treat this as connection configuration rather than content to publish publicly.

For Claude Code, cPanel documents two locations: ~/.claude.json for single-user access or .mcp.json in a repository root for a configuration shared with that project's users. Choose the scope deliberately.

04

Step 3: Add the WebPros MCP server to Claude CodennAdd the supplied server configuration to the appropriate `mcpServers` section. Use the configuration cPanel generated rather than inventing a server endpoint or credentials from examples.

Restart Claude Code after changing the configuration so the client loads the server.

05

Step 4: AuthenticatennRun Claude Code's `/mcp` command, select the WebPros/cPanel connection and choose authentication. cPanel says a browser window opens to complete authorization.

Authentication is a meaningful permission boundary. Review which account you are authorizing instead of treating the browser step as a routine confirmation.

06

Step 5: Test discovery before deploymentnnStart with a low-risk request that confirms the connector is available and that the agent is addressing the intended cPanel account. Avoid making production changes as your first connectivity test.

Once the connection is confirmed, move to a narrowly scoped task such as inspecting the deployment prerequisites for a project.

07

Step 6: Deploy only after reviewing the targetnncPanel's Node.js documentation supports a WebPros MCP deployment flow where an agent can deploy the current project and return a live HTTPS URL. Before issuing that request, verify the target account, domain/subdomain, environment variables and project source.

The fact that an agent can deploy does not remove the need to review application security, secrets, dependencies and production configuration.

08

Disconnecting MCPnncPanel documents an Unlink WebPros Account control in the MCP Connection section. Disconnecting means you will need to sign in again before using the WebPros MCP connection with that cPanel account.

Know the revocation path before giving an agent recurring operational work.

09

FAQ

Does cPanel officially support Claude Code with MCP?

Yes. cPanel's current Connect to MCP documentation explicitly walks through Claude Code.

Do I need SSH or a manually created API token?ncPanel positions WebPros MCP as a way for supported AI clients to automate deployment without requiring the user to manually manage API tokens or use SSH for that workflow.

Can I share the MCP configuration with a project?

The official docs describe .mcp.json in a repository root for shared project access, while ~/.claude.json is the single-user path. Consider the security implications before sharing configuration.

How do I remove access?

Use Unlink WebPros Account in Meridian's MCP Connection section, according to cPanel's documentation.