WordPress Studio vs Fabrement
WordPress Studio and Fabrement both let an AI agent like ChatGPT, Claude, Codex or Cursor build a WordPress site, so they get compared. They work in different places. Studio is a free desktop app for local WordPress sites, with an MCP server and an AI assistant of its own. Fabrement is a plugin that runs on the site itself, on any host. This page says plainly where Studio is the better choice.
The short answer
WordPress Studio gives the agent a WordPress on your computer: it can create sites, write theme and plugin files directly, run WP-CLI and take screenshots of its own work. It is the better choice for local development, especially if you host on WordPress.com or Pressable, where Studio can sync your work.
Fabrement works on the site itself, live or staging, wherever it is hosted. The agent builds through fixed operations: new blocks written as code from Figma, a screenshot or a sentence, all on one design system, then templates, pages, menus, forms, Yoast SEO and WPML translations. Block code is checked before it is saved. It is the better choice when the site already exists, or when the people running it after launch are not developers.
Key takeaways
- Studio is local first. Its MCP server works with local Studio sites. Its AI assistant, Studio Code, can also work on WordPress.com and Jetpack-connected sites.
- Fabrement works on any host. It needs WordPress 6.9, PHP 8.0 and HTTPS, and there is no deploy step because the work happens on the site.
- Studio gives the agent more freedom: files, WP-CLI and screenshots. Fabrement gives it guardrails: fixed operations, checked block code and publishing as a separate step.
- Studio has a visual loop built in. Its agent screenshots its own work and iterates. With Fabrement, visual checks depend on your AI client’s browser tools.
- Both start free. Studio is free and open source, and Studio Code is free during its beta within a monthly limit. The Fabrement plugin is free; over MCP the agent runs in the AI client you already pay for.
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.
| WordPress Studio | Fabrement | |
|---|---|---|
| What it is | A desktop app for local WordPress sites, with an MCP server for agents and an AI assistant, Studio Code (beta) | A plugin on the site with an MCP endpoint for agents and a chat inside wp-admin |
| Made by | WordPress.com (Automattic) | 7Fridays |
| Where it works | Local Studio sites; Studio Code also on WordPress.com and Jetpack-connected sites | Any WordPress 6.9+ site with PHP 8.0+ and HTTPS, on any host |
| How the agent builds | Reads and writes files in the site folder and runs WP-CLI | Through fixed operations; no file access beyond the blocks it writes |
| Builds blocks, themes and plugins | Yes: themes, plugins and sites, as files | Blocks, headers, footers and templates, as checked code; not themes or plugins as files |
| Checks before writing | Not listed | Yes: block code is checked before it is saved; publishing is a separate step |
| Visual check | Yes: the agent takes screenshots and iterates | Partly, not the main workflow: preview links for drafts; screenshots depend on your AI client |
| From Figma | Partly, not the main workflow: an agent also connected to Figma’s own MCP server can use the design | Yes, built in: frames become blocks with real flex and grid layout |
| Design system | Partly, not the main workflow: through the theme’s theme.json | Colour roles, type scale and button styles used by every block |
| Forms, SEO, multilingual | Not listed as built-in operations; possible by editing plugins and themes as files | Contact Form 7 and WPForms, Yoast SEO, WPML |
| WP-CLI | Yes | No |
| Getting it live | Sync with WordPress.com paid plans and Pressable; free preview sites (ten, live for seven days); other hosts need your own deployment | No deploy step: the work is already on the site |
| Who runs the site after launch | Partly, not the main workflow: Studio is a development tool | Yes: owners and teams keep changing the site through the agent or the editor |
| AI clients | Claude Desktop, Claude Code, Cursor, Codex, Windsurf, VS Code | ChatGPT, Claude (web, desktop and Claude Code) and Codex with OAuth; Cursor and any HTTP MCP client; plus the wp-admin chat |
| Price | Free and open source; Studio Code free in beta within a monthly limit, needs a WordPress.com account with a payment method | Plugin free; no per-action charge over MCP; the wp-admin chat uses your own AI key after a starter credit |
| Platforms | macOS, Windows, Linux | Runs inside WordPress, so any system with a browser |
Where WordPress Studio is the better choice
- You are a developer and want the agent working on your computer, away from any live site.
- You want the agent to write themes and plugins as files, with WP-CLI and Git.
- You want an agent that screenshots its own work and fixes what it sees.
- You host on WordPress.com or Pressable, where Studio can sync your work.
- You want to try ideas on throwaway sites and share free preview links.
Where Fabrement is the better choice
- The site already exists, on any host, and you want the agent to build on it where it is.
- The people running the site after launch are owners or marketers, not developers.
- You work from Figma and want frames turned into real, editable Gutenberg blocks.
- You want every new section built on one design system, and the code checked before it is saved.
- You need forms, Yoast SEO or WPML handled in the same conversation as the design.
Can you use both?
They fit different stages. Studio suits development on your own computer; Fabrement suits building on and running the site where it lives. We have not tested Fabrement inside a Studio site yet, so we do not claim it. More on how Fabrement works is on how Fabrement builds a WordPress site, and on what an agent can do once connected in building and managing WordPress with MCP.
Frequently asked questions
Is Fabrement a WordPress Studio alternative?
For building on a live site on any host, yes. For local development with files, WP-CLI and screenshots, Studio covers ground Fabrement does not.
Does WordPress Studio work on my live site?
Its MCP server works with local Studio sites. Studio Code, its AI assistant, can also work on WordPress.com and Jetpack-connected sites. For other hosts you deploy the work yourself.
Which is safer for a live site, WordPress Studio or Fabrement?
Studio keeps mistakes on your computer until you sync them. Fabrement works on the site, but through fixed operations: block code is checked before it is saved, the agent has no file access beyond the blocks it writes, and publishing is a separate step.
Which is cheaper, WordPress Studio or Fabrement?
Both start free. Studio is free and open source, and Studio Code is free during its beta within a monthly limit. The Fabrement plugin is free and does not charge per action over MCP; you pay only for your own AI client.
Sources
WordPress Studio facts were checked on 25 September 2026 against the Studio page, its MCP documentation and its Studio Code documentation. 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.
Related articles
WordPress MCP Adapter vs Fabrement
The official MCP Adapter is the bridge that lets an AI agent call what WordPress plugins register. Fabrement is a plugin with…
WPVibe vs Fabrement
WPVibe gives an AI agent hands on the WordPress site you already have. Fabrement builds the whole site, from Figma to forms,…
How to Connect Claude to WordPress to Build and Run Your Site
Connect Claude to a WordPress site in the browser, the desktop app or Claude Code: one-click OAuth, the terminal commands or a…