pnlcs-mcp
Related Servers
Alternatives to pnlcs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and manage a web hosting billing platform through its External API — clients, tickets, invoices, domains, orders, products, and system data. It defaults to read-only with per-domain opt-in for writes, two-step confirmation for billing and destructive actions, and automatic redaction of secrets, card data, and PII.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to autonomously govern cloud hosting infrastructure and billing workflows, including provisioning, invoices, wallet credits, support tickets, and catalog management through 35 tools with JSON:API response hydration.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage cPanel hosting accounts including DNS, email, databases, SSL, files, security, and more through natural language using cPanel's UAPI and API2.-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage WHM hosting accounts and server administration tasks including account management, server stats, updates, SSL, backups, and email through a secure API.11-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to administrate WHMCS installations through the External API, providing ~50 tools for clients, billing, orders, services, domains, support, and aggregators with safety features and governance.45 npm3ISC
- AlicenseNot gradedqualityBmaintenanceConnect Claude, ChatGPT, and Cursor to your live WHMCS. 96 tools, 18 workflow prompts, 24 resources. Runs as a Docker container (or Linux binary) that talks to the WHMCS API from outside — nothing installed inside WHMCS. OAuth 2.0 for Claude.ai and ChatGPT web, bearer tokens for Cursor. dryRun on every write. 14-day trial, no card.13 npm2MIT
TDQS
Scored across 15 tools
Each tool targets a distinct resource or summary view: health/stats/activity are clearly separate from client, invoice, order, ticket, transaction, and product listings. There is little overlap, and the get_/list_ split makes singular detail vs collection retrieval obvious.
Tool names consistently use lowercase snake_case with get_ for single items/details and list_ for collections. The compound list_client_services and list_client_domains still follow the same predictable verb_noun pattern as the rest of the set.
Fifteen tools is at the upper end of the ideal range but every one maps to a distinct and useful view of the PNLCS domain, from clients and invoices to tickets and activity. There is no obvious redundancy or filler.
As a read-only business overview server, the surface is broad and coherent: clients, services, domains, invoices, orders, tickets, transactions, products, stats, health, and activity are all exposed. Minor gaps such as no get_order, get_product, or get_transaction detail views, and no mutation endpoints, keep it from being fully complete.