Describe the section you want and Claude builds it in Elementor, on your real site, using the widgets you already have installed. What makes that possible is Premium Addons for Elementor, which exposes your pages, widgets and design settings to Claude as a set of tools it is allowed to call. Nothing about your site leaves WordPress until you approve the connection in your own browser, and no password is ever pasted into Claude.
Claude is also the quickest of the AI clients to set up, because Premium Addons can hand it a connector that is already filled in. Most of what follows happens on the WordPress side; the Claude side is a few clicks.
New to the idea? What MCP is and how Premium Addons uses it explains the machinery, and the Premium Addons MCP and AI Abilities page shows finished builds next to the prompts that produced them.
What You Need Before You Start
- WordPress 7.0 or higher. The Abilities API arrived in 6.9 and the piece that publishes those abilities to AI clients arrived in 7.0.
- Premium Addons for Elementor 4.11.91 or higher, which is the release that added Claude on the web as a supported client.
- Premium Addons PRO to build with anything beyond free Elementor and Premium Addons widgets, including Elementor Pro widgets and widgets from other Elementor 3rd party plugins.
- Elementor installed and active.
- An HTTPS site with a permalink structure other than Plain.
- A site the internet can reach. Claude connects from Anthropic’s servers, not from your computer, so a local install or a site behind HTTP authentication cannot be connected.
- A Claude account. Custom connectors work on every plan, and free plans can add one. On Team and Enterprise an administrator may have to allow custom connectors first.
- A WordPress administrator login in the same browser you approve the connection in.
Step 1: Turn On AI Abilities
AI Abilities ships switched off. Go to Premium Addons → MCP Config & AI Abilities in your WordPress dashboard, find the Enable AI Abilities card at the top of the tab, and turn the toggle on. The change saves by itself.
The tab then holds two sections. MCP Server is where you connect Claude. Manage AI Abilities is where you choose which abilities it is allowed to use.
Step 2: Switch the Connection Method to OAuth
Open the MCP Server section. At the top you will find Connection method with two cards. Select OAuth, the one marked Recommended.
⚠️ Info: Password protection and security plugins can block this connection. Claude reaches your site from Anthropic’s servers, so both the sign-in page at /pa-oauth/ and the MCP endpoint under /wp-json/ have to be reachable from outside. If your site sits behind a password, a firewall, or a plugin that restricts the REST API, allow those two paths or switch the protection off while you connect.
Selecting the card is what switches OAuth on, so there is no separate save. If the card is greyed out it prints the reason underneath, and the reason is almost always one of two things: your site is not on HTTPS, or your permalinks are set to Plain.
Now pick Claude (claude.ai) from the row of client tabs.
One thing to know before you switch windows. Your site only accepts a new AI client for thirty minutes after you load this tab. That window exists because a client has no WordPress credentials at the point it asks to be registered, so the door cannot be left open permanently. Finish the Claude side inside that half hour. If you take longer, reload the tab and start again.
Step 3: Add the Connector to Claude
Select Add it automatically. Claude opens its Customize page with the Add custom connector dialog already filled in, which saves copying two values across.
Claude will warn you that the connector was suggested by an external link and ask you to check the name and URL before adding it. That warning is doing its job. The link came from your own dashboard, and the URL should be your own domain.
Select Continue. On the second step, leave the settings alone. Claude probes your site and marks what it found as Detected: sign-in always required, and no client ID needed because your site registers one automatically. Then select Add.
Adding It by Hand Instead
If you would rather not use the button, the manual path lands in the same dialog. In Claude, open Customize in the left sidebar, choose the Connectors tab, and select Add in the top right corner. Connectors used to live under Settings; that page now only points you to Customize. Give the connector the name shown in the Premium Addons panel, paste the server URL from the same panel, select Continue, and leave the second step at what Claude detected before selecting Add.
Step 4: Approve the Connection
Adding the connector does not finish it. Claude opens the connector’s own page, which says you are not connected to it yet. Select Connect.
Your browser opens on an approval screen served by your own site. It names the client asking for access, names your site, and tells you which WordPress account the connection will act as. The client name comes from the client itself, so read it as a label rather than proof of identity.
Select Approve. That is the connection made, and it stays made. Only ever approve a screen like this when you started the connection yourself.
Claude then returns to the connector page, now listing everything it picked up from your site, split into read-only tools and tools that write or delete, with a permission control on each group.
This split is worth a moment. Read-only tools inspect your site and change nothing. The write group is the one that edits pages, so if you want to be asked before anything is touched, set that group to ask rather than allow.
Build Your First Elementor Page With Claude
Start a new chat, mention the connector, and ask for something small:
“Build a new Elementor page called Claude Test Page with a heading, a short paragraph and a button, using Premium Addons widgets where they fit.”
Claude reads your site before it writes anything: your theme, your colours, your fonts, and which widgets you have available. Then it builds, and tells you what it did.
Check the result in WordPress rather than in the chat. Open Pages in your dashboard and the draft is there, marked as an Elementor page and ready to open in the editor.
That last part matters more than it sounds. Claude writes a summary of what it did, and a summary is not evidence. WordPress is the only place that knows what actually happened.
Usage Examples
Connecting is the easy half. Working out what to ask for takes longer, so the Premium Addons MCP and AI Abilities page collects real use cases, each one showing the exact prompt behind it and a video of what came out.
The examples run from building a homepage hero slider and a pricing table with monthly and yearly billing, to applying a scroll animation or display conditions to a single widget, redesigning an existing page, and rebuilding a Figma design as editable Elementor. Every one has a Copy Prompt button, so the fastest way to start is to take the closest example, change the details to match your site, and send it.
Get Better Results With the Agent Skill
The connection gives Claude the ability to build. The Premium Addons Agent Skill gives it the judgement to build well: how to read your site first, which widget suits which job, when to stop and ask, and what never to touch without permission. It is free, it installs in a couple of minutes, and it is the single biggest difference in the quality of what comes out.
If the Connection Does Not Work
- Claude reports a registration error. The thirty minute window closed. Reload the MCP Config & AI Abilities tab and add the connector again.
- The OAuth card is greyed out. It names the reason underneath. Switch your site to HTTPS, or change your permalinks to anything other than Plain.
- The approval screen never appears. You are not signed in to WordPress as an administrator in that browser. Log in and select Connect again.
- Claude cannot reach your site at all. It is not reachable from the public internet. Local installs and sites behind HTTP authentication cannot be connected.
- The tools worked and then stopped mid build. Check whether you have hit your Claude usage limit first, because that is what it usually is, and the connection is fine.
Disconnecting Claude
There are two ways to end the connection, and they are not the same size.
In Claude, open Customize, choose Connectors, then Yours, open the connector and select Disconnect. That ends this one connection and leaves anything else you have connected alone. The connector stays in your list so you can connect it again later; the three-dot menu next to Disconnect has Remove if you want it gone.
On your site, go to Premium Addons → MCP Config & AI Abilities, open the MCP Server section, and choose Manage or revoke access, then Disconnect all clients.
Read that second button literally. It revokes every access token your site has issued, to every client, not only to Claude. Anything you had connected has to be approved in the browser again before it can come back.
Come & Join the Community
Feel free to join our Facebook group and subscribe to our YouTube channel to keep up with our newest features, improvements, and helpful video tutorials.
