|
/ Documentation /UAE AI Tools/ UAE AI Tools: Connect AI to Your Elementor Site

UAE AI Tools: Connect AI to Your Elementor Site

The UAE AI Tools feature lets you connect AI clients like Claude, Cursor, and VS Code directly to your WordPress site, or use Elementor’s built-in Angie assistant, to build and manage headers, footers, templates, pages, and widgets using natural language.

There are two independent ways to use UAE’s AI tools:

External AI Clients (MCP)In-Editor (Angie)
Where it runsYour AI app (Claude, Cursor, VS Code…)Inside the Elementor editor, in the browser
TransportModel Context Protocol over HTTPElementor’s Angie assistant
NeedsApplication Password + client configAngie plugin active + a single toggle
Best forPower users, agencies, automationEveryday editing while designing a page

Both paths use the same underlying abilities and the same WordPress capability checks. You can enable one or both independently.

Requirements

RequirementDetails
WordPress7.0+ recommended.
UAE PluginUltimate Addons for Elementor (2.9.0+) and/or Ultimate Addons for Elementor Pro (1.46.0+)
Elementor3.0 or later
For MCP clientsNode.js 18+ installed on your computer; Application Passwords enabled (WordPress default); HTTPS site for production
For AngieThe Angie plugin installed and active

Step 1: Enable AI Tools

Before connecting any AI client, turn on the feature in your WordPress admin.

  1. Go to UAE → Settings → AI Tools.
  2. Turn on Enable AI Tools (off by default).
  3. If you want the AI to create or modify content, also turn on Allow Modifications. Without this, the AI is read-only.
  4. Optional: turn on Standalone UAE Server to create a dedicated endpoint that exposes only UAE tools.
image

Default is off. Until you enable AI Tools, nothing is exposed and no abilities are registered. Existing sites are unaffected by the update.

Method 1: AI Setup Prompt (Easiest)

Once AI Tools is enabled, UAE generates a ready-made setup prompt for you.

  1. On the UAE → Settings → AI Tools page, click the sparkle (✨) button to copy the setup prompt to your clipboard.
  2. Open your AI client (Claude, Cursor, VS Code, etc.) and paste the prompt into the chat.
  3. The AI will guide you through the rest of setup by asking:
    • Which AI client you use and your operating system
    • Your WordPress Application Password (see how to create one)
    • To run which npx && node –version && echo $PATH and paste the output
  4. The AI writes the correct config file for your setup, using your actual paths and credentials.
  5. The AI confirms everything is in place and your connection is working.
sparkle button mcp

This method works for all supported clients. The AI detects your OS and client automatically and places the config in the right location, no manual file editing required.

Method 2: Manual Setup

If you prefer to configure the connection yourself, see the Integration Setup guide for step-by-step instructions for each supported client: Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Windsurf, and Codex.

Use AI Inside Elementor (Angie)

Angie is Elementor’s in-editor AI assistant. When the Angie plugin is active, UAE makes its abilities available to Angie so you can build and edit pages directly while designing, no Application Password or MCP config required.

See: Use UAE AI Tools with Angie

MCP and Angie are independent. You can use Angie without configuring any external MCP client, and vice versa.

Settings Reference

All options live on UAE → Settings → AI Tools.

SettingDefaultWhat it does
Enable AI ToolsOffMaster switch. When off, no abilities are registered and nothing is exposed.
Allow ModificationsOffWhen off, AI can only read your site. When on, AI can create, edit, and delete.
Standalone UAE ServerOffCreates a dedicated endpoint at /wp-json/uae/mcp exposing only UAE tools. When off, UAE tools appear on the default WordPress MCP endpoint.
Angie IntegrationOffExposes UAE abilities to Elementor’s in-editor Angie assistant.
Ability TogglesAll onPer-ability switches to hide individual tools you don’t want AI to access.

Recommendation: For your first rollout, keep Allow Modifications off until you have confirmed the AI behaves as expected. Then enable writes deliberately.

Available AI Tools

Read-Only Tools

(Available whenever AI Tools is enabled)

AreaExamples
Plugin infoVersion, health status, active hooks
TemplatesList and read headers, footers, and blocks; which template renders on a given URL
PagesList WordPress pages
WidgetsList all widgets and their status; widget usage across templates
ExtensionsScroll to Top and Reading Progress Bar status
Display rulesAvailable display-rule locations
ThemeTheme detection, compatibility, and rendering method
Settings & designRead plugin settings and Elementor design tokens (colors, fonts, spacing)
BuilderRead page/template structure, widget schemas, and custom CSS

Write Tools

(Require Allow Modifications to be enabled)

AreaExamples
TemplatesCreate, update, delete, restore, and duplicate headers/footers/blocks
PagesCreate, delete, restore, change status, and update metadata
WidgetsActivate, deactivate, bulk-toggle, and deactivate unused widgets
Extensions & rulesToggle extensions; update display rules
SettingsUpdate plugin configuration (administrator only)
BuilderBuild a full layout, insert/update/remove/move elements, add sections and columns, regenerate CSS
Builder: UndoRevert the most recent AI builder change on a post
MaintenanceClear Elementor and plugin caches

Security Best Practices

  1. Use a dedicated WordPress user for AI access with only the roles and capabilities it needs.
  2. Use Application Passwords they can be revoked individually without changing your main password.
  3. Start read-only. Enable Allow Modifications only when you need the AI to make changes.
  4. Disable abilities you don’t need using the Ability Toggles on the settings page.
  5. Always use HTTPS on production sites.
  6. Revoke Application Passwords when a client no longer needs access (Users → Profile).

Having trouble? See the UAE AI Tools Troubleshooting guide or contact our support team.

Was this doc helpful?
What went wrong?

We don't respond to the article feedback, we use it to improve our support content.

Scroll to Top