Cursor + WHMCS MCP Server
Cursor and VS Code both support MCP natively. Add your WHMCS MCP Server to the editor config, and query client data, invoices, and tickets from the AI sidebar while you code. Look up live data to test hooks, debug API integrations, or check service states without leaving your IDE.
Supported Code Editors
| Editor | Config File | Transport | Notes |
|---|---|---|---|
| Cursor | .cursor/mcp.json | STDIO + SSE | Native MCP. Project or global config. |
| VS Code (Copilot) | .vscode/mcp.json | STDIO + SSE | Enable via "chat.mcp.enabled": true |
| Windsurf | .windsurf/mcp.json | STDIO + SSE | MCP discovery and AI Flow. |
| Zed | settings.json | STDIO | MCP prompts and tools. |
What You Can Do
Access WHMCS data while writing code. No context switching.
Debug with Live Data
While building a WHMCS hook, ask the AI sidebar for a real client record to see the exact data structure. No more guessing field names or checking documentation. Query live WHMCS data to reproduce bugs against real scenarios.
Example prompt:
“Get the order history for client #2045. Show me the last 5 orders with product details.”
Returns real order data from your WHMCS. You see exact field names, data types, and relationships.
Generate Code from Real Data
Query WHMCS for product structures, then ask the AI to generate a PHP hook based on actual data models. The AI sees real field names and relationships instead of working from outdated documentation.
Example prompt:
“Show me all product groups and their products. Generate a PHP hook that runs when a new order is placed.”
The generated code uses correct field names and table relationships because the AI queried your actual WHMCS.
Quick Admin Tasks During Dev
Create test tickets, look up invoices, or check server status without switching to the WHMCS admin panel. Saves context switches during long development sessions.
Example prompt:
“Create a test ticket for client #1001 with subject "Testing webhook integration".”
Ticket created directly from the IDE. You stay in your coding flow.
Schema Discovery
Ask the AI what fields are available on a client record, invoice, or ticket. Useful when writing custom modules or API integrations and you need to know the exact data shapes.
Example prompt:
“What fields are available on a WHMCS client record? Show me an example response.”
Returns the full field list from a real MCP tool response. More accurate than documentation because it is live data.
How to Connect
Add WHMCS to your editor in 3 steps.
Install MCP Server on your WHMCS
Upload the addon, activate it, and generate a Bearer token. Full installation guide
Add MCP config to your editor
Create the MCP config file in your project or global settings:
// Cursor: .cursor/mcp.json
{
"mcpServers": {
"whmcs": {
"type": "streamable-http",
"url": "https://your-whmcs.com/modules/addons/mx_mcp/mcp.php",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
// VS Code: .vscode/mcp.json
{
"servers": {
"whmcs": {
"type": "streamable-http",
"url": "https://your-whmcs.com/modules/addons/mx_mcp/mcp.php",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
// Enable via: Settings > "chat.mcp.enabled": trueUse the AI chat to query WHMCS
Open the AI sidebar in your editor and ask questions about your WHMCS data. The MCP tools will appear automatically.
Data Flow
How Cursor Connects to WHMCS
Cursor reads your WHMCS data through MCP Server while you code. Debug client issues, query billing data, and build modules faster.
MCP Server
AI Integration Hub
Better Together
Access the full MX ecosystem from your code editor.
Query MX Metrics analytics data while developing. Check how your code changes affect revenue metrics. Pull live MRR, churn, or LTV data into your development context.
Learn about MX Metrics →Debug MX Proposals integration with real proposal data. Query proposal status, client history, and acceptance rates during development without leaving your editor.
Learn about MX Proposals →How your data flows
WHMCS queries go through MCP to your server. AI processing depends on your editor: Cursor uses their cloud (Anthropic or OpenAI models), VS Code Copilot uses Microsoft/OpenAI. For fully private dev environments, combine with local AI models via Ollama or LM Studio.
For fully private AI operations, consider local AI models that run entirely on your hardware.
Frequently Asked Questions
- Does Cursor support MCP natively?
- Yes. Cursor has native MCP support via .cursor/mcp.json (per-project) or ~/.cursor/mcp.json (global). It supports STDIO, SSE, and HTTP transports. MCP tools appear automatically in the AI sidebar when you open a project with an MCP config.
- Does VS Code support MCP?
- Yes. VS Code supports MCP through GitHub Copilot Chat. Enable it in Settings with "chat.mcp.enabled": true, then add your MCP servers to .vscode/mcp.json. Works with Copilot Chat in the sidebar. Requires VS Code 1.99 or later and an active Copilot subscription.
- Can I use Windsurf or Zed too?
- Yes. Windsurf (by Codeium) supports MCP with a similar JSON config. Zed supports MCP via its settings.json. JetBrains IDEs (IntelliJ, WebStorm, PHPStorm) support MCP through the JetBrains AI Assistant plugin. See our compatible tools page for the full list.
- Who is this integration for?
- WHMCS module developers, hosting company DevOps teams, freelancers building custom WHMCS solutions, and anyone who writes code that interacts with WHMCS. If you develop in PHP for WHMCS, being able to query live client data from your editor without switching to the admin panel saves significant time.
- Can I share the MCP config with my team?
- Yes. Use the project-level config (.cursor/mcp.json or .vscode/mcp.json) and commit it to your repo. Each developer uses their own API key (set via environment variable). The config file references the env var, not the key itself. This way the setup is shared but credentials stay per-developer.
Query WHMCS from your code editor
Install MCP Server, add the config to your editor, and access client data, invoices, and tickets without leaving your IDE.