Developer · Local MCP server
Whmcs MCP Server
MCP server for WHMCS - 73 tools, 10 resources, 8 prompts, simulate mode, rate limiting.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.not-sure-w/whmcs-mcp-server- Version
- 1.2.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-04-05
- Updated
- 2026-04-05
- Publisher
- not-sure-w (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/not-sure-w) · how
- Repository
- github.com/not-sure-w/whmcs-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | whmcs-mcp-server | 1.2.0 | stdio |
How to connect Whmcs MCP Server
Whmcs MCP Server runs locally from a Node.js package published to the npm registry: whmcs-mcp-server version 1.2.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y whmcs-mcp-server@1.2.0. It reads these environment variables: WHMCS_BASE_URL (required), WHMCS_IDENTIFIER (required, secret) and WHMCS_SECRET (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"whmcs-mcp-server": {
"command": "npx",
"args": [
"-y",
"whmcs-mcp-server@1.2.0"
],
"env": {
"WHMCS_BASE_URL": "<value>",
"WHMCS_IDENTIFIER": "<secret>",
"WHMCS_SECRET": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| WhichModelCost-optimized LLM model routing recommendations for autonomous AI agents. | Remote · HTTPLive check: ✗ no handshake |
| WhisperOne routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| WhisperGraphThe internet's infrastructure graph for AI agents - 46B nodes and edges, free trial via 2 HTTP calls. | Remote & Local · HTTP, stdioLive check: sign-in required |
| WhiteCapData DevOperate a k3s / Kubernetes cluster from your AI agent - safe-by-default MCP server. | Local · stdio |
| Whois MCP ServerDomain registration, availability, DNS records, and IP/ASN resolution via RDAP and DNS-over-HTTPS. | Local · stdio, HTTP |
| WhoisJSONWHOIS, DNS, SSL, and domain availability lookups for AI assistants. | Local · stdio |
| Whoop MCPRead-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports. | Local · stdio |
| WHOOP MCPSync WHOOP recovery, sleep, strain, and workouts into Postgres and query them from any MCP client. | Local · stdio |