AlphaBridge MCP — free plugin
Your WordPress site, managed in conversation. AlphaBridge MCP turns a WordPress site into a
native Model Context Protocol server. Claude, ChatGPT and other
MCP clients connect over one authenticated HTTPS endpoint. They write and edit posts, pages,
media, categories and tags, reply to and moderate comments, set SEO titles and descriptions,
manage user accounts, widgets and site settings, change prices, stock and orders in WooCommerce,
read the outline of pages built with blocks or a common page builder, and undo a change with one
sentence. Every tool checks WordPress capabilities on every single call.
The site only reads until an administrator turns on one switch for write access. Then every tool
is on; each connection keeps its access level (full, content only or read only). Switching it
off takes one click.
This repository holds the source of the free plugin, published on the WordPress.org plugin
directory. It is the same code WordPress.org ships.
What it does
-
Native MCP endpoint — JSON-RPC 2.0 over HTTP POST at /wp-json/alphabridge/v1/mcp
(protocol versions 2024-11-05, 2025-03-26, 2025-06-18 and the stateless 2026-07-28, side by
side; the newest one can be switched off). Pure PHP inside WordPress: no Node middleware, no
external service, nothing extra to host.
-
82 structured tools across content, media, taxonomies, comments, widgets, menus, site
settings, site info, users, plugins and themes, cron and the error log, SEO fields, WooCommerce,
maintenance, page builders, search and replace and bulk status changes.
-
Undo — wp_update_post, wp_bulk_update_status, wp_update_site_settings,
wp_update_builder_element and wp_search_replace (page-builder pages and option rows) leave an
undo point with the previous values that expires after 7 days; wp_undo_list, wp_undo (with a dry run) and
wp_undo_discard work on the account's own points, and a restore checks the rights of the
original change again.
-
Page builders — wp_get_builder_layout reads a page as an outline: its elements in page
order, with their visible text, link and image fields; elements that cannot be read safely,
such as code, forms or unknown elements, are listed as locked, with the reason and without
their content.
- Read: WordPress blocks, Elementor, Beaver Builder, SiteOrigin Page Builder, SeedProd,
GenerateBlocks, Kadence Blocks, Spectra, Stackable, Pagelayer, Otter Blocks and CoBlocks
(both as plain blocks), WPBakery Page Builder, Divi 4, Avada (Fusion Builder), Flatsome (UX
Builder) and Enfold (Avia Layout Builder).
- Read according to the vendors' documentation: WPBakery Page Builder, Divi 4, Avada, Flatsome
and Enfold.
- Recognised, not read: Brizy, Themify Builder, Zion Builder, Live Composer, Cornerstone,
Thrive Architect, Bricks, Breakdance, Oxygen 6, Oxygen Classic, BeTheme (BeBuilder), Visual
Composer Website Builder, Divi 5 and Etch.
Where a builder shows its own data and post_content is only a copy — Elementor, Beaver
Builder, SiteOrigin Page Builder and Enfold — wp_update_post refuses a change to the content
while the builder is active, because it would not show, and says how to change the page
instead.
wp_update_builder_element changes the text, link or image of one element right in the
builder (WordPress blocks, GenerateBlocks, Kadence Blocks, Spectra, Stackable, Pagelayer,
Elementor, Beaver Builder, SiteOrigin Page Builder, SeedProd, WPBakery Page Builder, Divi 4,
Avada, Flatsome and Enfold), with a preview by default, an undo point before the write and a
read-back after it.
Security model
Handing an AI access to a site should feel safe, so control comes first:
- Write access off out of the box. A new site, and every site after updating from a version
before 4.4.0, starts with write access off: assistants can read content, media, terms,
comments, settings and the structure of the site. Every tool that creates, changes or deletes is
refused, and so is every reading tool noted only with write access (in this plugin the readers
of user profile fields and of the error log), with an answer that says why and leads to the switch. The main
switch Write access for AI assistants at the top of Settings → AlphaBridge MCP holds for every
connection (Claude, ChatGPT, Cursor and all others); an administrator switches it on after
confirming, with a ticked box, that changes take effect immediately, that it is at the site
owner's own risk and that a current backup exists. The account, the time, the version of that
notice and its wording are recorded. Switching on switches every tool on; switching off takes
one click.
- Every connection acts as a real WordPress user; every tool enforces the matching
capability, including object-level checks. What that user may not do, the AI cannot do.
- Scoped connections — read-only or content-only keys with optional expiry, rotatable in
one click.
- Fine-tuning — every tool is on, and switching write access on switches every tool on
again; switch single tools or whole groups off, and they vanish from the MCP surface until write
access is switched on the next time. Each tool shows a short name in the admin's language and
says whether it reads or writes.
Code reads the switch through
AB_MCP_Site_Mode (get(), is_full(), allows(),
runs_in_read(); the slugs read and full are write access off and on); a tool that reads
code, files, the database, logs or credentials is marked with 'dangerous' => true, which
keeps it out while write access is off. The action ab_mcp_site_mode_changed fires when write
access is switched, ab_mcp_reset_switches when a switch from off to on switched everything on
(add-ons switch their own items on there). The fine-tuning takes an add-on's fields into its one form
(filter ab_mcp_fine_group_html, action ab_mcp_fine_save).
- Positive allowlists instead of blocklists — arbitrary options and transients cannot be
read at all; only a fixed list of common site settings is exposed, and the settings of
registered widgets through
wp_get_widgets, without the values whose key the credential guard
below refuses.
- Layered meta protection — protected keys,
is_protected_meta() keys and two kinds of
credential-shaped key are refused: keys whose whole name is a credential word, singular or
plural (, , , , , , , ),
and keys containing one of a fixed list of compound patterns (, ,
, , , , , , …). The list is
matched literally, which makes the guard deliberately conservative rather than exhaustive:
ordinary keys such as , and counters such as pass it,
and so do camelCase spellings such as . It is defence-in-depth, not the primary
control. Generic meta access additionally passes WordPress's own per-key meta capability
( / / ), which honours rules
registered by other plugins — that is the layer doing the real work. Page-builder data that
ends up in the page as markup or code, also where a builder keeps it under a key without
(such as , , , , or
), is written through the argument of and
only for accounts with the capability; for any other
account the call is refused before anything is written. One read-only tool
reaches further, by design: , for an account that may edit the post,
reads the page builder's own stored data of that post, protected keys included, and returns
only the visible text, link and image fields of its elements — never the raw meta, code,
styling or attributes; separate keys that hold a page's own scripts or CSS are not read at
all.
copies protected keys too, into the new draft only and only for an
account that may edit the original: WordPress's own page template, featured image and list of
removed hooked blocks, and — with the capability, because it holds markup —
the post meta of page builders, each builder's keys together or not at all. Credential-shaped
keys, the original's editing state, the meta of a revision,
builder caches and other plugins' protected keys are not copied.
Details: https://alphabridge-mcp.com/security.html
Requirements
WordPress 6.5+ (tested up to 7.1) · PHP 8.0+
Installation
Install AlphaBridge MCP from your WordPress admin under Plugins → Add New, or from
WordPress.org.
To run this repository directly, clone it into your plugins directory as alphabridge-mcp:
git clone https://github.com/CultureClub-dev/alphabridge-mcp-free.git wp-content/plugins/alphabridge-mcp
Then activate it and open Settings → AlphaBridge MCP to create a connection.
Paid add-on
A separate commercial add-on, AlphaBridge MCP Pro, lets the assistant do more:
- change texts, links and images on pages of many page builders;
- run the abilities other plugins offer, and say so when such a run reports success on a post
but nothing was saved;
- edit plugin and theme files and the PHP snippets of Code Snippets or WPCode;
- check the site with test requests after saving active PHP code, and put the previous
version back automatically when one of them ends with a fatal error;
- use tool groups for the database, options, install/update, migration and multisite;
- undo its own changes too (page-builder elements, files, PHP snippets, options); undo points
expire after 7 days by default, adjustable from 1 to 30 days.
Its Agency plan adds Site Deploy for agencies and developers: files, themes and whole builds
published over SFTP onto the server the site runs on; ZIP deploys can run atomically, with
rollback when the swap fails.
Pro can be tried free for 7 days, no card needed. Both are entirely optional: this free plugin is
complete on its own and stays fully functional without them. Their source is not part of this
repository. Details at https://alphabridge-mcp.com.
Contributing & support
Bug reports and security findings are welcome — see SECURITY.md for the reporting
path. General support questions are best raised in the
WordPress.org support forum.
This repository mirrors released versions; day-to-day development happens elsewhere, so pull
requests may be applied by hand rather than merged directly.
License
GPL-2.0-or-later — see LICENSE.
A product of CultureClub Kulturagentur UG (haftungsbeschränkt).
