
Whmcs Mcp Server
io.github.not-sure-wPublished by GitHub account not-sure-wv1.2.0Updated Oct 25, 2026
MCP server for WHMCS — 73 tools, 10 resources, 8 prompts, simulate mode, rate limiting.
Overview
A local MCP server that connects an assistant to a WHMCS installation, exposing 73 tools, 10 resources and 8 prompts for billing and client management.
- What you can do
- Work with WHMCS data through 73 tools covering clients, orders, invoices, products and support areas, plus 10 resources and 8 prompts for guided workflows. Includes a simulate mode and built-in rate limiting. The manifest does not list individual tools, so exact capabilities should be checked in the package before relying on them.
- When to use it
- Useful when an assistant needs to look up or act on WHMCS billing, client, order or support data for a hosting or service business, and you want that access from a local desktop client.
- Requirements
- Runs locally over stdio, installed from the npm package whmcs-mcp-server (Node.js). Needs an HTTPS WHMCS installation URL in WHMCS_BASE_URL, plus the WHMCS API identifier and secret in WHMCS_IDENTIFIER and WHMCS_SECRET. Desktop only; not web executable.
Installation
In SourceWeft
- Open Whmcs Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.2.0LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.