Elementor MCP Connections — MCP Apps on NV oOS Assistants
Operational guide for connecting Elementor MCP servers (remote WordPress +
Elementor sites) to NV oOS assistants through the Pro "MCP Apps" subsystem.
Verified against plugin v1.1.91 source (addons/pro/includes/mcp-apps/,
includes/assistants/metaboxes/class-wp-mcp-ai-metabox-mcp-apps.php,
addons/pro/includes/slash-commands/) and the Elementor MCP / WordPress MCP
Adapter public documentation (2026-09).
When to use this skill
- Connecting an assistant to an Elementor MCP server (official Elementor MCP
or a third-party Elementor MCP plugin).
- Creating or editing a Remote Sites connection with connection type
mcp_server, or wiring an assistant to one via connection_ref
("Add from Remote Sites").
- Using the MCP Apps metabox on the assistant editor, the
/mcp-app
slash command, or the mcp-ai/v1/mcp-apps REST routes.
- Troubleshooting "Test Connection" / "Discover Tools" failures, allowlist
rejections, or Elementor tools not appearing in chat.
- Deciding auth type for WordPress application-password-based servers.
- Anything touching assistant meta
_wp_mcp_ai_mcp_apps /
_wp_mcp_ai_mcp_app_status or the mcp_app_* bridged tool slugs.
Mental model
Elementor site (remote) NV oOS site (this plugin)
──────────────────────────── ────────────────────────────────
Elementor MCP server (official or plugin) Assistant CPT post
/wp-json/mcp/<server-slug> ◄──JSON-RPC 2.0── _wp_mcp_ai_mcp_apps meta
Streamable HTTP + app password over (up to 10 app configs)
HTTP WP_MCP_AI_MCP_App_Client
WP_MCP_AI_MCP_App_Registry
├─ tools/list discovery
├─ WP_MCP_AI_MCP_App_Tool_Bridge
│ → local tools mcp_app_<label>_<name>
└─ wp_mcp_ai_chat_effective_tools seam
→ bridged tools in chat payload
The remote side runs Elementor MCP (built on the WordPress Abilities API
- the official MCP Adapter). The local side is the Pro MCP Apps subsystem:
it discovers the remote server's tools and re-registers each as a local
mcp_app_* tool so the assistant can call Elementor operations through normal
chat tool execution. Bridged tools register at chat time (not in the Tools
metabox) and are appended to the LLM payload via the
wp_mcp_ai_chat_effective_tools seam, so they are always visible to the
assistant once connected.
Elementor MCP on the remote site — requirements and setup
Official Elementor MCP (Elementor Core/Pro 4.3.0+)
- Requirements (Elementor's stated minimums): WordPress 6.8+ (Abilities
API is 6.9+ core, so prefer 6.9+), Elementor Core and Pro 4.3.0+.
- Enable: WP Admin → Elementor → Elementor MCP (or Elementor →
Editor → Elementor MCP) → Enable MCP access → pick the client tab
(Claude Code, Claude Desktop, Codex, Cursor, or Other) → tick the
acknowledgment → Generate Prompt → Copy prompt.
- What that prompt contains: an application password (created under
the logged-in user, named "Elementor MCP – ") plus a ready-to-paste
MCP client config. Extract the server URL and the username +
application password from it — those are the two inputs the NV oOS MCP
App needs.
- Permission model: the connected AI inherits the exact capabilities of
the WordPress user the application password belongs to. It cannot edit
pages, publish, or change site settings beyond that role. Always create a
dedicated, least-privilege user for MCP access (industry best practice
from the WordPress MCP Adapter guidance).
- Revoke: per-client — Users → Profile → Application Passwords →
Revoke next to "Elementor MCP – ". Site-wide — Elementor →
Elementor MCP → Turn off MCP access (blocks all connected agents).
- Do not guess the endpoint slug. Copy the URL from the generated prompt.
Typical shapes across the ecosystem:
https://site.com/wp-json/mcp/<server-slug>
(e.g. mcp-adapter-default-server, third-party elementor-mcp-server,
emcp-tools-server). The slug is per-plugin/per-install.
Third-party Elementor MCP plugins (when the official one is not used)
msrbuilds/elementor-mcp — 200+ tools, per-tool WordPress capability
checks, ready-to-paste config including a .mcpb Claude Desktop bundle.
Digitizers/elementor-mcp — endpoint https://your-site.com/wp-json/mcp/elementor-mcp-server.
emcptools.com (EMCP) — /wp-json/mcp/emcp-tools-server, Freemius-licensed,
up to 509 tools.
bvisible/elementor-mcp-api — REST API + MCP, ships a Claude Code skill.
All of them authenticate with WordPress application passwords. The NV oOS
connection recipes below are identical regardless of which server you use.
Connecting in NV oOS — two paths
Path A (recommended) — Remote Sites connection + assistant reference
For a connection reused across assistants (or needing encrypted central
storage), create it once in NV oOS Pro → Remote Sites → Add Connection:
- Connection type:
MCP Server (Elementor MCP / WordPress MCP Adapter)
(connection_type: mcp_server).
- URL: the full endpoint from the Elementor-generated prompt
(
https://site.com/wp-json/mcp/<server-slug>).
- Authentication:
Basic Auth or Application Password
(username + application password) — the manager maps this onto the MCP
client's basic auth; Custom Header (header name + value, e.g.
Authorization + Bearer user:app-password); Bearer Token; OAuth 2.0
(MCP Authorization spec).
- Test Connection runs a real JSON-RPC handshake; Discover Tools
persists the tool count on the connection. Credentials are encrypted at
rest (AES-256-CBC) like every other remote-site secret.
- On the assistant editor → MCP Apps metabox → Add from Remote Sites
→ pick the connection. This creates a reference entry
(
connection_ref + label + enabled) — the credential lives centrally and
is resolved (decrypt-on-use) at chat time. Rotating the application
password in Remote Sites updates every referencing assistant.
(v1.1.90): the dropdown also lists Upwork-in-MCP-mode connections
(labelled Name (Upwork MCP — https://mcp.upwork.com/mcp)) —
resolve_connection_ref() resolves those refs via
build_upwork_mcp_app_config() (official gateway + the decrypted central
mcp_oauth blob), the import validator no longer auto-disables them, and
finalize_oauth_flow() persists the reference entry onto the assistant
after the OAuth login completes.
(v1.1.93): FlowHub-in-MCP-mode connections get the same treatment
(PR #6854) — the dropdown labels them
Name (FlowHub MCP — https://mcp.flowhub.com), get_mcp_app_connections()
merges them, is_mcp_app_connection() accepts them (import-validator
fix via the shared predicate), update_mcp_oauth() persists their OAuth
to the encrypted central store, test_connection() runs a real JSON-RPC
handshake (test_flowhub_mcp_connection()), and resolve_connection_ref()
resolves FlowHub refs via build_flowhub_mcp_app_config() (optional
flowhub_mcp_url override, decrypted mcp_oauth, connection_ref
auto-refresh). Proxy inheritance (PR #6861): build_flowhub_mcp_app_config()
maps the connection's proxy into the app config as proxy_url/proxy_auth
(proxy password decrypted from the connection record, FlowHub toolkit
settings proxy as fallback — the same resolution order as the sync engine);
WP_MCP_AI_MCP_App_Client + WP_MCP_AI_MCP_App_OAuth_Client (all five
outbound call sites via run_proxied_request()) route FlowHub gateway
traffic through the proxy via the http_api_curl cURL layer — geo-blocked
deployments need no direct egress to mcp.flowhub.com. In-process
same-origin dispatch stays direct. (v1.1.94): the proxy now also rides
the OAuth login flow (PR #6867) —
WP_MCP_AI_REST_MCP_Apps_Controller::get_oauth_client_options() resolves
proxy/timeout/SSL options from the connection_ref (or a gateway-URL
match for inline rows) and initiate_oauth() persists them in the
flow-state transient, so the callback/complete/probe/refresh/revoke
handlers rebuild the client with the same options — geo-blocked
deployments can complete the web login, not just the connection test.
Path B — inline MCP App (per-assistant)
Assistant editor → MCP Apps metabox → Add MCP App. Fields (sanitized
by WP_MCP_AI_MCP_App_Registry::sanitize_app_config()):
| Field |
Notes |
label |
Friendly name; drives the bridge slug (mcp_app_<label>_<tool>). Use something short like elementor so slugs read mcp_app_elementor_read_page. |
server_url |
Full MCP endpoint URL from the Elementor-generated prompt. Must pass is_url_allowed() (scheme http/https + host + allowlist when configured). Omitted on reference entries. |
connection_ref |
(Reference mode) ID of a central Remote Sites connection — mcp_server, Upwork-in-MCP-mode (v1.1.90+), or FlowHub-in-MCP-mode (v1.1.93+). Resolved at chat time; the row renders read-only with a "Managed in Remote Sites" badge. |
auth_type |
none, bearer, basic, header, or oauth. See the mapping below. |
token |
Bearer token / Basic credentials / raw header value / OAuth access token. Masked in the UI — never echoed back after save; leaving it blank preserves the stored value. |
header_name |
Custom header name, only for auth_type: header. |
enabled |
Per-app on/off switch (default true). |
timeout |
1–120 s (default 30). |
verify_ssl |
Default true. |
Hard limits (constants on the registry): 10 apps per assistant
(MAX_APPS_PER_ASSISTANT), 2 MB max response body (MAX_RESPONSE_SIZE),
5-minute discovery cache (CACHE_TTL), 60-second negative cache
(FAILURE_CACHE_TTL).
Auth mapping for Elementor MCP (application passwords)
WordPress application passwords authenticate over HTTP Basic. Two supported
mappings, pick by what the server expects:
- Preferred —
auth_type: basic, token: <wp-username>:<application-password>.
The client auto-base64-encodes the credentials; a : in the token is the
encode trigger, so raw user:pass input is fine. Application passwords
print with spaces (e.g. 2SEB qW5j D7CW fpsh pbmN RGva) — paste without the
spaces in the password portion.
- Alternative —
auth_type: header, header_name: Authorization,
token: Bearer <wp-username>:<application-password> — for servers that read
the application password from an Authorization: Bearer user:pass header
(documented by some WordPress MCP plugins).
oauth is for servers running real OAuth 2.0 (metadata discovery, DCR, PKCE,
refresh) — Elementor MCP does not use it; use basic/header instead.
Discovery (v1.1.91+) walks the full MCP Authorization spec chain:
WP_MCP_AI_MCP_App_OAuth_Client::discover_metadata() tries RFC 8414 metadata
on the MCP origin + the §3.2 path-insertion variant, then RFC 9728
protected-resource metadata (every advertised authorization_servers entry),
then the 401 WWW-Authenticate: Bearer resource_metadata probe, then OIDC
.well-known/openid-configuration, then the WordPress REST metadata fallback.
RFC 8414 documents are accepted only with both authorization_endpoint and
token_endpoint; every attempt is recorded and the metabox failure alert
surfaces the real transport error (attempts + hint), the
server-advertised default_scope is honored, and per-probe timeouts cap at
10 s — so a "discovery failed" alert now tells you which step failed.
Test, discover, import
- Test Connection — runs the JSON-RPC handshake and renders a status badge
(Connected / Error / Not tested) persisted to
_wp_mcp_ai_mcp_app_status.
- Discover Tools — fetches
tools/list and shows the tool count; results
are cached 5 minutes keyed by config hash.
- JSON import — paste a
mcpServers block (Claude Desktop / Claude Code /
Cursor format) to bulk-fill rows; entries are capped at the 10-app limit.
This is the fastest path when the user already has an Elementor-generated
client config — paste it and let the importer extract URL + credentials.
- Same-site URLs (the Elementor MCP endpoint lives on this WordPress site)
are routed in-process via
rest_do_request() instead of an outbound HTTP
call, avoiding PHP-FPM pool deadlocks / hairpin-NAT stalls. The metabox JS
warns when it detects this.
Verification and troubleshooting
Slash command /mcp-app (chat surface, requires manage_options, guests blocked)
/mcp-app # list apps for the current assistant
/mcp-app --test=<label> # test one app's connection
/mcp-app --discover=<label> # re-run tool discovery for one app
/mcp-app --assistant-id=<n> --json
REST (namespace mcp-ai/v1, admin-gated)
POST /mcp-apps/test — server_url, auth fields → handshake result.
POST /mcp-apps/discover — server_url, assistant_id → tool list.
GET /mcp-apps/{assistant_id} — stored configs (tokens redacted in output —
verify masking before claiming otherwise).
POST /mcp-apps/oauth/{probe,init,refresh,revoke}, GET /mcp-apps/oauth/callback,
POST /mcp-apps/oauth/complete (manual loopback paste-back, 10-min state TTL).
Failure patterns (root-cause order)
- "host is not on the configured allowlist" (403) — the URL guard
(
is_url_allowed()) is rejecting the host. Add it to Settings →
Security Center → Network & Headers → "MCP App Allowed Hosts" (textarea,
one host per line, stored as mcp_app_allowed_hosts in wp_mcp_ai_settings).
Precedence: WP_MCP_AI_MCP_APP_ALLOWED_HOSTS constant (hard override when
defined — UI setting is then ignored) → wp_mcp_ai_mcp_app_allowed_hosts
filter → saved setting. Never bypass the guard for "internal" servers —
add an allowlist entry instead. Note: with no allowlist configured the
guard is permissive (logs a warning); the code checks scheme + host only —
it does NOT block loopback/private IPs, so an empty allowlist is genuinely
open to arbitrary upstream servers. Recommend always configuring one.
- Test Connection fails on an older server — the client first attempts
the stateless
server/discover handshake (protocol 2026-07-28) and
auto-falls back to the legacy sessionful initialize handshake when the
server returns -32601/-32600/session errors or a bare HTTP
400/404/405/501 without a JSON-RPC error envelope (strict 2025-era
gateways reject the unknown method that way). The fallback initialize
handshake and every request inside a legacy session omit the 2026-only
MCP-Protocol-Version/Mcp-Method routing headers and the _meta
envelope, so they look exactly like a 2025-era client (Claude Desktop /
Cursor shape). Once a legacy fallback succeeds, a per-URL dialect hint
(transient wp_mcp_ai_mcp_app_legacy_<md5>, 24h) skips the doomed probe on
subsequent tests/connects (saves one round trip per connect cycle; visible
as Handshake: initialize with no server/discover on the wire). A stale
hint self-heals: if initialize is rejected with a stateless signature
(-32601/-32600 or HTTP 400/404/405/501), the hint is cleared and
discover() is retried. A bare "connection failed" with a 2xx response
usually means the URL points at the wrong route slug — re-check against the
generated prompt.
- Tools discovered but missing from chat — bridged tools require the
edit_posts capability check at execution and are only appended when the
effective-tools seam resolves the assistant ID. Check: app enabled is
true, the discovery cache isn't stale (re-run Discover Tools), and the
negative cache (60 s) isn't masking a temporarily-down server. Saving apps
invalidates both the discovery cache and the /tools REST listing cache.
- "Tool enumeration failed: MCP server returned invalid JSON" — some
gateways (Envoy AI Gateway / Agent Router) answer
initialize with plain
JSON but every post-initialize request (tools/list, tools/call) with an
SSE stream (text/event-stream, event: message + data: {…}). The
client now detects SSE via the Content-Type header or data: body
sniffing (some gateways mislabel SSE as application/json) and extracts
the JSON-RPC message via parse_sse_payload(); an empty stream surfaces
the dedicated wp_mcp_ai_mcp_app_empty_sse error. On older builds, update
the plugin and re-run Test Connection.
- "No OAuth access token available" after a successful web login — the
metabox never sends
oauth_data back (credentials are masked server-side).
Current builds restore the stored oauth_data blob (including client_id,
which Upwork requires on token/refresh requests) in resolve_stored_token(),
persist rotated tokens (inline assistant meta / central update_mcp_oauth()),
and re-hydrate the freshest credentials before each bridge execution.
- "Response errors mid-chat" — remote bodies are capped at 2 MB; a larger
payload surfaces a truncation error, not a silent drop.
verify_ssl: false
is only for self-signed staging endpoints — prefer adding the CA instead.
- Elementor tools exist but calls are denied — the remote WordPress user
(application password owner) lacks the capability; fix the role on the
Elementor site, not the NV oOS config.
- "connection_ref not found in Remote Sites" — a reference entry points
at a deleted/renamed central connection. Recreate the connection in Remote
Sites, or remove the reference row from the MCP Apps metabox. Imported
bundles with missing references are auto-disabled with a warning
(
wp_mcp_ai_mcp_apps_validate_imported_refs).
- Restricted-host rejection (Remote Sites) — the
mcp_server type runs
the manager's private/reserved-range guard (no bypass); localhost/private
endpoints must use the inline MCP App path (Path B), while the site's own
public hostname still routes in-process via the same-site bridge.
- Upwork MCP (
https://mcp.upwork.com/mcp) returns "HTTP 400" — Upwork's
gateway rejects the 2026-07-28 server/discover probe with a bare HTTP
400, which older client builds never fell back from. Verified fix (client
- registry fallback on 400/404/405/501, legacy-header omission) shipped in
the mcp-apps cluster — deploy it and re-run Test Connection / Discover
Tools. Remote Sites freelance-marketplace mode: Upwork connections
(
connection_type: upwork) also accept upwork_mode: mcp, which drives
the CRM search/import tools through the same gateway (upwork__find_jobs
action search/get, upwork__list_accounts for org_uid); the login
flow is the MCP Apps REST flow with connection_ref set to the Upwork
connection ID, persisting tokens to its encrypted mcp_oauth field.
Diagnostics caveat: Upwork binds OAuth access tokens to the
originating server IP, so reproducing the handshake with curl from
another machine returns 401 even with a valid token — validate on the site
itself (the HTTP-error WP_Error data now includes a 400-char response
body snippet). Upwork auth is OAuth 2.1 with DCR and loopback-only
redirect URIs: the login tab ends on
http://localhost:<port>/callback?code=...&state=... that never loads —
paste that URL into the metabox's manual paste field and click Complete
Login within the 10-minute state TTL. An expired state returns "This
login link has expired" — re-initiate and paste the new URL. The paste-back
box is always visible for unauthenticated OAuth rows (survives page
reloads), and token exchange/refresh now send client_id in the request
body (Upwork rejects requests without it with
invalid_request: Missing parameters: client_id).
Security rules (industry + plugin)
- Least privilege on both ends. On the Elementor site, a dedicated user
with the minimum role the workflow needs; on the NV oOS site, bridged tools
still pass per-tool capability gating (
edit_posts).
- Central connections are encrypted at rest.
mcp_server Remote Sites
credentials (password, token, mcp_oauth blob) use the manager's AES-256-CBC
scheme — prefer Path A for production. Inline MCP App secrets (Path B: token,
oauth_data access/refresh) are also encrypted at rest since v1.1.88
(same scheme) and masked in the metabox with blank-submit preservation —
never echo them into chat logs, commits, or docs. Record them in the Vault
(see design-vault). Remote Sites verify_token (WhatsApp/Messenger) and
verification_token (Google Chat) are encrypted too, centrally decrypted in
get_connection(); the three raw-store webhook read sites decrypt
explicitly. Legacy plaintext rows keep working (decrypt-on-read is
idempotent) and encrypt on their next save. Rotated OAuth tokens persist
back to assistant meta / the central mcp_oauth blob, and central rotations
emit mcp_oauth_refresh activity events with metadata only.
- Revoke when done. Rotate/revoke the application password on the
Elementor site when a connection is decommissioned; deleting the NV oOS app
row or Remote Sites connection does not revoke the remote credential.
- Export/import: the assistant portability engine redacts inline
token /
oauth_data fields on export and strips them from imports by default;
connection_ref entries export as non-secret pointers (no credentials
ever ride in assistant bundles). Remote Sites backups
(WP_MCP_AI_Export_Provider_Remote_Sites) decrypt/re-encrypt credentials by
design (trusted migration, contains_sensitive_data=true). Opt-out filters
for assistant bundles: wp_mcp_ai_assistant_export|import_redact_mcp_app_tokens
(default true). See the portability skill.
- Prefer read-only ability sets on public endpoints (WordPress MCP Adapter
guidance): if the Elementor MCP endpoint is internet-reachable, the remote
server should expose read/diagnostic abilities rather than destructive ones.
- Monitor usage — tool-execution telemetry fires for bridged tools like
any other tool; MCP Server test/discover events are activity-logged; review
logs after Elementor write operations.
Code map (verified, v1.1.90)
| Concern |
Location |
| Registry (meta keys, allowlist, discovery, status, reference resolution) |
addons/pro/includes/mcp-apps/class-wp-mcp-ai-mcp-app-registry.php |
| Transport client (handshake, auth types, fallback) |
addons/pro/includes/mcp-apps/class-wp-mcp-ai-mcp-app-client.php |
| Tool bridge |
addons/pro/includes/mcp-apps/class-wp-mcp-ai-mcp-app-tool-bridge.php |
| OAuth client |
addons/pro/includes/mcp-apps/class-wp-mcp-ai-mcp-app-oauth-client.php |
| REST controller |
addons/pro/includes/mcp-apps/class-wp-mcp-ai-rest-mcp-apps-controller.php |
| Registration + effective-tools seam + import-ref validator |
addons/pro/includes/mcp-apps/mcp-apps-init.php |
Remote Sites mcp_server type (save/validate/test/discover/mapping) |
addons/pro/includes/class-wp-mcp-ai-pro-remote-site-manager.php |
| Remote Sites admin UI (type option, MCP fields, toggles) |
addons/pro/includes/admin/class-wp-mcp-ai-pro-remote-sites-admin.php |
| Assistant metabox (UI, badges, JSON import, Add from Remote Sites, ref rows) |
includes/assistants/metaboxes/class-wp-mcp-ai-metabox-mcp-apps.php |
| Slash command |
addons/pro/includes/slash-commands/commands/class-wp-mcp-ai-pro-slash-command-mcp-app.php |
| Folder contract |
addons/pro/includes/mcp-apps/README.md |
Key constants: META_KEY = '_wp_mcp_ai_mcp_apps',
STATUS_META_KEY = '_wp_mcp_ai_mcp_app_status', MAX_APPS_PER_ASSISTANT = 10,
CACHE_TTL = 300, FAILURE_CACHE_TTL = 60,
PROTOCOL_VERSION = '2026-07-28', MAX_RESPONSE_SIZE = 2 MB.
Cross-references
design-elementor-template-kits — designing/building/importing Elementor
page content once connected (kits vs live MCP editing are different tracks;
MCP Apps give the agent live editing tools, kits give offline import).
design-ai-assistant-admin — assistant-level configuration this skill
plugs into (meta keys, capability gates).
mcp-ai-wpoos-assistant-portability — export/import of assistants carrying
MCP App configs (token caveat above).
mcp-ai-wpoos-plugin — JSON-RPC over HTTP mechanics shared with the MCP
bridge.
design-vault — store the application passwords/tokens.
wp-security-deep — SSRF review of the URL guard before touching it.
wp-security-secrets — auditing token storage/handling.
What this skill does NOT cover
- Running the NV oOS plugin as an MCP server for other clients — that is the
inverse direction; see
addons/pro/includes/mcp-servers/.
- Authoring Elementor template kits or fixing kit imports —
design-elementor-template-kits.
- Writing Elementor abilities on the remote site (wp_register_ability /
MCP Adapter development) — WordPress developer docs.
- The general chat UI / Elementor widget embeds of NV oOS — plugin chat docs.
References
1---2type: Skill3name: design-elementor-mcp-connection4description: Connect and manage Elementor MCP servers as "MCP Apps" on NV oOS assistants — official Elementor MCP (application passwords, permission inheritance, enable/revoke flows), third-party Elementor MCP plugins, the Pro MCP Apps metabox/slash-command/REST surfaces, the Remote Sites "MCP Server" connection type with assistant connection_ref references, auth-type mapping (basic vs header vs oauth), the host allowlist (Security Center setting, constant, filter), tool discovery/bridging into chat, and troubleshooting (allowlist 403s, restricted hosts, protocol fallback, negative discovery cache, same-site in-process bridge, missing connection_ref). Use when connecting an assistant to Elementor MCP, creating a Remote Sites MCP Server connection, using /mcp-app, fixing Test Connection or Discover Tools failures, allowlisting an Elementor host, or debugging bridged elementor_* tools missing from chat.5license: Proprietary. See LICENSE.txt6metadata:7 source: https://skillmd.com/skills/nvdigitalsolutions/design-elementor-mcp-connection8 type: Skill9 plugin: mcp-ai-wpoos10 plugin-version: "1.1.94"11 plugin-version-tested: "1.1.94"12 last-updated: "2026-10-03"13---1415# Elementor MCP Connections — MCP Apps on NV oOS Assistants1617Operational guide for connecting Elementor MCP servers (remote WordPress +18Elementor sites) to NV oOS assistants through the Pro "MCP Apps" subsystem.19Verified against plugin v1.1.91 source (`addons/pro/includes/mcp-apps/`,20`includes/assistants/metaboxes/class-wp-mcp-ai-metabox-mcp-apps.php`,21`addons/pro/includes/slash-commands/`) and the Elementor MCP / WordPress MCP22Adapter public documentation (2026-09).2324## When to use this skill2526- Connecting an assistant to an Elementor MCP server (official Elementor MCP27 or a third-party Elementor MCP plugin).28- Creating or editing a **Remote Sites** connection with connection type29 `mcp_server`, or wiring an assistant to one via `connection_ref`30 ("Add from Remote Sites").31- Using the **MCP Apps** metabox on the assistant editor, the `/mcp-app`32 slash command, or the `mcp-ai/v1/mcp-apps` REST routes.33- Troubleshooting "Test Connection" / "Discover Tools" failures, allowlist34 rejections, or Elementor tools not appearing in chat.35- Deciding auth type for WordPress application-password-based servers.36- Anything touching assistant meta `_wp_mcp_ai_mcp_apps` /37 `_wp_mcp_ai_mcp_app_status` or the `mcp_app_*` bridged tool slugs.3839## Mental model4041```42Elementor site (remote) NV oOS site (this plugin)43──────────────────────────── ────────────────────────────────44Elementor MCP server (official or plugin) Assistant CPT post45 /wp-json/mcp/<server-slug> ◄──JSON-RPC 2.0── _wp_mcp_ai_mcp_apps meta46 Streamable HTTP + app password over (up to 10 app configs)47 HTTP WP_MCP_AI_MCP_App_Client48 WP_MCP_AI_MCP_App_Registry49 ├─ tools/list discovery50 ├─ WP_MCP_AI_MCP_App_Tool_Bridge51 │ → local tools mcp_app_<label>_<name>52 └─ wp_mcp_ai_chat_effective_tools seam53 → bridged tools in chat payload54```5556The remote side runs Elementor MCP (built on the WordPress **Abilities API**57+ the official **MCP Adapter**). The local side is the Pro MCP Apps subsystem:58it discovers the remote server's tools and re-registers each as a local59`mcp_app_*` tool so the assistant can call Elementor operations through normal60chat tool execution. Bridged tools register at chat time (not in the Tools61metabox) and are appended to the LLM payload via the62`wp_mcp_ai_chat_effective_tools` seam, so they are always visible to the63assistant once connected.6465## Elementor MCP on the remote site — requirements and setup6667### Official Elementor MCP (Elementor Core/Pro 4.3.0+)68691. **Requirements** (Elementor's stated minimums): WordPress 6.8+ (Abilities70 API is 6.9+ core, so prefer 6.9+), Elementor Core and Pro 4.3.0+.712. **Enable:** WP Admin → **Elementor → Elementor MCP** (or Elementor →72 Editor → Elementor MCP) → **Enable MCP access** → pick the client tab73 (Claude Code, Claude Desktop, Codex, Cursor, or Other) → tick the74 acknowledgment → **Generate Prompt** → **Copy prompt**.753. **What that prompt contains:** an **application password** (created under76 the logged-in user, named "Elementor MCP – <client>") plus a ready-to-paste77 MCP client config. Extract the **server URL** and the **username +78 application password** from it — those are the two inputs the NV oOS MCP79 App needs.804. **Permission model:** the connected AI inherits the exact capabilities of81 the WordPress user the application password belongs to. It cannot edit82 pages, publish, or change site settings beyond that role. **Always create a83 dedicated, least-privilege user for MCP access** (industry best practice84 from the WordPress MCP Adapter guidance).855. **Revoke:** per-client — **Users → Profile → Application Passwords →86 Revoke** next to "Elementor MCP – <client>". Site-wide — **Elementor →87 Elementor MCP → Turn off MCP access** (blocks all connected agents).886. **Do not guess the endpoint slug.** Copy the URL from the generated prompt.89 Typical shapes across the ecosystem: `https://site.com/wp-json/mcp/<server-slug>`90 (e.g. `mcp-adapter-default-server`, third-party `elementor-mcp-server`,91 `emcp-tools-server`). The slug is per-plugin/per-install.9293### Third-party Elementor MCP plugins (when the official one is not used)9495- `msrbuilds/elementor-mcp` — 200+ tools, per-tool WordPress capability96 checks, ready-to-paste config including a `.mcpb` Claude Desktop bundle.97- `Digitizers/elementor-mcp` — endpoint `https://your-site.com/wp-json/mcp/elementor-mcp-server`.98- `emcptools.com` (EMCP) — `/wp-json/mcp/emcp-tools-server`, Freemius-licensed,99 up to 509 tools.100- `bvisible/elementor-mcp-api` — REST API + MCP, ships a Claude Code skill.101102All of them authenticate with WordPress **application passwords**. The NV oOS103connection recipes below are identical regardless of which server you use.104105## Connecting in NV oOS — two paths106107### Path A (recommended) — Remote Sites connection + assistant reference108109For a connection reused across assistants (or needing encrypted central110storage), create it once in **NV oOS Pro → Remote Sites → Add Connection**:1111121. **Connection type:** `MCP Server (Elementor MCP / WordPress MCP Adapter)`113 (`connection_type: mcp_server`).1142. **URL:** the full endpoint from the Elementor-generated prompt115 (`https://site.com/wp-json/mcp/<server-slug>`).1163. **Authentication:** `Basic Auth` or `Application Password`117 (`username` + application password) — the manager maps this onto the MCP118 client's `basic` auth; `Custom Header` (header name + value, e.g.119 `Authorization` + `Bearer user:app-password`); `Bearer Token`; `OAuth 2.0`120 (MCP Authorization spec).1214. **Test Connection** runs a real JSON-RPC handshake; **Discover Tools**122 persists the tool count on the connection. Credentials are encrypted at123 rest (AES-256-CBC) like every other remote-site secret.1245. On the assistant editor → **MCP Apps** metabox → **Add from Remote Sites**125 → pick the connection. This creates a **reference entry**126 (`connection_ref` + label + enabled) — the credential lives centrally and127 is resolved (decrypt-on-use) at chat time. Rotating the application128 password in Remote Sites updates every referencing assistant.129 **(v1.1.90):** the dropdown also lists **Upwork-in-MCP-mode** connections130 (labelled `Name (Upwork MCP — https://mcp.upwork.com/mcp)`) —131 `resolve_connection_ref()` resolves those refs via132 `build_upwork_mcp_app_config()` (official gateway + the decrypted central133 `mcp_oauth` blob), the import validator no longer auto-disables them, and134 `finalize_oauth_flow()` persists the reference entry onto the assistant135 after the OAuth login completes.136 **(v1.1.93):** **FlowHub-in-MCP-mode** connections get the same treatment137 (PR #6854) — the dropdown labels them138 `Name (FlowHub MCP — https://mcp.flowhub.com)`, `get_mcp_app_connections()`139 merges them, `is_mcp_app_connection()` accepts them (import-validator140 fix via the shared predicate), `update_mcp_oauth()` persists their OAuth141 to the encrypted central store, `test_connection()` runs a real JSON-RPC142 handshake (`test_flowhub_mcp_connection()`), and `resolve_connection_ref()`143 resolves FlowHub refs via `build_flowhub_mcp_app_config()` (optional144 `flowhub_mcp_url` override, decrypted `mcp_oauth`, `connection_ref`145 auto-refresh). **Proxy inheritance (PR #6861):** `build_flowhub_mcp_app_config()`146 maps the connection's proxy into the app config as `proxy_url`/`proxy_auth`147 (proxy password decrypted from the connection record, FlowHub toolkit148 settings proxy as fallback — the same resolution order as the sync engine);149 `WP_MCP_AI_MCP_App_Client` + `WP_MCP_AI_MCP_App_OAuth_Client` (all five150 outbound call sites via `run_proxied_request()`) route FlowHub gateway151 traffic through the proxy via the `http_api_curl` cURL layer — geo-blocked152 deployments need no direct egress to `mcp.flowhub.com`. In-process153 same-origin dispatch stays direct. **(v1.1.94):** the proxy now also rides154 the **OAuth login flow** (PR #6867) —155 `WP_MCP_AI_REST_MCP_Apps_Controller::get_oauth_client_options()` resolves156 proxy/timeout/SSL options from the `connection_ref` (or a gateway-URL157 match for inline rows) and `initiate_oauth()` persists them in the158 flow-state transient, so the callback/complete/probe/refresh/revoke159 handlers rebuild the client with the same options — geo-blocked160 deployments can complete the web login, not just the connection test.161162### Path B — inline MCP App (per-assistant)163164Assistant editor → **MCP Apps** metabox → **Add MCP App**. Fields (sanitized165by `WP_MCP_AI_MCP_App_Registry::sanitize_app_config()`):166167| Field | Notes |168|---|---|169| `label` | Friendly name; drives the bridge slug (`mcp_app_<label>_<tool>`). Use something short like `elementor` so slugs read `mcp_app_elementor_read_page`. |170| `server_url` | Full MCP endpoint URL from the Elementor-generated prompt. Must pass `is_url_allowed()` (scheme http/https + host + allowlist when configured). Omitted on reference entries. |171| `connection_ref` | (Reference mode) ID of a central Remote Sites connection — `mcp_server`, Upwork-in-MCP-mode (v1.1.90+), or FlowHub-in-MCP-mode (v1.1.93+). Resolved at chat time; the row renders read-only with a "Managed in Remote Sites" badge. |172| `auth_type` | `none`, `bearer`, `basic`, `header`, or `oauth`. See the mapping below. |173| `token` | Bearer token / Basic credentials / raw header value / OAuth access token. Masked in the UI — never echoed back after save; leaving it blank preserves the stored value. |174| `header_name` | Custom header name, only for `auth_type: header`. |175| `enabled` | Per-app on/off switch (default true). |176| `timeout` | 1–120 s (default 30). |177| `verify_ssl` | Default true. |178179Hard limits (constants on the registry): **10 apps per assistant**180(`MAX_APPS_PER_ASSISTANT`), 2 MB max response body (`MAX_RESPONSE_SIZE`),1815-minute discovery cache (`CACHE_TTL`), 60-second negative cache182(`FAILURE_CACHE_TTL`).183184### Auth mapping for Elementor MCP (application passwords)185186WordPress application passwords authenticate over HTTP Basic. Two supported187mappings, pick by what the server expects:188189- **Preferred — `auth_type: basic`**, `token: <wp-username>:<application-password>`.190 The client auto-base64-encodes the credentials; a `:` in the token is the191 encode trigger, so raw `user:pass` input is fine. Application passwords192 print with spaces (e.g. `2SEB qW5j D7CW fpsh pbmN RGva`) — paste without the193 spaces in the password portion.194- **Alternative — `auth_type: header`**, `header_name: Authorization`,195 `token: Bearer <wp-username>:<application-password>` — for servers that read196 the application password from an `Authorization: Bearer user:pass` header197 (documented by some WordPress MCP plugins).198199`oauth` is for servers running real OAuth 2.0 (metadata discovery, DCR, PKCE,200refresh) — Elementor MCP does not use it; use `basic`/`header` instead.201Discovery (v1.1.91+) walks the full MCP Authorization spec chain:202`WP_MCP_AI_MCP_App_OAuth_Client::discover_metadata()` tries RFC 8414 metadata203on the MCP origin + the §3.2 path-insertion variant, then RFC 9728204protected-resource metadata (every advertised `authorization_servers` entry),205then the 401 `WWW-Authenticate: Bearer resource_metadata` probe, then OIDC206`.well-known/openid-configuration`, then the WordPress REST metadata fallback.207RFC 8414 documents are accepted only with both `authorization_endpoint` and208`token_endpoint`; every attempt is recorded and the metabox failure alert209surfaces the real transport error (`attempts` + `hint`), the210server-advertised `default_scope` is honored, and per-probe timeouts cap at21110 s — so a "discovery failed" alert now tells you *which* step failed.212213### Test, discover, import214215- **Test Connection** — runs the JSON-RPC handshake and renders a status badge216 (Connected / Error / Not tested) persisted to `_wp_mcp_ai_mcp_app_status`.217- **Discover Tools** — fetches `tools/list` and shows the tool count; results218 are cached 5 minutes keyed by config hash.219- **JSON import** — paste a `mcpServers` block (Claude Desktop / Claude Code /220 Cursor format) to bulk-fill rows; entries are capped at the 10-app limit.221 This is the fastest path when the user already has an Elementor-generated222 client config — paste it and let the importer extract URL + credentials.223- Same-site URLs (the Elementor MCP endpoint lives on *this* WordPress site)224 are routed in-process via `rest_do_request()` instead of an outbound HTTP225 call, avoiding PHP-FPM pool deadlocks / hairpin-NAT stalls. The metabox JS226 warns when it detects this.227228## Verification and troubleshooting229230### Slash command `/mcp-app` (chat surface, requires manage_options, guests blocked)231232```233/mcp-app # list apps for the current assistant234/mcp-app --test=<label> # test one app's connection235/mcp-app --discover=<label> # re-run tool discovery for one app236/mcp-app --assistant-id=<n> --json237```238239### REST (namespace `mcp-ai/v1`, admin-gated)240241- `POST /mcp-apps/test` — `server_url`, auth fields → handshake result.242- `POST /mcp-apps/discover` — `server_url`, `assistant_id` → tool list.243- `GET /mcp-apps/{assistant_id}` — stored configs (tokens redacted in output —244 verify masking before claiming otherwise).245- `POST /mcp-apps/oauth/{probe,init,refresh,revoke}`, `GET /mcp-apps/oauth/callback`,246 `POST /mcp-apps/oauth/complete` (manual loopback paste-back, 10-min state TTL).247248### Failure patterns (root-cause order)2492501. **"host is not on the configured allowlist" (403)** — the URL guard251 (`is_url_allowed()`) is rejecting the host. Add it to **Settings →252 Security Center → Network & Headers → "MCP App Allowed Hosts"** (textarea,253 one host per line, stored as `mcp_app_allowed_hosts` in `wp_mcp_ai_settings`).254 Precedence: `WP_MCP_AI_MCP_APP_ALLOWED_HOSTS` constant (hard override when255 defined — UI setting is then ignored) → `wp_mcp_ai_mcp_app_allowed_hosts`256 filter → saved setting. **Never bypass the guard for "internal" servers —257 add an allowlist entry instead.** Note: with no allowlist configured the258 guard is permissive (logs a warning); the code checks scheme + host only —259 it does NOT block loopback/private IPs, so an empty allowlist is genuinely260 open to arbitrary upstream servers. Recommend always configuring one.2612. **Test Connection fails on an older server** — the client first attempts262 the stateless `server/discover` handshake (protocol `2026-07-28`) and263 auto-falls back to the legacy sessionful `initialize` handshake when the264 server returns `-32601`/`-32600`/`session` errors **or a bare HTTP265 400/404/405/501 without a JSON-RPC error envelope** (strict 2025-era266 gateways reject the unknown method that way). The fallback `initialize`267 handshake and every request inside a legacy session omit the 2026-only268 `MCP-Protocol-Version`/`Mcp-Method` routing headers and the `_meta`269 envelope, so they look exactly like a 2025-era client (Claude Desktop /270 Cursor shape). Once a legacy fallback succeeds, a per-URL **dialect hint**271 (transient `wp_mcp_ai_mcp_app_legacy_<md5>`, 24h) skips the doomed probe on272 subsequent tests/connects (saves one round trip per connect cycle; visible273 as `Handshake: initialize` with no `server/discover` on the wire). A stale274 hint self-heals: if `initialize` is rejected with a stateless signature275 (`-32601`/`-32600` or HTTP 400/404/405/501), the hint is cleared and276 `discover()` is retried. A bare "connection failed" with a 2xx response277 usually means the URL points at the wrong route slug — re-check against the278 generated prompt.2793. **Tools discovered but missing from chat** — bridged tools require the280 `edit_posts` capability check at execution and are only appended when the281 effective-tools seam resolves the assistant ID. Check: app `enabled` is282 true, the discovery cache isn't stale (re-run Discover Tools), and the283 negative cache (60 s) isn't masking a temporarily-down server. Saving apps284 invalidates both the discovery cache and the `/tools` REST listing cache.2854. **"Tool enumeration failed: MCP server returned invalid JSON"** — some286 gateways (Envoy AI Gateway / Agent Router) answer `initialize` with plain287 JSON but every post-initialize request (`tools/list`, `tools/call`) with an288 **SSE stream** (`text/event-stream`, `event: message` + `data: {…}`). The289 client now detects SSE via the `Content-Type` header **or** `data:` body290 sniffing (some gateways mislabel SSE as `application/json`) and extracts291 the JSON-RPC message via `parse_sse_payload()`; an empty stream surfaces292 the dedicated `wp_mcp_ai_mcp_app_empty_sse` error. On older builds, update293 the plugin and re-run Test Connection.2945. **"No OAuth access token available" after a successful web login** — the295 metabox never sends `oauth_data` back (credentials are masked server-side).296 Current builds restore the stored `oauth_data` blob (including `client_id`,297 which Upwork requires on token/refresh requests) in `resolve_stored_token()`,298 persist rotated tokens (inline assistant meta / central `update_mcp_oauth()`),299 and re-hydrate the freshest credentials before each bridge execution.3006. **"Response errors mid-chat"** — remote bodies are capped at 2 MB; a larger301 payload surfaces a truncation error, not a silent drop. `verify_ssl: false`302 is only for self-signed staging endpoints — prefer adding the CA instead.3037. **Elementor tools exist but calls are denied** — the remote WordPress user304 (application password owner) lacks the capability; fix the role on the305 Elementor site, not the NV oOS config.3068. **"connection_ref not found in Remote Sites"** — a reference entry points307 at a deleted/renamed central connection. Recreate the connection in Remote308 Sites, or remove the reference row from the MCP Apps metabox. Imported309 bundles with missing references are auto-disabled with a warning310 (`wp_mcp_ai_mcp_apps_validate_imported_refs`).3119. **Restricted-host rejection (Remote Sites)** — the `mcp_server` type runs312 the manager's private/reserved-range guard (no bypass); localhost/private313 endpoints must use the inline MCP App path (Path B), while the site's own314 public hostname still routes in-process via the same-site bridge.31510. **Upwork MCP (`https://mcp.upwork.com/mcp`) returns "HTTP 400"** — Upwork's316 gateway rejects the 2026-07-28 `server/discover` probe with a bare HTTP317 400, which older client builds never fell back from. Verified fix (client318 + registry fallback on 400/404/405/501, legacy-header omission) shipped in319 the mcp-apps cluster — deploy it and re-run Test Connection / Discover320 Tools. **Remote Sites freelance-marketplace mode:** Upwork connections321 (`connection_type: upwork`) also accept `upwork_mode: mcp`, which drives322 the CRM search/import tools through the same gateway (`upwork__find_jobs`323 action `search`/`get`, `upwork__list_accounts` for `org_uid`); the login324 flow is the MCP Apps REST flow with `connection_ref` set to the Upwork325 connection ID, persisting tokens to its encrypted `mcp_oauth` field.326 Diagnostics caveat: Upwork binds OAuth access tokens to the327 originating server IP, so reproducing the handshake with `curl` from328 another machine returns 401 even with a valid token — validate on the site329 itself (the HTTP-error `WP_Error` data now includes a 400-char response330 body snippet). Upwork auth is OAuth 2.1 with DCR and **loopback-only331 redirect URIs**: the login tab ends on332 `http://localhost:<port>/callback?code=...&state=...` that never loads —333 paste that URL into the metabox's manual paste field and click **Complete334 Login** within the 10-minute state TTL. An expired state returns "This335 login link has expired" — re-initiate and paste the new URL. The paste-back336 box is **always visible** for unauthenticated OAuth rows (survives page337 reloads), and token exchange/refresh now send `client_id` in the request338 body (Upwork rejects requests without it with339 `invalid_request: Missing parameters: client_id`).340341## Security rules (industry + plugin)342343- **Least privilege on both ends.** On the Elementor site, a dedicated user344 with the minimum role the workflow needs; on the NV oOS site, bridged tools345 still pass per-tool capability gating (`edit_posts`).346- **Central connections are encrypted at rest.** `mcp_server` Remote Sites347 credentials (password, token, `mcp_oauth` blob) use the manager's AES-256-CBC348 scheme — prefer Path A for production. Inline MCP App secrets (Path B: token,349 `oauth_data` access/refresh) are **also encrypted at rest since v1.1.88**350 (same scheme) and masked in the metabox with blank-submit preservation —351 never echo them into chat logs, commits, or docs. Record them in the Vault352 (see `design-vault`). Remote Sites `verify_token` (WhatsApp/Messenger) and353 `verification_token` (Google Chat) are encrypted too, centrally decrypted in354 `get_connection()`; the three raw-store webhook read sites decrypt355 explicitly. Legacy plaintext rows keep working (decrypt-on-read is356 idempotent) and encrypt on their next save. Rotated OAuth tokens persist357 back to assistant meta / the central `mcp_oauth` blob, and central rotations358 emit `mcp_oauth_refresh` activity events with metadata only.359- **Revoke when done.** Rotate/revoke the application password on the360 Elementor site when a connection is decommissioned; deleting the NV oOS app361 row or Remote Sites connection does not revoke the remote credential.362- **Export/import:** the assistant portability engine redacts inline `token` /363 `oauth_data` fields on export and strips them from imports by default;364 `connection_ref` entries export as **non-secret pointers** (no credentials365 ever ride in assistant bundles). Remote Sites backups366 (`WP_MCP_AI_Export_Provider_Remote_Sites`) decrypt/re-encrypt credentials by367 design (trusted migration, `contains_sensitive_data=true`). Opt-out filters368 for assistant bundles: `wp_mcp_ai_assistant_export|import_redact_mcp_app_tokens`369 (default `true`). See the portability skill.370- **Prefer read-only ability sets on public endpoints** (WordPress MCP Adapter371 guidance): if the Elementor MCP endpoint is internet-reachable, the remote372 server should expose read/diagnostic abilities rather than destructive ones.373- **Monitor usage** — tool-execution telemetry fires for bridged tools like374 any other tool; MCP Server test/discover events are activity-logged; review375 logs after Elementor write operations.376377## Code map (verified, v1.1.90)378379| Concern | Location |380|---|---|381| Registry (meta keys, allowlist, discovery, status, reference resolution) | `addons/pro/includes/mcp-apps/class-wp-mcp-ai-mcp-app-registry.php` |382| Transport client (handshake, auth types, fallback) | `addons/pro/includes/mcp-apps/class-wp-mcp-ai-mcp-app-client.php` |383| Tool bridge | `addons/pro/includes/mcp-apps/class-wp-mcp-ai-mcp-app-tool-bridge.php` |384| OAuth client | `addons/pro/includes/mcp-apps/class-wp-mcp-ai-mcp-app-oauth-client.php` |385| REST controller | `addons/pro/includes/mcp-apps/class-wp-mcp-ai-rest-mcp-apps-controller.php` |386| Registration + effective-tools seam + import-ref validator | `addons/pro/includes/mcp-apps/mcp-apps-init.php` |387| Remote Sites `mcp_server` type (save/validate/test/discover/mapping) | `addons/pro/includes/class-wp-mcp-ai-pro-remote-site-manager.php` |388| Remote Sites admin UI (type option, MCP fields, toggles) | `addons/pro/includes/admin/class-wp-mcp-ai-pro-remote-sites-admin.php` |389| Assistant metabox (UI, badges, JSON import, Add from Remote Sites, ref rows) | `includes/assistants/metaboxes/class-wp-mcp-ai-metabox-mcp-apps.php` |390| Slash command | `addons/pro/includes/slash-commands/commands/class-wp-mcp-ai-pro-slash-command-mcp-app.php` |391| Folder contract | `addons/pro/includes/mcp-apps/README.md` |392393Key constants: `META_KEY = '_wp_mcp_ai_mcp_apps'`,394`STATUS_META_KEY = '_wp_mcp_ai_mcp_app_status'`, `MAX_APPS_PER_ASSISTANT = 10`,395`CACHE_TTL = 300`, `FAILURE_CACHE_TTL = 60`,396`PROTOCOL_VERSION = '2026-07-28'`, `MAX_RESPONSE_SIZE` = 2 MB.397398## Cross-references399400- `design-elementor-template-kits` — designing/building/importing Elementor401 page content once connected (kits vs live MCP editing are different tracks;402 MCP Apps give the agent live editing tools, kits give offline import).403- `design-ai-assistant-admin` — assistant-level configuration this skill404 plugs into (meta keys, capability gates).405- `mcp-ai-wpoos-assistant-portability` — export/import of assistants carrying406 MCP App configs (token caveat above).407- `mcp-ai-wpoos-plugin` — JSON-RPC over HTTP mechanics shared with the MCP408 bridge.409- `design-vault` — store the application passwords/tokens.410- `wp-security-deep` — SSRF review of the URL guard before touching it.411- `wp-security-secrets` — auditing token storage/handling.412413## What this skill does NOT cover414415- Running the NV oOS plugin as an MCP *server* for other clients — that is the416 inverse direction; see `addons/pro/includes/mcp-servers/`.417- Authoring Elementor template kits or fixing kit imports —418 `design-elementor-template-kits`.419- Writing Elementor abilities on the remote site (wp_register_ability /420 MCP Adapter development) — WordPress developer docs.421- The general chat UI / Elementor widget embeds of NV oOS — plugin chat docs.422423## References424425- Elementor MCP setup/revoke: https://elementor.com/help/how-to-connect-elementor-to-an-ai-tool-using-mcp/426- WordPress MCP Adapter + best practices: https://developer.wordpress.org/news/2026/02/from-abilities-to-ai-agents-introducing-the-wordpress-mcp-adapter/427- MCP Apps extension (SEP-1865): https://modelcontextprotocol.io/extensions/apps/overview428- Folder contract: `addons/pro/includes/mcp-apps/README.md`429- Tests: `tests/mcp-apps/test-mcp-app-chat-exposure.php`,430 `tests/mcp-apps/test-mcp-app-client-connection-enhancements.php`,431 `addons/pro/tests/test-pro-slash-command-mcp-app.php`