Each tool is a first-class MCP tool with its own JSON Schema, required scopes and WordPress capability checks. tools/list is filtered by your token’s scopes — a token holding all eight scopes sees all 61 tools; a narrower token sees fewer, and calling outside its scopes is refused.
Understand and manage the site itself: structure, pages, menus (including theme locations and assignments), media, settings through a strict allowlist, the static homepage, installed plugin and theme inventories, structure export/import, revision snapshots with restore, and safe image import from a public URL (WordPress safe remote fetch, image MIME allowlist, size cap).
liyans_site_inspectliyans_list_pagesliyans_get_pageliyans_get_site_structureliyans_update_contentliyans_list_medialiyans_set_media_altliyans_list_menusliyans_add_menu_itemliyans_upsert_menuliyans_assign_menu_locationliyans_get_site_settingsliyans_site_settingsliyans_set_homepageliyans_list_pluginsliyans_list_themesliyans_preview_urlliyans_export_structureliyans_import_structureliyans_revision_snapshotliyans_restore_snapshotliyans_import_image
Build and refine Elementor pages: full layouts from a spec, HTML converted to native Elementor elements, visual specs turned into layouts, element-level append and remove (snapshot-first), widget discovery with live control schemas, template listing, a structural design audit that also reads the active kit’s global colours and fonts, and two layers of verification — structural, plus rendered-output checks. More on the builder →
liyans_build_layoutliyans_import_htmlliyans_import_visual_specliyans_update_pageliyans_delete_pageliyans_theme_builderliyans_get_elementor_widgetsliyans_inspect_widgetliyans_list_templatesliyans_append_elementsliyans_remove_elementliyans_verify_layoutliyans_render_checkliyans_design_audit
Note: liyans_delete_page moves a page to the WordPress Trash. Nothing in the plugin deletes content permanently.
For WooCommerce stores: product list/create/update, a store overview (revenue figures only for users holding the reports capability), product terms and attributes, variations, and a payment-gateway inspector that returns ids, titles and enabled state only — never gateway settings or credential values. For SEO: a per-page audit, a deep metadata inspector covering Yoast SEO and Rank Math (including canonical and social fields), and meta writes that update both plugins when both are active. For forms: deep, read-only inspection of Contact Form 7 and WPForms definitions — fields and mail/notification configuration, never submission data. ACF field groups can be read where Advanced Custom Fields is present.
liyans_list_productsliyans_create_productliyans_update_productliyans_store_overviewliyans_list_product_termsliyans_create_product_termliyans_list_product_attributesliyans_list_product_variationsliyans_inspect_payment_gatewaysliyans_seo_auditliyans_inspect_seoliyans_set_seo_metaliyans_list_formsliyans_inspect_formliyans_get_acf_fields
Dependency-gated tools answer dependency_missing when their integration is not active on the site — a clear refusal, never a guess.
Multi-page work as a resumable session instead of a pile of one-off calls. Starting a session validates the plan up front and reports per-page slug conflicts before anything is written. Pages are then built one call at a time — across requests, across days — rebuilding a page takes a snapshot first, and finalising closes the session. Sessions are stored server-side, belong to the credential’s WordPress user, and are invisible to other users.
liyans_start_build_sessionliyans_list_build_sessionsliyans_get_build_sessionliyans_build_session_pageliyans_finalize_build_session
Each connected app or machine can have its own device record: its own client id, secret (shown once), scope list and responsive overrides. Overrides support exactly three keys — mobile_direction, hide_widget_types and section_settings — and unknown keys are rejected.
liyans_list_devicesliyans_register_deviceliyans_revoke_deviceliyans_get_device_overridesliyans_set_device_overrides
liyans://site/inspect — a live site-inspection snapshot, produced through the ordinary tool pipeline so scope and capability checks apply. liyans://tools — the tool catalogue as visible to the current caller.
Three ready-made workflow templates: build_landing_page, audit_page_seo and redesign_page — structured starting points your client can fill with arguments.
The server speaks the legacy MCP revisions 2025-11-25, 2025-06-18 and 2024-11-05 — and, since 1.4.0, the 2026-07-28 profile on the same endpoint: modern clients call server/discover and negotiate per request, receiving resultType envelopes on every result and ttlMs/cacheScope on list results (subscriptions/listen is not implemented and is not advertised). It handles batch request arrays item by item, and reports tool argument problems as tool errors (isError: true, per SEP-1303) while protocol problems stay JSON-RPC errors. Every tool also carries honest annotations in tools/list — read-only and destructive hints that follow each tool’s scope and real behaviour — and the eight tools whose result shapes were verified identical across the 1.3.1 and 1.4.0 live runs publish an outputSchema.