If a question is not covered here, the project documentation in the downloads goes deeper — including the list of things that are not yet verified.
Nothing. The core plugin is free — GPL-2.0-or-later, with all 61 tools, OAuth 2.1, build sessions, safety features and integrations included. Commercial offerings (separate add-ons, priority support, managed setup) are planned for the future and will be announced with their details when ready; they will never unlock or meter the core. See the Pricing page.
No. There is no metering in the core: no usage quotas, no action counters for billing, no licence checks, no activation. You can run it on as many of your sites, with as many calls, as you like. One distinction, stated plainly: since 1.4.0 the MCP and token endpoints carry configurable abuse-protection rate limits (defaults: 600 MCP requests per minute per credential; 60 token requests per minute per client and IP) that exist only to stop request floods no interactive client produces. They are not a quota, they never meter or bill your usage, and you can retune or switch them off entirely in Settings → Security.
No. It sends no telemetry and contacts no third-party service. The only outbound requests it makes are ones your own work requires: fetching your own site’s published pages during a render check, and downloading an image when you explicitly call the import tool with a URL.
Any MCP client that can reach a remote MCP endpoint over HTTP with a bearer header or OAuth 2.1 — that includes Claude and ChatGPT class clients and local agent tooling. The server negotiates the legacy MCP revisions 2025-11-25, 2025-06-18 and 2024-11-05, and since 1.4.0 also serves the 2026-07-28 protocol profile on the same endpoint. The AI Clients screen in wp-admin lists the known clients with a setup guide and copy-ready configuration for each.
Not by default. Writes are draft-first: pages and products are created as drafts, and a status value smuggled into arguments is stripped. Publishing exists only on explicit, scope-gated paths (publish scope plus the matching WordPress capability). Most owners review drafts in wp-admin and publish them personally.
Its page-removal tool moves content to the WordPress Trash — recoverable, like deleting by hand. The plugin has no permanent-delete path for content, and its uninstaller removes only the plugin’s own options and tables, never posts, pages, media or products.
The dependent tools stay visible but answer dependency_missing when called — a clear refusal rather than a fabricated result. The Diagnostics screen shows which integrations are detected and which are supported.
No. The builder works with free Elementor. With Pro, Theme Builder templates can be created and listed, but the plugin does not write Pro display conditions — you assign a template’s display location in Elementor itself. Elementor Pro was not in our lab testbed, so Pro-specific behaviour is not claimed as verified.
No. OAuth 2.1 is optional and off by default. The standard path is a scoped bearer token created in wp-admin. OAuth exists for clients and teams that prefer a sign-in and consent flow, dynamic client registration and rotating refresh tokens. Registering clients may be public (PKCE only) or confidential — a confidential client receives a secret that is shown exactly once and stored only as a hash, and must authenticate before any token exchange.
Through scopes and the owning account. Each token carries a subset of the eight scopes, and every call is additionally checked against the live WordPress capabilities of the account that owns the token. Revoke a token at any time under LIYANS MCP → Connection; demoting the account reduces its tokens’ power immediately. The article Understanding scopes and tokens walks through it.
Entirely in your own WordPress database: tokens (as hashes), settings, device and OAuth records, build sessions, snapshots and the audit log live in the plugin’s options and its two tables. Nothing is stored on any server of ours — there is no server of ours in the design.
The declared minimums are WordPress 6.5+ and PHP 7.4+. Honestly: multisite and a PHP 7.4 runtime are on the open verification list — the lab-verified environment is a current PHP with WordPress 7.1.4 on a single-site install. We would rather tell you that than let you discover it.
Yes. Builder output is a native Elementor element tree — the same data the Elementor editor itself writes. Open the draft in Elementor and edit it like any hand-built page.
Yes — every release archive is published with its SHA-256 on the Downloads page. Compare the hash of your file before installing.
Through LIYANS DIGITAL — see the Contact page. Checking the plugin’s Diagnostics screen in wp-admin first, and mentioning its results, makes any support exchange shorter. Priority support as a paid service is planned but not yet offered, so nothing about response times is promised today.