Connect a module
WHMCS
ShopMCP connects WHMCS clients, invoices, services, domains, support tickets, orders, quotes, and hosting module actions to Claude, ChatGPT, Cursor, and other MCP clients.
Selected workspace rollout
1. Create WHMCS API credentials
In WHMCS Admin, create API authentication credentials for an admin user whose role includes API Access. ShopMCP uses the official WHMCS External API fields identifier, secret, action, and responsetype=json.
Use a dedicated admin user or role group for ShopMCP where possible. Grant the WHMCS permissions that match the work you want the agent to do, then widen access only when a workflow needs it.
2. Decide how WHMCS will allow API traffic
WHMCS restricts API access by IP unless you configure an API access key in configuration.php. If your WHMCS host cannot safely allow the ShopMCP outbound IP path, create the access key and paste it into ShopMCP as the optional access key.
php$api_access_key = 'your-secret-api-access-key';
Keep the access key private
3. Connect WHMCS in ShopMCP
Open Settings - Integrations, choose WHMCS, then enter:
- Your WHMCS base URL, for example
https://billing.example.com. - The API identifier.
- The API secret.
- The optional API access key, if your WHMCS install uses one.
- A label, useful when an agency manages more than one WHMCS install.
ShopMCP verifies the connection with WHMCS details or system stats, then stores the credentials encrypted at rest.
4. What you can ask
| Goal | Example prompt | What ShopMCP reads |
|---|---|---|
| Rank client revenue | Show my highest lifetime WHMCS revenue clients, ignoring tiny recurring-only accounts. | Clients, paid invoices, services, domains. |
| Find outreach opportunities | Which older WHMCS clients have large past invoices but no recent project work? | Invoice totals, largest invoice, last paid invoice date, active services. |
| Support context | Pull the recent ticket history for this client before I email them. | Tickets, ticket replies, departments, statuses. |
| Hosting service checks | List active services for this client and flag anything due for renewal. | Client products, domains, orders, module state. |
| Billing cleanup | Show overdue invoices and clients with repeated late payment patterns. | Invoices, transactions, credits, client details. |
5. Large WHMCS reports
WHMCS accounts can have a small client list but thousands of historical invoices. For revenue ranking, use the WHMCS client revenue summary tool instead of asking the AI client to inspect each client one by one. ShopMCP pages the WHMCS data server-side, stores the large result as a temporary resource, and returns a compact ranked table to the AI client.
- Lifetime revenue is calculated from WHMCS invoice totals, not invoices billed outside WHMCS.
- Large results use temporary ShopMCP resources so raw invoice data does not flood the chat window.
- The AI client can filter, aggregate, or export the stored resource without fetching the full payload into conversation context.
6. Writes and safety
WHMCS write tools stay hidden until writes are enabled for the workspace. When enabled, the agent can create or update clients, invoices, payments, credits, tickets, domains, orders, service modules, activity log entries, emails, affiliates, and quotes.
Review billing and module actions