WPVibe vs Fabrement
WPVibe and Fabrement both connect an AI agent to WordPress over MCP, so they get compared. They solve different problems, and both are good at their own. This page says plainly where WPVibe is the better choice. It compares the WPVibe plugin by SeedProd (wpvibe.ai), not the open-source project of the same name on GitHub.
The short answer
WPVibe connects an AI assistant to the WordPress site you already have, whatever it was built with: Elementor, Divi, Bricks, Gutenberg, WooCommerce. It is the better choice for operating an existing site.
Fabrement builds the whole site: native Gutenberg blocks written as real code from a Figma frame, a screenshot or a sentence, then the headers, footers and templates around them, forms, Yoast SEO and WPML translations, all on one design system, and then manages it. It is the better choice when you are building or rebuilding and want a site without a page builder underneath.
Key takeaways
- WPVibe works with the stack you have, including page builders and WooCommerce. Fabrement does not touch WooCommerce and does not edit page-builder layouts.
- Fabrement builds the whole site as code: blocks, headers, footers, templates, forms, SEO and translations. WPVibe mainly works with the blocks and builders a site already has; custom code is possible through its theme file editor, but it is not what the product is built around.
- WPVibe has an approval panel and an append-only log for destructive actions. Fabrement separates publishing from saving but has no approval panel or audit log yet.
- WPVibe meters actions per day: 100 a day free, paid plans from $99 a year. Fabrement charges nothing per action over MCP; you pay only for your own AI client.
- Requirements differ: WPVibe runs from WordPress 6.0 and PHP 7.4; Fabrement needs WordPress 6.9 and PHP 8.0.
Side by side
How to read the table: Yes is a stated feature. Partly, not the main workflow means it is possible, but not what the product is built for. Not listed means it is not in the product’s own description, which is not the same as impossible.
| WPVibe | Fabrement | |
|---|---|---|
| What it is | An MCP server that lets an AI operate your WordPress site | An AI agent that builds and runs the whole site: blocks, headers, footers, templates, forms, SEO and translations |
| Made by | SeedProd (Awesome Motive) | 7Fridays |
| Adoption | 30,000+ installs on wordpress.org, rated 5/5 | Early; wordpress.org listing in review |
| Builds new blocks as code | Partly, not the main workflow: the agent can write block code into a sandboxed draft theme, with a PHP syntax check before saving | Yes, it is the core of the product: PHP, CSS and JS per block with editor fields, checked and versioned before it is saved |
| From Figma | Partly, not the main workflow: no Figma import of its own, but an AI client also connected to Figma can use the design as a reference and build the page through WPVibe | Yes, built in: the plugin reads the Figma frame itself and turns it into blocks with real flex and grid layout, not an approximation from a screenshot |
| Page builders | Elementor, Bricks, Breakdance, Beaver Builder, Divi, SeedProd, Gutenberg | Native Gutenberg only, no builder runtime |
| Design system | Partly, not the main workflow: it can edit a theme’s theme.json, WordPress’s global styles, but has no design system of its own that new blocks are built from | Colour roles, type scale and button styles used by every block |
| Whole theme | Can scaffold a classic theme in a draft theme | Headers, footers and templates, applied to pages, post types and archive listings |
| Custom post types | Supported, including ACF fields | Created with their own single pages and listing pages, plus their own custom fields, shown on the single page and reused across the site |
| Forms | Yes: WPForms (a sister product), through its Abilities API integration; styling goes through the theme’s CSS | Contact Form 7 and WPForms, styled to match the site |
| SEO | Yes: All in One SEO and Rank Math, through their Abilities API integrations; Yoast is not in its list | Yoast titles, descriptions and schema, per page and per archive |
| WooCommerce | Yes: products, prices, stock | No |
| Multilingual | Partly, not the main workflow: it works on WPML sites (version 1.16.1 fixed reading translated pages), but has no translation workflow of its own | WPML: pages in another language, translated menus, headers, footers, slugs and SEO fields, plus a language switcher |
| Plugin and core updates | Yes, with rollback | No, updates are still done in wp-admin |
| Theme file editing | Yes, in a sandboxed draft theme | No file access beyond the blocks it writes |
| Approval before destructive actions | Yes, with dry-run previews | Publishing is a separate step; no approval panel yet |
| Audit log | Append-only approval log | Not yet |
| AI clients | Claude (desktop, web, Code), ChatGPT, Cursor, Windsurf, OpenCode | ChatGPT, Claude (web, desktop and Claude Code) and Codex with OAuth; Cursor and any HTTP MCP client; plus a chat inside wp-admin |
| Connection | Through the WPVibe service to your site | The agent connects to the site’s own MCP endpoint; block code is checked by the Fabrement service |
| Price | Plugin free; 100 actions a day free, paid plans $99 to $899 a year | Plugin free; no per-action charge over MCP; the wp-admin chat uses your own AI key after a starter credit |
| Requirements | WordPress 6.0+, PHP 7.4+ | WordPress 6.9+, PHP 8.0+ |
Where WPVibe is the better choice
- Your site is already built on Elementor, Divi or another builder, and you want AI to operate it rather than rebuild it.
- You run WooCommerce and want products, prices and stock handled from a chat.
- You want the agent to update plugins and core, with rollback.
- You want an approval step and a permanent log before anything destructive happens.
- You are on older WordPress or PHP versions.
Where Fabrement is the better choice
- You are building or rebuilding a site and want native Gutenberg without a page builder underneath.
- You work from Figma and want frames turned into real, editable blocks rather than approximated.
- You want one design system every section follows, so new sections match the site automatically.
- You need custom post types with real listing pages, or a multilingual site on WPML.
- You want forms, SEO and translations handled in the same conversation as the design, not by a separate tool each.
- You care about performance: each page loads only the CSS and JavaScript of the blocks it uses.
Can you use both?
Technically yes: they are different plugins doing different jobs. In practice, pick one agent connection per site, so there is one place to look when something changed. More on how Fabrement works is on how Fabrement builds a WordPress site.
Frequently asked questions
Is Fabrement a WPVibe alternative?
For building and managing a native Gutenberg site, yes. For operating a site built on Elementor, or for running WooCommerce, WPVibe covers ground Fabrement does not.
Which works with Elementor, WPVibe or Fabrement?
WPVibe. Fabrement builds native Gutenberg blocks and does not edit page-builder layouts.
Which is cheaper, WPVibe or Fabrement?
Both plugins are free. WPVibe meters WordPress actions per day on its service, from 100 a day on the free plan. Fabrement does not charge per action over MCP; you pay only for your own AI client.
Which is safer, WPVibe or Fabrement?
WPVibe has an approval panel with dry-run previews and an audit log today. Fabrement gives the agent no file access beyond the blocks it writes, a read-only database operation and publishing as a separate step, but has no approval panel yet.
Sources
WPVibe facts were checked on 23 September 2026 against its wordpress.org listing (version 1.17.5) its product site and its pricing page. Fabrement facts come from our own AGENTS.md (plugin version 1.4.0, checked 30 September 2026). If anything here is out of date, tell us and we will correct it.