About
Elementor MCP is built by one person, not an anonymous company. Here's who built it, why, what you can check for yourself, and how to reach me.
Who built this plugin
I'm Youness Fatine, an independent developer based in Lyon, France. I've been building WordPress sites for clients for several years, mostly with Elementor.
Elementor MCP is a solo project: no team, no investors, no outsourced support desk — and when you email me, I'm the one who answers.
Two names, one person
Two names come up on this site, so let me clear them up. Elementor MCP (mcp-elementor.com) is the product you buy here. youness@fatine.fr is my own address, and it is where the product's support runs — you write to me directly, not to a shared inbox.
The same person is behind both: me. The legal publisher of this site and of the plugin is Youness Fatine, a registered French sole trader — SIRET, trade register entry and registered address are published in full on the legal notice page, under the same name as in the plugin's composer.json.
Why I built it
Delivering Elementor sites for clients, I kept losing time cleaning up what an AI assistant produces when you ask it for a page section: hardcoded text, div soup with no semantic structure, no Schema.org markup, nothing that respects the site's design system.
Elementor MCP connects your AI assistant (Claude, ChatGPT, Cursor, or any other Model Context Protocol client) directly to the Elementor editor on your WordPress sites. The AI generates sections that match your mockup, but built with Elementor's Atomic Design components, a clean semantic DOM, and automatic Schema.org markup — not raw text dumped into divs.
The goal isn't to replace the freelancer's work, but to save the time lost fixing what a general-purpose AI produces without knowing Elementor. The license is a one-time €9.99 payment for lifetime use, no subscription, tied to a single site.
What's actually inside the plugin
The plugin exposes 38 MCP tools to your assistant: reading the site's design system (colours, fonts, spacing, breakpoints), creating and editing Elementor trees, declaring custom post types and ACF fields, Schema.org markup, and SEO and performance audits. The plugin itself never calls an AI provider — your assistant does the generating, on your own subscription.
Two safety nets do most of the invisible work. On every tree write, a structural SEO audit checks the output — one h1, no skipped heading levels, landmarks, image alt text, div soup, valid JSON-LD — and hands anything off back to the assistant. And a fidelity loop compares every section against your mockup on five checks: content, decorative media, styles and tokens, layout and spacing, responsive and states.
Installing it, connecting your assistant and running the first generation are written out step by step in the documentation, limitations included.
What you can check before you buy
No testimonials, no customer counter, no star rating — I have nothing honest to show there yet. What you can check is this:
- Who publishes it: name, legal status, SIRET, trade register entry and registered address, in full, plus the site's host. Legal notice
- Who wrote the plugin: the project's composer.json names me as the author.
- What the plugin does: the documentation spells out each step, and each limitation, before you pay anything. Documentation
- What changes: the changelog lists what each version contains. Changelog
Get in touch
A question before buying, a bug after installing, an idea? Email me directly — I answer every message myself, no automated ticket system.
If you hit a case the plugin handles badly, send me the context (WordPress and Elementor versions, what you asked your assistant): that's how fixes reach the next release.