AlphaBridge MCP 4.10.0

• Page-builder texts and search and replace in the free plugin, 82 tools in all. wp_update_builder_element and wp_search_replace came with AlphaBridge MCP Pro only; they work as they did there, with the same checks, and their messages come in the plugin's languages.
• wp_update_builder_element changes the text, link or image of one element on pages of the WordPress blocks, GenerateBlocks, Kadence Blocks, Spectra, Stackable, Pagelayer, Elementor, Beaver Builder, SiteOrigin Page Builder, SeedProd, WPBakery Page Builder, Divi 4, Avada, Flatsome and Enfold. It previews by default; applied, it records an undo point first, saves through the builder and reads the page back.
• wp_search_replace replaces across posts, postmeta, options and terms, safe for serialized and JSON values, with a dry run per table first. On page-builder pages (scope text) only the fields the builder's writer may change are touched, and matches in locked places are counted in locked_matches; scope raw replaces the stored data as text.
• New: post_ids and expected_count. post_ids keeps a replace to the posts it names; with expected_count, apply=true writes only when the call still finds as many matching rows as its dry run did.
• New: undo for option rows. The option rows a replace changes get an undo point of their own (options_undo_token), recorded before the first of them is written.
• Undo for page-builder pages. wp_undo puts every stored copy of a page back byte for byte and leaves a page changed since as it is, unless force=true.
• Protected options (the site address, active plugins and theme, roles and registration, the mail server, keys, AlphaBridge's own settings) stay out of every replace.

AlphaBridge MCP 4.9.0

• 22 more tools in the free plugin, 80 in all, undo included. Until now they came with AlphaBridge MCP Pro only; they work as they did there, with the same rights checks, and their messages come in the plugin's languages. wp_update_user_meta and wp_update_term_meta keep the backslashes in a value.
• Undo. wp_update_post (the post fields it changes, not custom fields or terms), wp_bulk_update_status and wp_update_site_settings keep an undo point with the previous values; wp_undo_list lists your own points, wp_undo puts one back (with dry_run=true it only shows what it would do), wp_undo_discard throws one away. If only part comes back, the undo point is replaced by one with just the rest (rest_token, same expiry), so trying again never writes back what already came back. Putting back a file's former parent needs the right to edit that post now. Undo points expire after 7 days; the newest 50 and 100 MB at most are kept, as copies in a protected folder in the uploads. A restore asks again for the right to the post or the setting, as the original change did. Undo points that Pro recorded on this site stay where they are: Pro reverses them, and without Pro they expire.
• Posts. Bring back an earlier revision (wp_restore_revision), set one custom field (wp_update_post_meta; page-builder data takes the unfiltered_html capability), and publish, unpublish or trash up to 500 posts at once (wp_bulk_update_status).
• Users. Create, change and delete user accounts (wp_create_user, wp_update_user, wp_delete_user), within the roles your own account may give; the last administrator cannot be deleted or demoted. Set user and term meta (wp_update_user_meta, wp_update_term_meta).
• WooCommerce. Change the price, sale price, stock and status of a product, the status of an order, and create coupons (wp_wc_update_product, wp_wc_update_order_status, wp_wc_create_coupon), with the right to the one product or order.
• Widgets and settings. Add, change and remove widgets (wp_add_widget, wp_update_widget, wp_delete_widget); set the site title, tagline, admin email, timezone and posts per page (wp_update_site_settings), each read back.
• Maintenance. Clear the object cache, OPcache and the page cache of supported caching plugins (wp_clear_cache), refresh the rewrite rules (wp_flush_rewrite_rules), optimise the site's database tables (wp_db_optimize) and remove expired transients (wp_cleanup_transients).
• All of them write only with write access on, as every writing tool does. Deleting the plugin also removes the undo points, unless AlphaBridge MCP Pro is still installed.

Also on WordPress.org: https://wordpress.org/plugins/alphabridge-mcp/

AlphaBridge MCP 4.8.1

The request for a review comes sooner and where administrators look. It appears once the plugin has been in use for 3 days with at least 25 successful tool calls (before: 14 days and 50 calls), as before as a strip in the header of Settings → AlphaBridge MCP and now also as a notice on the Dashboard and the Plugins screen, for administrators only. One answer ends it everywhere: «Write a review» or «Don't show again». It never comes back, also not after an update, and nothing is sent anywhere.

Also on WordPress.org: https://wordpress.org/plugins/alphabridge-mcp/

AlphaBridge MCP 4.8.0

SEO fields in the free plugin, 58 tools in all. wp_seo_set sets the SEO title, meta description and focus keyword of a post in Yoast SEO or Rank Math: only the fields given, tags and line breaks stripped, with the right to edit the post and each of its SEO fields. Until now it came with AlphaBridge MCP Pro only. A backslash in a value is stored as written, and so are the variables the SEO plugin fills in, such as %%category%% or %date%. With All in One SEO or without a supported SEO plugin the call is refused, and the answer says why and what to do.

Wording: the hub. The free service at connect.alphabridge-mcp.com that links your sites to Claude and ChatGPT is called the hub.

Also on WordPress.org: https://wordpress.org/plugins/alphabridge-mcp/