Architecture
One bridge. Every agent, every tool.
AI assistants connect through the Relyagent MCP gateway — OAuth-secured, scope-gated, rate-limited and fully audited — to reach your WHMCS clients, tickets, invoices, services and domains.
Relyagent turns your WHMCS install into a self-hosted MCP server. Claude Desktop, Cursor, your custom bot — they speak Model Context Protocol; now WHMCS does too. OAuth-gated, scope-controlled, audit-logged.
AI assistants connect through the Relyagent MCP gateway — OAuth-secured, scope-gated, rate-limited and fully audited — to reach your WHMCS clients, tickets, invoices, services and domains.
One license per WHMCS installation. Includes updates, support, and unlimited MCP clients & tool calls.
Yearly plan with continuous updates
Pay once, own it forever
A complete MCP server built into your WHMCS — with the guardrails your business actually needs in production.
Clients, tickets, invoices, services, domains, admin. Read or write, all scope-gated. Toggle entire groups on or off from the admin panel.
Full OAuth authorization-code server built in. Register clients from the admin UI, consent-screen flow, RSA-signed JWTs. No third-party auth service needed.
Both MCP transports out of the box. Auto-negotiated per request via the Accept header. Works with every spec-compliant client.
Ten known jailbreak patterns scrubbed from ticket bodies, client notes, and invoice descriptions before they reach the model. Detected hits flagged in the audit log.
Fixed-window minute + day counters per access token. Defaults 60/min and 5,000/day, tunable per install. Returns HTTP 429 + Retry-After on overflow.
One row per tool call — success, sanitized, forbidden, rate-limited, error. Sensitive params redacted. Write tools refuse to fire until you flip the admin toggle.
Every MCP client is registered explicitly. Every connection goes through an admin consent screen with the exact scopes laid out. PKCE-protected, one-time auth codes, refresh tokens with rotation tracking.
clients:read, tickets:write, admin:read, etc.
clients:readView client profilestickets:readView support ticketstickets:writeReply, change statusadmin:readStats & activity logThe Relyagent admin panel gives you a live view of every registered client, every active token, and every tool call. Three KPIs at a glance, a click-to-revoke table, and a one-button panic switch when something feels off.
Relyagent writes one audit row per tool call — regardless of outcome. Success, sanitised, forbidden, rate-limited, or error. Sensitive parameters (passwords, card numbers, OAuth secrets) are redacted before insert. Queryable from the admin panel, exportable as CSV.
AI agents make mistakes. Sometimes they get prompt-injected. Sometimes they hallucinate a destructive action. Relyagent assumes the worst — and contains it at four layers.
Bearer-token auth via league/oauth2-server. RSA-signed JWTs. Per-install keypair, rotatable on demand. Every call validated through a real resource server.
One audit row per tool call. Success, sanitised, forbidden, rate-limited, or error — all captured. Sensitive parameters redacted before insert. CSV export, no leaks.
Minute and day windows per access token. Defaults 60/min and 5,000/day. Tunable up to 10,000/min, 1M/day. HTTP 429 + Retry-After on overflow.
Ten known jailbreak patterns scrubbed from every value flowing back to the LLM. Hits flagged in the audit log as status=sanitized for forensic review.
Relyagent runs on standard WHMCS environments. No exotic dependencies, no extra services to manage, no third-party auth provider.
A WHMCS addon that exposes your WHMCS install as a self-hosted MCP (Model Context Protocol) server — so any LLM client that speaks MCP (Claude Desktop, Cursor, your custom agent) can call WHMCS tools through OAuth 2.0 + PKCE.
Roughly 25 scope-gated tools across six groups: clients, tickets, invoices, services, domains, and admin.
You register the client from Addons → Relyagent → MCP Clients, picking which OAuth scopes it can request. The client then uses the standard OAuth 2.0 authorization-code flow with PKCE — you approve the request on a consent screen with the exact scopes spelled out, and the client receives a bearer access token and refresh token.
Every subsequent JSON-RPC call carries that bearer. Refresh tokens rotate on use.
Yes — Relyagent ships both MCP transports: Streamable HTTP (default) and Server-Sent Events (when the client sends Accept: text/event-stream). Anything that implements the MCP 2025-03-26 spec works out of the box.
That's the entire design centre. Every tool requires a specific OAuth scope. Write operations require an additional "Dangerous Operations" admin toggle, which starts off. Every parameter and result flows through a prompt-injection sanitiser. Every call is rate-limited per token. Every call is audit-logged with sensitive parameters redacted.
The agent can only do what you explicitly granted — and you can see exactly what it did.
Yes — and that's the default. The Dangerous Operations toggle in MCP Settings starts off. Until you flip it on, write tools (suspend_service, create_invoice, update_client, add_credit, etc.) reject every call with MCP error -32004.
You can also disable entire tool groups (clients, tickets, invoices, services, domains, admin) independently — useful for staging environments or restricted-purpose agents.
Each access token has its own minute + day counters. Defaults are 60/min and 5,000/day, tunable in MCP Settings (hard ceilings: 10,000/min and 1,000,000/day). On overflow the request returns HTTP 429 with a Retry-After header and MCP error -32029.
There's also a one-click "Revoke All Tokens" panic switch in the admin panel for when something's clearly wrong.
A library of ten known jailbreak patterns — ignore previous instructions, you are now a/an, act as, [INST], <|im_start|>, DAN mode, jailbreak, and several others — is matched against every string in every tool response. Anywhere user-generated text lives: ticket bodies, client notes, invoice descriptions, etc.
Matches are replaced with [sanitized]. The audit row gets tagged status=sanitized so you can spot which calls hit a pattern.
Relyagent v1.0.x is built and tested for WHMCS 8.x with PHP 7.4 or higher. ionCube Loader is required (it's pre-installed on virtually all WHMCS-ready hosting environments, including all Relyweb hosting plans).
One license per WHMCS installation, matched by domain and directory. The plugin checks your license periodically and caches the result locally. Updates are checked daily — when one's available, click "Update Now" from the admin panel; the plugin backs up the current installation before applying the update and auto-restores if anything fails.
Annual licenses continue to work after expiry, but stop receiving updates and support. Lifetime licenses never expire.
Yes — we offer a 14-day money-back guarantee. If Relyagent doesn't fit your setup or doesn't meet your needs, just contact support within 14 days of purchase for a full refund.
OAuth-protected. Audit-logged. Scope-controlled. 14-day money-back guarantee, no risk.