Elementor MCP troubleshooting
This page gathers every problem the three setup guides cover, one heading per message you may actually see on screen. Find the one that matches your situation, read the cause, follow the steps — and open the full guide if you want the whole context around it.
Once a license has been validated, the plugin caches the result for 12 hours and re-checks it on its own. If our license server is unreachable at that moment, a 24-hour grace period keeps the site running, so a short outage on our side never locks you out mid-project.
License and activation
A key that isn't Active stops every tool, so start there.
“Invalid or expired license”
Cause: The license server did not recognise the key sent by your site.
Fix:
- Open Elementor MCP → License in your WordPress admin and read the status shown there.
- Copy the key again from your purchase email — the entire string, with no leading or trailing space.
- Paste it into the license field and click Activate / Verify. The status turns Active once it is confirmed.
- If it still refuses, email youness@fatine.fr with the key and the site address.
“Already activated on another site”
Cause: The key bound itself to the first site that activated it and cannot be moved.
Fix:
- Check which site you are activating on — a staging copy and a production site count as two different sites.
- Activate the key on the site you actually meant to use.
- If the key is stuck on a site you no longer own or use, email youness@fatine.fr.
You no longer have your license key
Cause: Nothing is broken — the key is simply no longer in front of you.
Fix:
- Use the Find my key link on the Elementor MCP → License screen.
- Or search your inbox for the purchase email, which contains the key and the plugin download link.
Connecting your AI assistant
Most connection problems come from the config file, not the plugin.
The server doesn't appear in Claude Desktop
Cause: The JSON wasn't read: wrong file, invalid JSON, or the app wasn't restarted.
Fix:
- Check that the block sits inside mcpServers in claude_desktop_config.json.
- Check that the file is still valid JSON — one extra comma is enough to break it.
- Quit the app completely and reopen it: the server list is read at startup.
- Compare the url and the Authorization header against the plugin's MCP configuration screen, which stays the reference.
The assistant connects but every tool is refused
Cause: Your license isn't active, so the connection and each tool refuse separately.
Fix:
- Open Elementor MCP → License and check the status.
- Activate or re-verify the key until the status reads Active.
- Ask your assistant to run get-site-info again — no restart is needed once the license is valid.
The ✦ Elementor MCP panel stays locked 🔒 in the editor
Cause: Same cause as above: the panel unlocks only when the license turns Active.
Fix:
- Activate your license from Elementor MCP → License.
- Reload the Elementor editor: the panel then shows your endpoint and the configuration to copy.
You lost the Application Password
Cause: It is displayed only once, on the plugin's MCP configuration screen.
Fix:
- Go to Users → MCP_ELEMENTOR → Application Passwords in WordPress and generate a new one.
- Rebuild the Authorization header with that new value.
- Paste the updated configuration into your assistant and restart it.
Your site's address changed
Cause: The url in your assistant's configuration still contains the old domain.
Fix:
- Open the plugin's MCP configuration screen to read the current endpoint.
- Update the url in your assistant's configuration, then restart it.
Generating and writing sections
A write can be refused, and the plugin says so rather than guessing.
The assistant reports a failed write
Cause: Writes are normalised and audited on our server first, and there is no local fallback.
Fix:
- Check the license status in Elementor MCP → License — read-only tools may still answer from the 12-hour validation cache while writes are already refused.
- Check that the site is the one your key is bound to.
- Retry the same request once your license reads Active; a refused write leaves your page untouched.
Nothing appears in the Elementor editor
Cause: The tree is written into the document itself, not into your open editor tab.
Fix:
- Reload the Elementor editor for that page.
- Check that your assistant worked on the page you meant — ask it which document it wrote to.
The section looks close to your mockup without matching it
Cause: The fidelity sessions ended before every check on every section had passed.
Fix:
- Ask for one more fidelity session in the same conversation.
- The assistant re-inventories the sections and restarts the comparison, check by check, until nothing differs.
The audit reports SEO problems
Cause: The structural audit found a heading, alt attribute or JSON-LD issue in what was written.
Fix:
- Ask for the fix in the same conversation, quoting what the audit reported.
- The audit comes back with every write, so you can confirm straight away that the problem is gone.