WordPress MCP Adapter vs Fabrement
The WordPress MCP Adapter and Fabrement both connect an AI agent like ChatGPT, Claude, Codex or Cursor to WordPress over MCP, so they get compared. They are different layers. The Adapter is the official bridge; Fabrement is a plugin with its own operations for building and running a site. This page says plainly where the Adapter is the better choice.
The short answer
The MCP Adapter is the WordPress project’s official bridge between the Abilities API and MCP. It exposes whatever abilities WordPress core and your plugins register, and nothing more. It is the right foundation if you are a developer who wants to expose your own plugin’s features to agents, the standard way.
Fabrement is a plugin that already has the operations for building a site: new blocks written as code from Figma, a screenshot or a sentence, all on one design system, then headers, footers, templates, pages, menus, forms, Yoast SEO and WPML translations. It ships its own MCP endpoint. It is the better choice when you want the agent to build now, not to write the abilities first.
Key takeaways
- The Adapter is infrastructure, not a builder. Its default server offers three tools: discover abilities, get ability info and execute an ability. What the agent can actually do depends on the abilities registered on the site.
- Fabrement is the operations. Dozens of them, for blocks, templates, pages, custom fields, menus, forms, media and SEO, with block code checked before it is saved.
- The Adapter has finer exposure control. Abilities are private by default and exposed one by one. Fabrement exposes its whole set of operations or none.
- The Adapter is the official direction. The WordPress 7.2 roadmap plans to publish it in the plugin directory and let administrators switch MCP on from the AI plugin.
- Both are free. The Adapter is open source. The Fabrement plugin is free; building blocks needs a Fabrement account because block code is checked by the service.
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. For the Adapter, many rows depend on which abilities other plugins register on your site.
| WordPress MCP Adapter | Fabrement | |
|---|---|---|
| What it is | The official bridge that exposes registered WordPress abilities as MCP tools | A plugin with ready operations to build and run the whole site, and its own MCP endpoint |
| Made by | The WordPress project, part of its AI Building Blocks work | 7Fridays |
| How you install it | Composer package from GitHub; the 7.2 roadmap plans a plugin directory release | Free .zip from fabrement.com; wordpress.org listing in review |
| Requirements | WordPress 6.9+ | WordPress 6.9+, PHP 8.0+, HTTPS |
| What the agent can do out of the box | Discover, inspect and run the abilities registered and made public on the site | A ready set of operations: blocks, templates, pages, custom fields, menus, forms, media, SEO, translations |
| Builds new blocks as code | Not listed: only if a plugin registers an ability for it | Yes: PHP, CSS and JS per block with editor fields, checked before it is saved |
| From Figma | Not listed | Yes, built in: frames become blocks with real flex and grid layout |
| Design system | Not listed | Colour roles, type scale and button styles used by every block |
| Templates, post types, archive pages | Not listed: depends on registered abilities | Headers, footers, templates, custom post types and their listing pages |
| Forms, SEO, multilingual | Only through abilities those plugins register themselves | Contact Form 7 and WPForms, Yoast SEO, WPML |
| Transports | HTTP and STDIO (for example through WP-CLI), plus custom transports | HTTP |
| Exposure control | Abilities are private by default and exposed one by one; per-ability permission checks | A fixed set of operations, all or none; no per-operation switch yet |
| Checks before writing | Each ability’s own permission check | Block code is checked before it is saved; publishing is a separate step from saving |
| Extending it | Yes, that is its purpose: register your own abilities and they become tools | No: you cannot add your own operations; you extend the site by having the agent build blocks |
| AI clients | Any MCP client | ChatGPT, Claude (web, desktop and Claude Code) and Codex with OAuth; Cursor and any HTTP MCP client; plus a chat inside wp-admin |
| Price | Free, open source | Plugin free; no per-action charge over MCP; building needs a Fabrement account |
Where the MCP Adapter is the better choice
- You are a plugin developer and want agents to use your plugin’s features the official way.
- You want to decide exactly which operations an agent can see, one by one.
- You want a local STDIO connection through WP-CLI rather than an HTTP endpoint.
- You want only open-source parts between the agent and the site, with no outside service.
- You are building your own agent product on top of WordPress and need the standard layer.
Where Fabrement is the better choice
- You want the agent to build a site now, not to write the abilities it would need first.
- You work from Figma and want frames turned into real, editable Gutenberg blocks.
- You want every new section built on one design system, so the site stays consistent.
- You need templates, custom post types with listing pages, forms, Yoast SEO or WPML handled in the same conversation.
- You want the code an agent writes checked before it reaches the site.
Can you use both?
Yes. They are different endpoints doing different jobs, and an agent can be connected to both. The Adapter is where WordPress core and other plugins expose their abilities; Fabrement is where the building happens. What the next WordPress release changes for this is in what WordPress 7.2 means for AI agents, and how Fabrement builds is on how Fabrement builds a WordPress site.
Frequently asked questions
Is the WordPress MCP Adapter an alternative to Fabrement?
Not directly. The Adapter is the bridge that exposes abilities registered by core and plugins. Fabrement is a plugin whose operations build and run the site. Without plugins that register building abilities, the Adapter gives an agent little to build with.
Does the MCP Adapter build Gutenberg blocks?
Not by itself. Its default server offers tools to discover, inspect and run abilities. Building blocks needs a plugin that registers that ability.
Which is more secure, the MCP Adapter or Fabrement?
They control different things. The Adapter keeps abilities private by default and checks permission for each one. Fabrement checks the code an agent writes before it is saved and keeps publishing separate, but exposes its operations all or none. In both cases the agent acts as a WordPress user, so give it only the access the job needs.
Will the MCP Adapter be in WordPress core?
Not in 7.2. The roadmap plans to publish it in the plugin directory and let administrators enable MCP from the AI plugin. AI features have to show adoption and practical value before they are considered for core.
Sources
MCP Adapter facts were checked on 25 September 2026 against its GitHub repository and releases (version 0.6.x, WordPress 6.9 required), and the Roadmap to 7.2. 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 Studio vs Fabrement
WordPress Studio gives an AI agent a local WordPress to build in, with files, WP-CLI and screenshots. Fabrement lets the agent build…
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,…
What WordPress 7.2 Means for AI Agents, and What It Still Leaves to Plugins
What the WordPress 7.2 roadmap brings for AI agents, from the official MCP Adapter to agent identity, and what building a site…