Seven plugins, one consistent system. Setup, authentication and configuration are consistent across the InsationAI suite — then each plugin adds its own MCP tools. Start here.
Install any InsationAI plugin, activate your license, and connect your first MCP client in minutes.
OAuth 2.1 with dynamic client registration — connect Claude, Cursor and other MCP clients.
Per-plugin settings: enable/disable individual tools, restrict roles, review the audit log.
Every plugin's full tool list, grouped by capability area — see the breakdown below.
Lifetime updates and a strict per-site license, delivered straight to a licensed install.
Connection, licensing and endpoint issues — and how to resolve them.
Every InsationAI plugin installs and licenses the same way:
The six WordPress plugins use OAuth 2.1 with dynamic client registration. Your AI client (Claude Desktop/API, Cursor, etc.) registers itself on first connect and obtains an access token — no manual key exchange. Every tool call is then enforced against WordPress user capabilities, so an AI can only do what the authenticated user is permitted to do. Connect a client via Settings → Connectors → Add custom connector using the plugin’s endpoint URL, then approve the OAuth handshake.
WHMCSMCP instead uses a bearer token you generate in its admin (Addons → MCP Server → API Keys); every call runs as a WHMCS admin user you choose. Connect it with the Authorization: Bearer <token> header (or the bundled mcp-remote bridge for Claude Desktop).
Each plugin’s admin tab under InsationAI Tools lets you enable/disable individual tools, manage API tokens, activate or re-check the per-site license, review the audit log of AI tool calls, and receive lifetime updates. The six WordPress plugins require WordPress 6.0+ and PHP 8.2+; WHMCSMCP runs on WHMCS 8.x with PHP 7.4+.
Turns core WordPress into a secure MCP server — no extra platform dependency. ~90 tools across 21 capability areas:
Requires WordPress 6.0+ and PHP 8.2+.
Structured, safe AI access to everything Elementor builds. Requires the free Elementor plugin. ~96 tools across 17 capability areas:
Requires WordPress 6.0+, PHP 8.2+, and Elementor (free) active. Also dual-registers tools on the WordPress Abilities API (WP 6.9+).
The Elementor Pro–only feature surface. Runs alongside ElementorMCP; requires Elementor Pro. ~46 tools across 12 capability areas:
Requires WordPress 6.0+, PHP 8.2+, and both Elementor and Elementor Pro active.
AI control of the Avada theme configuration surface. Pair with FusionBuilderMCP for the page-builder surface. 33 tools across 8 capability areas:
Requires WordPress 6.0+, PHP 8.2+, and the Avada theme active.
AI control of Fusion Builder — the page builder bundled with the Avada theme. Pair with AvadaMCP for the theme surface. 11 tools:
Requires WordPress 6.0+, PHP 8.2+, and Fusion Builder (bundled with Avada) active.
Automated GitHub releases for your plugins, driven from inside WordPress. Store a fine-grained GitHub token once in the plugin’s GitHub tab; releases are published server-side — the token never reaches the AI client. 6 tools:
Requires WordPress 6.0+ and PHP 8.2+. Set a repo-scoped GitHub token in the plugin’s GitHub tab.
Turns your WHMCS billing system into a secure MCP server — the only InsationAI plugin that runs on WHMCS rather than WordPress. Authenticate with a bearer token, scope every call to a WHMCS admin user you choose, and enable or disable individual tools. 68 tools across 10 capability areas:
Requires WHMCS 8.x and PHP 7.4+ (PHP 8.x recommended). Authentication is bearer-token based; the MCP endpoint only serves on a licensed, activated install.
If your AI client can’t connect:
Still stuck? Email support@insation.ai and include the diagnostic summary from the plugin’s Support tab.