Obambu cPanel MCP

obambu-cpanel-mcp

A Model Context Protocol (MCP) server that lets an AI assistant (Claude, etc.) manage a cPanel hosting account through the cPanel UAPI.

It exposes tools for domains, DNS zones, email accounts, MySQL databases, and file listing, plus a generic escape hatch to call any other UAPI module/function.

Requirements

• Node.js 18+
• A cPanel account with API token access (Security → Manage API Tokens in cPanel)

Getting your cPanel credentials (Obambu example)

The four env vars below can come from any cPanel host, but here's how to find them on Obambu:

• CPANEL_HOST — your server hostname, e.g. cp4.obambu.com (or your own domain if cPanel is reachable at https://yourdomain.com:2083). Find it in your Obambu welcome email, or in your domain's DNS zone: look for an A record named cpanel (e.g. cpanel.yourdomain.com) — that same server also answers at its cpX.obambu.com hostname.
• CPANEL_PORT — 00000 (cPanel's default HTTPS port). Leave it unless your host says otherwise.
• CPANEL_USERNAME — your cPanel account username, shown top-right when logged into cPanel, or in the welcome email Obambu sent when the hosting account was created.
• CPANEL_API_TOKEN — generate one yourself, it is not your cPanel password:
  1. Log into cPanel at https://<CPANEL_HOST>:00000
  2. Go to Security → Manage API Tokens
  3. Click Create, give it a name (e.g. mcp-server), optionally restrict it to specific ACLs, then Create
  4. Copy the token immediately — cPanel only shows it once

Using it with an MCP client (npx, recommended)

Published on npm as obambu-cpanel-mcp — no clone or build needed. Add it to your MCP client config (e.g. Claude Desktop / Claude Code):

{  "mcpServers": {    "obambu-cpanel": {      "command": "npx",      "args": ["-y", "obambu-cpanel-mcp"],      "env": {        "CPANEL_HOST": "your-server-hostname-or-ip",        "CPANEL_PORT": "00000",        "CPANEL_USERNAME": "your-cpanel-username",        "CPANEL_API_TOKEN": "your-api-token"      }    }  }}

Running from source

git clone https://github.com/RodrigueDev13/obambu-cpanel-mcp.gitcd obambu-cpanel-mcpnpm installcp .env.example .env

Edit .env with your cPanel details, then:

npm run buildnpm start

For local development without building first:

npm run dev

When running from source, point your MCP client at the built entrypoint instead of npx:

{  "mcpServers": {    "obambu-cpanel": {      "command": "node",      "args": ["/absolute/path/to/obambu-cpanel-mcp/dist/index.js"],      "env": {        "CPANEL_HOST": "your-server-hostname-or-ip",        "CPANEL_PORT": "00000",        "CPANEL_USERNAME": "your-cpanel-username",        "CPANEL_API_TOKEN": "your-api-token"      }    }  }}

Available tools

Usage examples

Once connected, just talk to your assistant in plain language — it picks the right tool:

• "Test the connection to my cPanel account" → get_account_summary
• "What domains and subdomains are on this hosting account?" → list_domains
• "Show me the DNS records for example.com" → list_dns_records
• "Add an A record for shop.example.com pointing to 1.2.3.4" → add_dns_record
• "Create a mailbox [email protected]" → create_email
• "Create a MySQL database and user for my new app, then grant privileges" → create_database + create_database_user + grant_database_privileges
• "List the files in public_html" → list_files
• "Read config/filesystems.php and fix this path" → cpanel_uapi_call with module: "Fileman", function: "get_file_content" / save_file_content

Because tool calls map directly to UAPI modules, this is also useful for real migration/deployment workflows — e.g. moving a site to a new cPanel account, provisioning a database for a fresh app, or auditing DNS before a domain cutover.

Notes on Fileman

Only list_files (backed by Fileman::list_files) and, through the cpanel_uapi_call escape hatch, get_file_content / save_file_content are known to work reliably for reading and writing individual files. Bulk filesystem operations (extract_files, rename, mkdir, fileop, delete_files, ...) are not guaranteed to be available depending on your cPanel version/provider — test before relying on them, and prefer cPanel's File Manager UI for bulk moves, extraction, and deletion.

Security

• Never commit your .env file (it's git-ignored by default).
• Scope your cPanel API token as narrowly as your provider allows.
• The cpanel_uapi_call tool can call any UAPI function available to your account — treat it with the same care as direct API/token access.

License

MIT