cPanel

The Cpanel MCP Server provides a bridge between AI assistants and cPanel hosting accounts, enabling natural language driven management of hosting tasks. It connects to the cPanel API to perform common actions such as file operations, disk usage checks, database and user management, email setup, subdomain and FTP management, backups, and SSL installation. Once configured, you can issue conversational commands to create or edit files, manage databases and users, create email accounts, spin up subdomains, manage FTP accounts, initiate backups, and install SSL certificates. The server is designed to run as a standard MCP server process and is invoked via Node.js, using a built/index.js build artifact as the entry point.

To use it, ensure your MCP settings point to the built index.js and provide the necessary CPANEL credentials as environment variables. With these in place, your AI assistant can translate user intents into cPanel API calls through the MCP layer, enabling tasks like updating website files, preparing backups, or configuring email accounts without leaving the chat interface.

Prerequisites:

• Node.js and npm installed on your system
• Access to a cPanel hosting account with API access enabled
• A working MCP environment and editor integration that supports MCP servers

Installation steps:

1. Install dependencies and build the server

   • npm install
   • npm run build

2. Configure MCP settings

   • Open your MCP settings file (e.g., cline_mcp_settings.json) and add the cpanel server block:

   { "mcpServers": { "cpanel": { "command": "node", "args": ["/path/to/Cpanel-MCP-Server/build/index.js"], "env": { "CPANEL_USERNAME": "your_cpanel_username", "CPANEL_API_TOKEN": "your_cpanel_api_token", "CPANEL_SERVER_URL": "https://your_cpanel_domain.com:2083" }, "disabled": false, "autoApprove": [] } } }

   Replace the placeholders with your actual cPanel credentials and the absolute path to the built index.js file on your system.

3. Run the server

   • Execute the Node.js entry point via your MCP runner configuration; the server will start listening for MCP requests and proxy them to the cPanel API.

Security: Your cPanel credentials are never stored in the repository. They are loaded at runtime from your local MCP settings file as environment variables. Ensure the settings file is kept secure and not committed to version control. If you update the cPanel API token or domain, regenerate the environment variables accordingly. Common issues may include incorrect API permissions, invalid server URL, or mismatched paths to the built index.js. Verify the CPANEL_SERVER_URL uses the correct protocol and port (typically https on port 2083).