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 MCP Integration.

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

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

Requirements

Part 1: Connect an External AI Client (MCP)

Step 1: Enable AI Tools

1. In your WordPress admin, go to UAE → Settings → AI Tools.
2. Turn on Enable AI Tools (this is 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.

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

Step 2: Create an Application Password

MCP uses WordPress Application Passwords to authenticate securely. You don’t share your main WordPress password.

1. Go to Users → Profile and scroll to the Application Passwords section.
2. Enter a name (e.g. Claude Desktop) and click Add New Application Password.
3. Copy the generated password immediately. WordPress shows it only once.

Tip: Create a separate Application Password for each AI client so you can revoke them individually without affecting other clients.

Step 3: Get Your Connection Details

On the UAE → Settings → AI Tools page, you will find your server URL and a ready-made config block.

The dedicated UAE endpoint is:

https://yoursite.com/wp-json/uae/mcp

If Standalone UAE Server is turned off, UAE abilities are served from the default WordPress MCP endpoint instead:

https://yoursite.com/wp-json/mcp/mcp-adapter-default-server

Step 4: Configure Your AI Client

Claude Desktop

Claude Desktop connects through a small Node.js bridge. Make sure Node.js 18+ is installed (node –version to check).

Config file location:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add the following to the mcpServers object in that file:

{ 

    "mcpServers": {

      "uae": {

        "command": "npx",

        "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],

        "env": {

          "WP_API_URL": "https://yoursite.com/wp-json/uae/mcp",

          "WP_API_USERNAME": "your-username",

          "WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"

        }

      }

    }

}

Save the file and restart Claude Desktop.

No-Node alternative: In Claude Desktop, go to Settings → Connectors → Add custom connector and paste your server URL directly. No Node.js required.

Claude Code

Create .mcp.json in your project root (or ~/.claude/.mcp.json for global use):

{ 

    "mcpServers": {

      "uae": {

        "type": "http",

        "url": "https://yoursite.com/wp-json/uae/mcp",

        "headers": { "Authorization": "Basic BASE64_ENCODED_CREDENTIALS" }

      }

    }

}

Generate your Base64 credentials by running:

echo -n “username:application-password” | base64

Cursor

Create .cursor/mcp.json in your project root, or go to Cursor Settings → Tools and MCP → Add Custom MCP:

{ 

    "mcpServers": {

      "uae": {

        "url": "https://yoursite.com/wp-json/uae/mcp",

        "headers": { "Authorization": "Basic BASE64_ENCODED_CREDENTIALS" }

      }

    }

}

VS Code (GitHub Copilot)

Create .vscode/mcp.json in your project root.

Note: VS Code uses a “servers” key instead of “mcpServers”.

{ 

    "servers": {

      "uae": {

        "type": "http",

        "url": "https://yoursite.com/wp-json/uae/mcp",

        "headers": { "Authorization": "Basic BASE64_ENCODED_CREDENTIALS" }

      }

    }

}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{ 

    "mcpServers": {

      "uae": {

        "serverUrl": "https://yoursite.com/wp-json/uae/mcp",

        "headers": { "Authorization": "Basic BASE64_ENCODED_CREDENTIALS" }

      }

    }

}

Codex (OpenAI)

Add to ~/.codex/config.toml:

[mcp_servers.uae]

url = "https://yoursite.com/wp-json/uae/mcp"

[mcp_servers.uae.http_headers]

"Authorization" = "Basic BASE64_ENCODED_CREDENTIALS"

Using the AI Setup Prompt (Easiest Method)

Not sure how to edit config files? Use the  sparkle button in the UAE MCP panel to copy a ready-made prompt, then paste it directly into your AI client. The AI will:

1. Ask which client you use and your OS
2. Ask for your Application Password
3. Locate the correct config file for your setup
4. Ask you to run which npx && node --version && echo $PATH and paste the output
5. Write the correct config with your actual paths
6. Confirm everything was added correctly

Part 2: 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, with no Application Password or external client configuration required.

How to enable:

1. Install and activate the Angie plugin.
2. Go to UAE → Settings → AI Tools and turn on Enable AI Tools.
3. Turn on Angie Integration.
4. Open any page or template in the Elementor editor. UAE’s build and edit tools will now be available inside Angie.

MCP and Angie are independent. You can use Angie without configuring any external MCP client, and vice versa. Enabling one does not require the other.

Settings Reference

All options live on UAE → Settings → AI Tools.

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)

Write Tools

(Require Allow Modifications to be enabled)

UAE Pro

Everything above applies to both UAE Lite and UAE Pro. When UAE Pro is active, the same AI Tools settings page gains extra abilities.

Operating modes:

• Dual mode (Lite + Pro active): Lite hosts the registry and Pro adds its abilities into it. One combined tool set is exposed on the UAE endpoint.
• Standalone Pro (Pro active, Lite inactive): Pro runs the full tool set on its own.

Pro-only abilities:

Recovery & Safety

AI-driven changes are recoverable through several layers:

One-step undo: Before every builder change, UAE snapshots the previous content. Just ask the AI to “undo that” and it will restore the snapshot.

Elementor revision history: Content edits also create Elementor revisions, so you can roll back to any earlier version from the editor’s History panel.

Trash, not delete: Deleting a page or template moves it to Trash. Dedicated Restore abilities let the AI bring it back if needed.

Object-level permissions: The AI can only edit content that the connected WordPress user is allowed to edit. It cannot access or modify other users’ content.

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).

Troubleshooting

Settings page says “requires WordPress 6.9+” or abilities list is empty

The Abilities API is not available. Upgrade to WordPress 7.0+, or install the MCP Adapter plugin on 6.9. Clear any page or object cache and reload.

0 abilities when both Lite and Pro are active

Update both UAE Lite and UAE Pro to the latest version. Earlier builds could fail to register abilities in certain plugin load orders when both were active. Reload the AI Tools page and flush the Elementor/plugin cache.

AI client shows no tools

1. Confirm Node.js 18+ is installed (run node -v).
2. Check the config file path for your operating system.
3. Verify the Application Password is correct (include the spaces, e.g. xxxx xxxx xxxx xxxx xxxx xxxx).
4. Make sure a security plugin is not blocking Application Password authentication.
5. Restart the AI client after editing the config.

“ReadableStream is not defined”

Your Node.js version is too old. Upgrade to Node 18 or later: nvm install 20 && nvm use 20.

Tools appear but return permission errors

The connected WordPress user doesn’t have the required capability for that operation. See Capabilities below and grant the appropriate role, or connect as a higher-privileged user.

Write tools are missing

Turn on Allow Modifications on the AI Tools settings page. Write tools are hidden until this is enabled.

Capabilities & Permissions

Every ability checks WordPress capabilities at execution time. The AI client acts as the authenticated WordPress user.

FAQ

Need help? Contact our support team or explore the UAE Documentation.