Latest release 1.12.0, 15 November 2026

What changed in every release

38 releases and 187 changes so far, copied straight from the plugin readme. Permission and security fixes are written out in full, not softened into a line about general improvements.

1.12.0

LatestRead the release post
4 features2 fixes

If you are upgrading: Adds element editing for WPBakery Page Builder and Avada pages, their templates and Library, admin-only builder settings and block-theme navigation tools. Every new tool starts off. Divi pages are no longer overwritten by update-page, update-post and replace-in-post.

  • Feature

    Agents can edit WPBakery Page Builder and Avada pages element by element with tools such as avada-update-element and wpbakery-insert-template. Restore revision works there too. See every tool.

  • Feature

    Users who can manage options can change WPBakery settings, Avada Global Options, layouts and Slider settings, and import Avada Studio items. Page CSS and page options can be set per page.

  • Feature

    list-navigations and update-navigation read and replace block-theme menus, pages take a parent and a template, update-site-settings sets the static homepage, and wc-update-product can remove an attribute.

  • Feature

    Connection adds Add to Cursor and Add to VS Code links and can end tokens issued for an old site address. Other plugins is now Plugins' own tools, and the accent follows your Admin Color Scheme.

  • Fix

    update-page, update-post and replace-in-post overwrote Divi page layouts and now refuse them, and avada-replace-text refuses a save that would strip other content.

  • Fix

    Expired or revoked OAuth tokens now get error="invalid_token", and alert emails go through WP-Cron on hosts that can't finish the page before sending.

1.11.2

Read the release post
2 features2 fixes1 chore

If you are upgrading: Change history now records agent edits from this update, in a new table kept 30 days and dropped on uninstall. Turn it off under Settings. The two new agent undo tools start off. wc-update-payment-gateway's order is now a zero-based position.

  • Feature

    A new Changes tab keeps 30 days of what agents changed with 25 tools and reverts a change if the item hasn't been edited since, and a site-wide find and replace reverts as one group. Every write tool now reports whether its change can be undone, with a reason when it can't (permanent deletes, orders, refunds).

  • Feature

    Two new tools, list-changes and undo-change, let an agent see and undo its own changes from the last 24 hours, up to 30 undo calls an hour per connection. Both start off, and undo-change is destructive, so the Read only, Content editor and Shop manager presets leave it out.

  • Fix

    wc-update-payment-gateway's order is now a zero-based position, as wc-get-payment-gateway reports it, and the write renumbers the stored gateway order, so a script that passed a stored sort value now gets a position. wc-get-order returns payment_method and payment_method_title, a variation's sale price can be cleared with an empty string, and WordPress's export and erase personal data tools now cover the activity log and the new change history.

  • Fix

    A refund above the remaining amount, a user deleting their own account, deleting or demoting the last administrator, a missing reassign user, trashing an item already in the Trash and a tool aimed at a content type that isn't exposed now each return a named error instead of a generic one.

  • Chore

    Change history is stored in its own table, which is dropped on every uninstall and emptied by Reset, and several tool descriptions and messages were reworded.

1.11.1

Read the release post
4 fixes1 chore

If you are upgrading: The high-risk lock now holds wc-create-order (not under Shop manager), WooCommerce's order status and update tools, and SCF's type tools. Post tools stop reaching a type whose own tool is off, read_private_posts alone no longer shows others' drafts, and five more page builders refuse writes.

  • Fix

    The high-risk lock now holds wc-create-order, WooCommerce's own order status and order update tools, and the Secure Custom Fields tools that can store a callback name, and its filter accepts other plugins' slugs. Shop manager connections no longer reach wc-create-order, and post tools no longer reach a type whose own tool is off.

  • Fix

    Agent writes to WPBakery, Bricks, Oxygen, Breakdance and Brizy pages are refused, but a page builder's post or page now accepts an edit that only sets the excerpt and keeps its stored content as it was, unless the plugin can't tell which builder owns it. A role with only read_private_posts no longer lists other people's drafts, the user meta tools can't reach the MCP session store, Test connection no longer sends your login cookies to another host, and a bridged tool's crash text no longer reaches the agent under WP_DEBUG.

  • Fix

    Bridged WooCommerce product create and update tools no longer leave ChatGPT stuck on an old tool list. Rank Math's get-head shows a post's own title and description, the Activity Log records which object each built-in write tool changed (a count for the site-wide replace), and invalid URLs, an event end before its start, a sale price above the regular price and similar bad input are refused with an error instead of being saved or ignored.

  • Fix

    A batch of smaller fixes across Quick Connect and Reset, subsite deletion, Force draft on product variations, meta tools that now say why a key was refused, the product types wc-create-product offers, protected excerpts, term backslashes, empty meta, SEO head and search answers, OAuth discovery on subfolder installs, and LiteSpeed and WP Fastest Cache purging after agent meta writes.

  • Chore

    Five old admin save actions are gone (a script calling them directly should use aafm_save_abilities_page), readme wording is corrected, and integration minimum versions are listed.

1.11.0

Read the release post
3 features1 fix1 chore

If you are upgrading: Tools that other plugins add after an update wait for your review and stay off until you switch them on. Nothing you have switched on changes.

  • Feature

    The Other plugins tab says which plugin provides each group of tools (or its namespace, when the plugin cannot be identified), labels each tool Read, Write or Destructive from the plugin's own annotations (an unlabelled tool is treated as destructive and says so), and marks tools that may return personal data such as form entries, orders, learner or member records. That mark is a hint from the plugin and tool name, not a full check.

  • Feature

    When a plugin update or a newly activated plugin adds tools, a "New tools since your last review" card lists them. They stay off until you switch them on, and Settings can send a notification for them.

  • Feature

    Each plugin on the Other plugins tab has an "Allow only read tools" button, and the Activity Log can filter to one plugin's tools.

  • Fix

    A bridged tool's error names the plugin, using the name from its header once cleaned up, for example "WPForms Lite" instead of "wpforms", or names the tool namespace and says so when the plugin cannot be identified. The Quick Connect note no longer promises deletes go to Trash, the upload tools name the upload-files capability, and Content editor and Shop manager say they can read playbooks.

  • Chore

    The TEC events list says whose draft events it returns, the Avada descriptions lost a dash, and leftover internal notes came out of the plugin's PHP comments.

1.10.2

Read the release post
4 fixes1 chore

If you are upgrading: Content editor and Shop manager connections can now read your playbooks. Nothing else needs changing.

  • Fix

    A request from another site's web page now gets a 403 even when it carries wrong credentials, and responses requested with ?_envelope=1 send Cache-Control: no-store like every other response.

  • Fix

    Content editor and Shop manager connections can read playbooks. The Playbooks editor refuses to save over a playbook someone else changed after you opened it, and keeps your text in the form.

  • Fix

    The unknown ACF field refusal names fields only for callers who can list them. A paused connection no longer leaves a "paused" note in the server instructions after you resume it. An app the site no longer recognizes now gets the steps and MCP URL to add it again.

  • Fix

    Seven integration tool descriptions now match what the tools do, and every description that lists page builders names all five.

  • Chore

    The ability picker on the Playbooks tab has space between its search box and the count line.

1.10.1

Read the release post
1 feature3 fixes1 chore

If you are upgrading: Nothing changes until you use the new Playbooks tab, and its two tools stay off until you turn them on. Browser pages on other sites can no longer call the MCP endpoint, and refusals now say why.

  • Feature

    The new Playbooks tab holds step-by-step instructions for agents. Tick the abilities each one uses or add one of five starters. Two read tools, off until you enable them, let agents list and load Active playbooks.

  • Fix

    A paused connection now signs in and lists tools, and each tool call returns a message that the connection is paused. Claude used to show a firewall or sign-in error instead.

  • Fix

    The MCP endpoint refuses requests from web pages on other sites, as the MCP specification requires, and sends Cache-Control: no-store on every response. Clients that open with server discovery now get the playbook list too.

  • Fix

    A blocked address, the rate limit and an unknown ACF field name now say why in the refusal. An unreadable playbook list is reported rather than overwritten, and a connection row shows Saved after you save it.

  • Chore

    New FAQ answers cover refreshing a client's tools, ChatGPT plans, playbooks and refused browser clients. The delete-tool and ChatGPT menu wording is corrected.

1.10.0

Read the release post
4 features1 fix

If you are upgrading: Existing connections keep their access, and the new block tools stay off until you turn them on. Writes can return new content warnings, new drafts report real GMT dates, and for users who can post unfiltered HTML an & in plain block attribute text is stored as written.

  • Feature

    Each OAuth connection can be paused and resumed without signing in again, given an end date and a lower rate limit of its own, and shows when and from which address it was last used. Approving an app, and Quick Connect, offer Read only, Content editor, Shop manager or Custom access.

  • Feature

    The Connection tab now has OAuth and Application Passwords tabs, a token lifetimes card (the client registration switch moved there from Settings), a switch that pauses all MCP access to the site, and a list of the agent users' Application Passwords with their last use and a Revoke button.

  • Feature

    Settings can limit which roles may connect an app and can read the visitor's real address behind Cloudflare or another proxy. Connection Doctor checks MCP headers, JSON bodies, redirects and stale or blocked discovery documents; the Dashboard says why an enabled tool is missing; tabs show a dot while they have unsaved changes; the Abilities tab opens on an All view listing every ability under its category, with the same bulk buttons each category has.

  • Feature

    Agents can list the site's block types and read one block's attributes, supports and styles, plus, for ACF blocks, its field names, choices and an example payload. A new Replace block tool swaps one block in a post or page without resending the whole page. Like every other tool, they stay off until you turn them on in the Abilities tab.

  • Fix

    Plain attribute text that WordPress would only entity-encode, such as an & in an ACF field, is now stored as written for users who may post unfiltered HTML, style and script elements are removed with their contents, WooCommerce product descriptions and Events Calendar events no longer strip the backslash escapes from block attributes, and writes that return content warnings now also flag unknown blocks or ACF fields, invalid attribute JSON and ignored block gaps. A custom-field-only change now clears that post's or term's cache entry (with an action for page caches and an opt-in full re-save for caches that need one), blank-looking IP allowlist lines are dropped, Settings and the Dashboard no longer scroll sideways on a phone, new drafts report real dates, OAuth clients and tokens record their creation time in UTC, and the Activity Log and Connection Doctor show placeholders while they load. The bundled MCP Adapter moves to 0.7.1.

1.9.0

Read the release post
2 features1 fix1 chore

If you are upgrading: Adds a searchable Activity Log and optional alerts, both safe to ignore: alerts stay off until you turn them on. The log table gets one new column the first time an admin page or an MCP request loads after the update. The CSV export has two new columns at the end.

  • Feature

    The Activity Log can be searched and filtered by user, connection, tool, plugin, date and text. Each call shows its connection and IP address, and its duration when it ran; the log adds a 7-day summary and a Live view. The CSV export follows your filters.

  • Feature

    Optional alerts, off by default: an admin notice, an email right away or a daily email when an app is authorized to connect, an Application Password is created for a user who can edit posts or for the agent user, a high-risk tool or permanent delete runs, calls are denied in a burst, or read-only mode or the high-risk lock is switched.

  • Fix

    A denied call now records why in the Activity Log, for example "key is not on the allowlist"; the message the agent sees is unchanged. Reading a meta key now logs a note the way writing one does.

  • Chore

    The Cloudflare advice in the FAQ, README and Help tab now points to "Configure AI bot policies" instead of the deprecated "Block AI bots" switch, and adds steps for WP Engine edge traffic rules and HTTP 429 limits.

1.8.1

1 fix

If you are upgrading: Fixes bridged tools, such as WooCommerce orders and products, that failed in strict clients like Claude when a value didn't match its declared format. No settings change needed.

  • Fix

    Bridged tools such as WooCommerce orders and products failed in strict clients like Claude when a value didn't match the format the source plugin declared, for example a date without a timezone or an empty URL. Bridged tools no longer advertise strict formats; the values are unchanged.

1.8.0

Read the release post
3 features2 fixes

If you are upgrading: Other plugins' MCP tools on the Adapter's default server work again, through a new Settings switch that starts on Automatic. Adds Site Brief, Connection Doctor and a Needs review card. A site using only WordPress core abilities should pick Always on.

  • Feature

    A Site Brief box on the Settings tab lets you describe your site in a few lines. Every agent that connects to this plugin reads it.

  • Feature

    The Connection tab has a Connection Doctor. One click checks the connection from your own server and tells you what to fix, for example a host that strips the Authorization header.

  • Feature

    A Needs review card on the Dashboard lists the drafts your agents wrote, with Preview, Open in editor, Publish and Discard buttons. Discard moves the post to the Trash.

  • Fix

    Other plugins' tools on the MCP Adapter's default server stopped working while this plugin was active. A new Settings switch (Automatic, Always on, Always off) brings that server back, and existing sites move to Automatic, which starts it only when another plugin publishes tools there. This plugin's own tools never appear on it, so a site that used it only for WordPress core abilities should pick Always on.

  • Fix

    With Force draft on, an agent that sent "publish" again for a post that was already live took it offline. The post now stays live. A "WP_MCP_VERSION already defined" warning next to the standalone MCP Adapter 0.6.x and a Settings crash with an older adapter copy are also fixed, and the plugin title now names Claude and ChatGPT.

1.7.10

1 fix
  • Fix

    Query Monitor showed a "bundled dependency" deprecation warning from the MCP Adapter on every request that started it; it no longer does.

1.7.9

Read the release post
3 fixes1 chore
  • Fix

    With the standalone MCP Adapter plugin (0.7.0) active and loading before this one, the /mcp endpoint returned a 404. It now serves in either load order.

  • Fix

    The standalone MCP Adapter plugin showed a red "Another version of MCP Adapter is already loaded" notice while this plugin's copy was in use. It no longer does.

  • Fix

    The adapter's per-request "bundled dependency" deprecation line no longer lands in the PHP error log.

  • Chore

    The bundled MCP Adapter moves from 0.6.1 to 0.7.0, and adapter versions 0.6.1 through 0.7.x are supported. The adapter itself now returns error -32602 instead of -32003 for an unknown tool, and clients must send the MCP-Protocol-Version header after initialize.

1.7.8

Read the release post
1 feature4 fixes
  • Feature

    A bridged ability's error now says which plugin returned it, and the Activity Log records that plugin's error code (the code only, never its message).

  • Fix

    37 bridged tools from WooCommerce, Meta Box, SiteOrigin, Premium Addons, SEOPress, WPForms, Elementor and ElementsKit worked when called but never showed in the tool list. They now list for users who can edit posts, and the source plugin still decides whether a call is allowed.

  • Fix

    Deleting through bridged ACF reported an error after the item was already deleted. It now returns ACF's own result.

  • Fix

    Bridged results holding plain objects (such as a PixelYourSite response) were refused after the write had already happened. They now come through, and a refused call is logged as an error instead of success.

  • Fix

    On WordPress 7.0 and later, the raw exception text from a throwing plugin no longer reaches the client.

1.7.7

Read the release post
2 features3 fixes
  • Feature

    The Abilities tab now has one Save changes button that saves every section on it, with an "Unsaved changes" note and a warning if you leave the page with edits pending.

  • Feature

    The Activity Log gets a row when an exposed list changes (content types, or post, user or term meta keys), giving the list name and how many keys were added and removed.

  • Fix

    Edits to exposed meta keys or content types were lost when you pressed only the main Save. The four separate section buttons are gone, and the one Save covers them.

  • Fix

    When a section fails to save, the page names it and keeps your edits so you can retry. Sections that did save stay saved.

  • Fix

    The Activity Log table scrolled sideways when a value such as the detail JSON was long; the columns now share the page width and long values wrap.

1.7.6

Read the release post
5 fixes

If you are upgrading: Security fix for sites with OAuth turned on: an MCP token could also act on other parts of the site. It now works on the MCP endpoint only. Meta, SEO, WooCommerce and event writes also report what actually saved.

  • Fix

    An OAuth token issued for the MCP endpoint also signed its holder in on other REST routes, admin-ajax.php, admin-post.php, the comment form, the OAuth authorize screen and discovery URLs. It now works on the MCP route only.

  • Fix

    Meta, SEO, media, WooCommerce and The Events Calendar writes now check the database for what actually landed and report written, unchanged, refused or a failed read. The Activity Log records each outcome, identifiers only.

  • Fix

    Read-only mode, the high-risk lock, ability switches and the allowlist are read from the database on every MCP request. A failed read keeps the stricter setting, so a stale object cache can't loosen them.

  • Fix

    WP-CLI printed a pair of "called incorrectly" notices for each enabled bridge tool whose source plugin was inactive; those tools are now skipped quietly. Activity Log rows for denied calls now read "Attempted: ..." instead of looking like the change happened.

  • Fix

    Under a persistent object cache, the review prompt wiped other plugins' cached "option doesn't exist" entries; it now clears only its own. Smaller fixes land in replace-sitewide, WooCommerce gateway ordering, the Rank Math and AIOSEO head previews, and several tool descriptions.

1.7.5

Read the release post
1 feature4 fixes
  • Feature

    The Connection tab swaps the allowlist textarea for a searchable checkbox picker and adds role and client selects, a Client ID copy control, paginated tables, and cross-tab abilities search.

  • Fix

    A zero-match abilities search left the Save button stranded on an empty card; the savebar now hides and returns with the results.

  • Fix

    The client picker's hover and selected states looked identical; hover is now a border outline only.

  • Fix

    Ability order now survives a re-save, a stale search clears on keyboard navigation, a large allowlist no longer renders every checkbox at load, and new controls have accessible names and translations.

  • Fix

    Post, block and template writes now confirm what landed, a stuck OAuth migration can no longer re-enable a switch you disabled, comment counts no longer include hidden comments, and a failed token revoke no longer reports success.

1.7.4

Read the release post
2 features3 fixes

If you are upgrading: New abilities for The Events Calendar, Slim SEO, Avada, GeoDirectory and URL media upload stay off until you turn them on. On pages owned by Elementor, Divi, Beaver Builder or Avada, a write that would silently do nothing is now refused.

  • Feature

    26 new abilities cover The Events Calendar, Event Tickets, Slim SEO, Avada, and GeoDirectory, plus uploading media straight from a URL. All of them stay off until you turn them on.

  • Feature

    A page-builder guard refuses a write that would silently do nothing on a page owned by Elementor, Divi, Beaver Builder, or Avada. A new allowlist narrows what each role or connection can reach.

  • Fix

    The bump to mcp-adapter 0.6.1 closes a multisite bug where a real subsite connection was reported as failed.

  • Fix

    Several OAuth paths treated a failed database read as permission granted. A deactivated client, a missing client record, or an unreadable registration limit now refuse the request instead of letting it through.

  • Fix

    Grants belonging to a deleted user are cleared out, the Connections screen shows each identity's current role, and a batch of smaller fixes lands across WooCommerce, the admin screens, and the connection tab.

1.7.3

Read the release post
2 fixes

If you are upgrading: If your site runs Redis, Memcached, or another persistent object cache and read-only mode or the high-risk switch would not turn off, this update fixes it. Nothing else changes.

  • Fix

    The plugin is now fully compatible with a persistent WordPress object cache (Redis, Memcached, or a host's own drop-in): a switch you turn off stays off, and a change that did not take is reported instead of logged as done.

  • Fix

    Reset to defaults and delete-on-uninstall clear the plugin's own option cache entries too, so a stale cache cannot bring a setting back after a reset.

1.7.2

Read the release post
2 features3 fixes

If you are upgrading: Dynamic client registration is now on, including on sites that never touched it, so ChatGPT and Claude connect without extra steps; you can turn it off on the Settings tab. Also fixes an OAuth redirect bug and adds transport logging to the Activity Log.

  • Feature

    The consent screen an agent sees at sign-in was rebuilt. It carries a real brand mark, your Site Icon, and the connector's own icon when the plugin recognizes it by its verified redirect host.

  • Feature

    The Activity Log now records every MCP request that reaches WordPress. A sign-in with no calls after it means a CDN or firewall stopped the agent before it arrived.

  • Fix

    ChatGPT could not connect on sites where dynamic client registration was off. It has its own switch on the Settings tab again, on by default, and existing installs get switched on when they update.

  • Fix

    Three connection bugs are gone: the OAuth authorize step mangled percent-encoded redirect addresses, a failed session write handed back a session ID that did not exist, and a very large tool schema could exhaust memory while the tool list was built.

  • Fix

    Smaller correctness fixes across WooCommerce, ACF, and Rank Math, plus a wrong capability check on delete-revision, OAuth options left behind at uninstall, and a new readme FAQ for CDNs that block the agent at the edge.

1.7.1

Read the release post
8 fixes1 chore
  • Fix

    lang:"all" measured a partial set of languages and reported success anyway. It now queries every configured WPML language for posts, pages, media, terms, search, and WooCommerce products, and the shared count helper sums across all of them.

  • Fix

    A tool's visibility in tools/list could disagree with what its execute-time permission check actually allowed, both ways, hiding tools an agent could use and advertising ones it couldn't. Discovery is reconciled with execute-time permissions across custom post types, pages, and ACF term fields.

  • Fix

    The RFC 9728 protected-resource-metadata route 404'd at the path agents actually request it at, breaking Claude connections for at least one user who reported it. It now resolves at the path-suffixed URL the spec calls for.

  • Fix

    moderate-comment reported failure when a comment was already in the requested state (already approved, already spam, and so on), even though nothing was wrong. It reports success on a no-op now, and no longer logs one as an audit error.

  • Fix

    Several code paths could short-circuit or reject a call before it finished, leaving a stuck or unreadable "started" row in the audit log rather than a real outcome, including on WordPress cores before 7.1. Every invocation now gets a unique token and closes out its row cleanly.

  • Fix

    Bridged output from a third-party plugin's own ability could hide an unsafe object a level or two deep. The bridge now recurses into the result to find it, and refuses a bare or ambiguous object rather than assuming it's safe. Bridged output isn't redacted the way this plugin's own abilities' output is, and the readme now says so.

  • Fix

    Media uploads now go through WordPress's own sideload handling and re-sanitize the resulting attachment's content, and the pixel-size cap that no longer matched that path is gone.

  • Fix

    A batch of smaller correctness fixes across WooCommerce, ACF, AIOSEO, Rank Math, and Yoast: writes and reads route through each vendor's own functions instead of re-deriving their behavior, plus fixes to tool descriptions, cache invalidation, and a few pages that had the wrong discovery floor.

  • Chore

    Uninstall now clears both daily cron events, not just the one tied to deleting data.

1.7.0

Read the release post
2 features6 fixes1 chore

If you are upgrading: Tested up to WordPress 7.1. Without ImageMagick, an upload too large to decode in memory is refused up front. The Abilities tab adds an Enable all writes button; deletes and high risk abilities still need turning on by hand.

  • Feature

    Sections on the Abilities tab now have an "Enable all writes" button beside "Enable all reads". It ticks the ordinary writes and leaves deletes and high-risk abilities alone.

  • Feature

    The audit log records more. Permanent deletes name what they removed, and term meta, user meta and site settings updates name the keys they wrote. It logs names and identifiers, not the free text a call carried.

  • Fix

    An authorize request in flight when you revoked a grant could still mint a code, and the token endpoint never re-checked consent, so that code redeemed into a working token after the screen said the revoke had succeeded. Consent is checked again at redemption.

  • Fix

    Payment gateway settings returned camelCase credential keys in full and marked none of them redacted. Authorize.Net's apiLoginID and transactionKey are the real case.

  • Fix

    Four ACF writes destroyed stored content and then reported failure: an unresolvable flexible content layout, clearing through a near-matching address, a protected-meta check that read the caller's address instead of ACF's, and a sub-field write landing under an undeclared name. All are refused before anything is written.

  • Fix

    WooCommerce counted refunds as orders, so a store with six orders and three refunds reported nine. Variations were validated against a display filter rather than the parent product, a variation delete reported failure on success, and an order lookup that threw escaped its rollback.

  • Fix

    Two refusals over MCP said "Permission denied" when that was not the problem. Setting alt text hit it because WordPress stores alt under a protected key, and the refusal now names aafm-update-media instead. A call missing a required argument hit it too, and now gets the schema error naming what is missing.

  • Fix

    Invisible characters are stripped from text on its way into storage, covering WooCommerce, SEO and ACF fields, order addresses and stored post text. Permanent deletes stop offering recovery the site cannot deliver, and an ability declaring no risk is treated as a permanent delete. Plus smaller fixes across shipping zones, menu listings on WordPress 6.9, ACF container writes, the first-run wizard, and refusal messages that named the wrong cause.

  • Chore

    Tested against WordPress 7.1. An accessibility pass over the admin screens covers keyboard operation, focus rings under forced colors, and proper names on toggles and table headers. OAuth housekeeping is sturdier, with InnoDB tables so token work rolls back and a cleanup cron that heals itself on subsites. A notice now asks for a wordpress.org review once the plugin has been carrying traffic for a while, and it can be dismissed for good. Vendor repository metadata no longer ships to wordpress.org.

1.6.3

2 chores
  • Chore

    Condensed the changelog so the full release history fits within the wordpress.org listing's length limit, in both readmes. Same releases, fewer lines, with the security and data-integrity fixes still called out one by one.

  • Chore

    Corrected a code comment that slightly overstated when a consumer plugin's short-circuit is visible to the rate-limit release hook.

1.6.2

Read the release post
1 feature8 fixes1 chore
  • Feature

    The admin activity log can filter on "Started", the state a crashed call leaves behind, matching what the activity-log ability already exposed.

  • Fix

    Closed a privilege gap where editing a WooCommerce customer, or writing user meta or ACF user fields, needed only the manage-WooCommerce capability and could read or overwrite any account's details. These require a real user-editing capability now and sit behind the high-risk lock.

  • Fix

    The rate limit on the OAuth endpoints never took effect on sites with no persistent object cache, which covers most shared hosting. It does now, and the per-user limit no longer counts each call twice.

  • Fix

    Several WooCommerce writes reported success when nothing happened: deletes that removed nothing, order-status changes that failed to apply, and per-line refunds that quietly became full refunds. Each is confirmed or refused before it reports success now, and an invalid billing email no longer erases the stored address.

  • Fix

    Bad values that used to be coerced silently are refused now: unparseable sales-report and coupon dates, non-numeric coupon amounts, negative limits, unknown tax classes (which had been filed under Standard and changed checkout tax), and a stock status set while stock management is on.

  • Fix

    ACF repeater, group, and flexible-content writes saved their rows but reported a failure, so an agent would retry over content it had already published; and fields nested in flexible-content or clone layouts were sanitized as plain text, flattening rich text and letting a javascript: link through. Both are fixed, at any nesting depth.

  • Fix

    Tightened what an agent can see and reach: an enabled admin-only tool could leak into a lower-privileged connection's tool list, an SEO head read could return for a post type the operator had not exposed, and a caller on a blocked IP could flood the activity log with denial rows.

  • Fix

    Multisite activation creates the plugin's tables on every site now, including sites added later; deleting a user reports that they were only removed from the current site rather than fully deleted; and creating an agent user honours the network's add-new-users setting.

  • Fix

    Corrected a run of tool descriptions and operator disclosures that overstated behaviour (what the activity log stores, how the ACF maps are keyed, count semantics, revision reversibility), and fixed a batch of smaller crash and response-shape defects across posts, blocks, comments, WPML, and SEO reads.

  • Chore

    Cleared stale comments and dead test scaffolding, and brought the WooCommerce test stubs in line with what the real plugin does.

1.6.1

2 features6 fixes1 chore

If you are upgrading: Fixes a crash: calling a bridged ability with arguments could take the site down on 1.6.0. Empty term, meta, and settings maps now encode as objects, so strict clients stop rejecting page reads. The activity log no longer stores raw error text, which could quote your data.

  • Feature

    A new aafm_ability_resolved action fires when a call finishes, so an uptime monitor or a logging plugin can react to a failure instead of waiting for someone to open wp-admin.

  • Feature

    The activity-log ability returns each entry's detail, so an agent can read why a call failed, not only that it did.

  • Fix

    Empty category, tag, custom-field, gallery, settings, and user maps returned an array where the schema declares an object, so a strict MCP client rejected the whole response. Reported by an outside user as issue #81; the sweep it prompted fixed the same defect across the catalog.

  • Fix

    Calling a bridged ability from another plugin with arguments could take the site down on 1.6.0, because the bridge rewrote the source plugin's schema into a shape WordPress core's validator cannot read. That rewrite is gone.

  • Fix

    The activity log stored the raw text of an unexpected error, which for a plugin like WooCommerce often quotes the value that caused the failure, such as an email or a SKU. It records the error's type and location now, which cannot carry your data.

  • Fix

    A permission check that failed unexpectedly returned the underlying error to the connected agent and could empty the entire tool list; it denies the call and records it now.

  • Fix

    Shipping method reads returned WooCommerce's legacy global settings, empty for zone methods since WooCommerce 2.6, so a title or cost you just wrote did not show up; they report the real per-instance configuration now. A variation no longer claims it manages stock it inherits from its parent.

  • Fix

    Coupon and product validation that used to crash or save a bad record returns a clean error now: a percentage coupon over 100 (including one raised past 100 by a later type change), a duplicate variation SKU, a negative amount, and a maximum below the minimum.

  • Chore

    Corrected copy and a code comment: the two shipping-method reads and the consent screen note that a method carries its own per-instance settings, and the settings redactor is described as the best-effort denylist it is, not deny-by-default.

1.6.0

3 features1 fix1 chore

If you are upgrading: Read-only mode is new: one switch on Settings stops every write ability from registering, including abilities from other plugins. It enables and disables nothing on its own, so your selections are untouched. Minimum PHP is now 7.4.

  • Feature

    Read-only mode, a switch on the Settings tab that stops any ability that writes from registering as an MCP tool, whatever is ticked, and it covers abilities from other plugins too. Turning it on or off enables and disables nothing by itself, so your selections survive, and finishing Quick Connect without choosing write access turns it on rather than ticking boxes.

  • Feature

    An "Enable all reads" button on the Abilities, Integrations, and Bridge tabs ticks every read ability in a section and leaves the writes alone.

  • Feature

    The page header states the site's posture on every tab (read-only, read plus write, or read plus write with high-risk unlocked), worked out from what would actually register rather than the stored setting. Turning read-only mode on or off is recorded in the activity log.

  • Fix

    A refund amount with surrounding whitespace is trimmed before the numeric check now, several lists that could sort differently on PHP 7.4 than on 8.x sort the same everywhere, and an ability from another plugin that returns an unexpected shape is caught and reported rather than failing further down.

  • Chore

    The minimum PHP version is now 7.4, down from 8.0. The Settings tab is reorganised with Safety controls up front, the "Other plugins" tab has its own name and icon, and the listing leads with what the plugin gives you rather than the generic "for AI agents" framing.

1.5.0

3 features3 fixes1 chore

If you are upgrading: Creating a WooCommerce customer now also requires create-users, and listing or reading a customer now also requires list-users; a stock Shop Manager loses both. Eight WooCommerce abilities that move money or grant authority stay locked until you switch on a new master switch on Settings.

  • Feature

    Eight WooCommerce abilities that move money or grant authority (refunds, order status and updates, payment gateway settings, coupon and tax-rate creation and updates) are locked by default now behind a single audited master switch on the Settings tab.

  • Feature

    The activity log records ability toggles and setting changes, not only calls, with a detail column that names what changed and links each identifier to its edit screen, and it can be exported as a CSV carrying the current filter.

  • Feature

    A failed Application Password attempt against the MCP endpoint is logged now, and rate limited per source IP so a credential-stuffing run cannot flood the log.

  • Fix

    Creating a WooCommerce customer requires the create-users capability now, and listing or reading one requires list-users, closing a gap that let a caller with only manage-WooCommerce read any user's email, address, and phone, administrators included. A stock Shop Manager is denied both where it was not before.

  • Fix

    Payment gateway and shipping settings could return secrets under field names the redaction list missed, such as passphrase and salt, and deleting a product variation did not check the caller's capability on that specific product. Both are fixed.

  • Fix

    A run of admin-log defects: an identifier could link to the wrong object, the Event and Detail columns could misalign after filtering, a large export could truncate while looking complete, and counts did not refresh until reload.

  • Chore

    Clarified copy on what an Application Password grants, that uninstalling does not revoke access on its own, and that an OAuth grant's requested scope does not limit the token; the rate-limit setting notes it ships off with a suggested starting value.

1.4.3

Read the release post
3 fixes1 chore

If you are upgrading: Media reads now return only the caller's own uploads unless they can edit other people's posts. An agent on a lower role will see less than before. Also fixes a WooCommerce delete permission gap and two OAuth conformance bugs.

  • Fix

    Media reads handed the whole library to anyone who could upload a file or edit a post; an agent connected as an author sees only what it uploaded now, and the media count follows the same rule. Deleting a WooCommerce product checks whether that particular product was yours to delete.

  • Fix

    A duplicate product SKU or coupon code returns a message naming the collision now instead of an uncaught error, and a bridged ability that answered with a bare list where the protocol asks for an object is always shaped as an object before it reaches the wire.

  • Fix

    The OAuth 401 pointer compared the request path case-sensitively, so a differently-cased request got no pointer, and the authorization response left out the issuer RFC 9207 requires. Both are fixed, on error redirects too.

  • Chore

    Tightened the build checks that guard these tools, including one that quietly passed any ability whose code it could not read.

1.4.2

Read the release post
1 feature2 fixes1 chore

If you are upgrading: Fixes a bug where asking an agent to create a draft published the post live instead, and a related permission gap around scheduled posts. Also stops a WooCommerce order update from adding line items when you meant to change them. Every tool input is now documented, so agents guess less.

  • Feature

    Every input on every tool explains itself now, all 505 of them, where only three abilities were fully documented before.

  • Fix

    Post status was ignored on create: "create a post as a draft" published it live and reported success. Create honours the status you ask for now, treats scheduling and private as publishing, and refuses a status your user cannot publish, on custom post types too.

  • Fix

    Updating a WooCommerce order with line_items added items rather than changing them, quietly raising the total; there is a clear add_line_items field now, and a request mixing valid and invalid product ids is fully validated before anything is written. A product type that does not match the product returns an error instead of being discarded.

  • Chore

    Added a build check that fails when any tool input goes undocumented, so this cannot drift back.

1.4.1

Read the release post
4 fixes1 chore

If you are upgrading: Standards fixes for OAuth and strict MCP clients. OAuth errors now use the RFC 6749 shape instead of WordPress's, an unknown or disabled tool no longer tells your client its session died, and discovery stops advertising an endpoint that is off. No settings or abilities changed.

  • Fix

    OAuth errors came back in WordPress's {code, message, data} shape instead of the {error, error_description} shape RFC 6749 requires, so no standard OAuth client could read them; reported as issue #68, and wrong since the first release. A malformed JSON body to an OAuth route escaped with the same wrong shape and no cache headers.

  • Fix

    Responses that carry a credential were missing Pragma: no-cache next to Cache-Control: no-store, including the token response.

  • Fix

    Calling a tool that does not exist or is switched off returned HTTP 404, which the MCP spec reserves for a dead session, so an ordinary mistake told the client to reconnect; it returns the right error now. The OAuth discovery document no longer advertises a client-registration endpoint when dynamic registration is off.

  • Fix

    Every ability declares openWorldHint false now, which the MCP schema otherwise reads as "may reach the open internet", the opposite of what the plugin actually does.

  • Chore

    Rate-limited OAuth responses send Retry-After now.

1.4.0

1 feature1 fix
  • Feature

    A first-run Quick Connect wizard gets a new admin connected on one screen: turn on OAuth and copy the endpoint, or create a dedicated agent user and generate an application password, then switch on content reads and, if you want, writes. A menu pointer greets a brand-new install and points to the plugin page.

  • Fix

    The onboarding "Connect your agent" step and the "Agent users" count no longer read any application password as a connected agent; they track the agent users this plugin created or an approved OAuth connection, so an unrelated password stops showing a false "done" or padding the count.

1.3.2

1 feature1 fix1 chore
  • Feature

    Content reads (posts, pages, search, terms, media, products) take an optional language argument now and report which language they returned, and a single-item read can fetch a specific translation. Sites without WPML are unaffected.

  • Fix

    On a WPML site the content lists returned only the default language while the counters reported every language; the counts match the returned language now, and the menu-item tools no longer report a false failure when WPML's language filter hides the new item from the re-read.

  • Chore

    Added a real-WPML contract test and a guard that fails the build if a read-only ability ever starts writing.

1.3.1

2 features3 fixes1 chore
  • Feature

    WooCommerce abilities require WooCommerce 9.1 or newer now; below that they simply do not register, with a clear reason on the Integrations screen rather than a fatal error.

  • Feature

    The activity log attributes each call to its OAuth client, shows a result count for list and read calls, and leaves a marker when the log is cleared.

  • Fix

    A run of WooCommerce fixes: list-customers can filter by role so a customer on another role stays visible, order-note authorship is detected correctly, a payment gateway's real display order and saved values are reported, the refund executor no longer crashes on a gateway with no tax method, and product-attribute updates work across WooCommerce versions.

  • Fix

    SEO and content fixes: the Rank Math and AIOSEO head and write-verification paths return a clear error or accept a benign normalization instead of a false failure, a term's parent must belong to the same taxonomy, count-media ignores the trash, upload-media fails clearly without the fileinfo extension, and update-site-settings reports failure when WordPress silently reverts a value.

  • Fix

    Admin and OAuth fixes: abilities from an inactive integration survive a form save, the agent-user picker finds users past the first page, a filtered-out row is actually hidden, denied OAuth bearer attempts are logged, and the consent screen and code redirect are never cached.

  • Chore

    Added a real-vendor contract test suite that runs against pinned WooCommerce, Rank Math, AIOSEO, and ACF code to catch API-shape regressions before release, and stopped shipping the mcp-adapter's Node package metadata in the zip.

1.3.0

Read the release post
1 feature4 fixes
  • Feature

    The OAuth consent screen warns when the account approving a connection is an administrator, the settings screen warns before a REST API lockdown would cut off your OAuth connections, and the Abilities Bridge directory shows each bridged ability's effective permission.

  • Fix

    New installs ship with OAuth off by default now, while sites that already had it on keep it, and a consent-grant phishing path that could get an administrator to approve a malicious client is closed.

  • Fix

    Hardened governance: the MCP capability gate verifies the running adapter still applies its filter rather than trusting a text match, update-user requires edit_users, and a bridged ability with no destructive annotation is treated as destructive rather than assumed safe.

  • Fix

    WooCommerce reads that failed on every real store are fixed: customer listing (it called a function WooCommerce does not have), empty shipping zones, ignored order paging on legacy storage, and product attributes dropped on create and wiped on update.

  • Fix

    SEO and content fixes: Yoast's robots_noindex was inverted so an agent wrote the opposite of what it asked, Rank Math and AIOSEO social images render now because the plugin writes the attachment id, ACF numeric and boolean writes stopped reporting a false failure, a partial menu-item update no longer wipes untouched fields, and the page-publish check recognises custom public statuses.

1.2.1

2 chores

If you are upgrading: Documentation and links only. The plugin's website link now points to agentabilitieswp.com, and the supported-client list is up to date for ChatGPT, Claude, and Manus. No code changes.

  • Chore

    The plugin's website link points to agentabilitieswp.com now instead of the GitHub repository.

  • Chore

    Refreshed the documentation so the supported-client list matches what works: ChatGPT, Claude (the claude.ai web app and Claude Desktop), and Manus connect by URL over OAuth, while Claude Code, Cursor, VS Code, Windsurf, and Gemini CLI connect from your own machine.

1.2.0

1 feature3 fixes1 chore

If you are upgrading: Fixes a critical crash that could white-screen logged-out visitors when another plugin resolves the current user early in the load, and tightens OAuth token scoping. Also adds ChatGPT support and fixes the Settings save.

  • Feature

    Added ChatGPT as a connection option and a single Claude entry that covers both the web app and Claude Desktop; hosted apps connect by URL over OAuth, so they no longer show the application-password steps, and Manus connects the same way.

  • Fix

    Logged-out visitors could see "There has been a critical error" on every page when another active plugin checked the current user very early in the load (The Events Calendar is one example); the plugin waits until it has finished loading now.

  • Fix

    The Settings screen saves the Enable OAuth, Dynamic Client Registration, and strict block-validation switches correctly now (they were being switched off on save), and there is no more white screen when the standalone MCP Adapter plugin is active alongside this one.

  • Fix

    Tightened OAuth token scoping so an MCP access token can only authenticate the MCP endpoint and never another REST route, closed a rare condition that could exhaust memory during connection setup, and made publishing always require publish permission, including for custom public post statuses. Valid Cover and Media & Text blocks are no longer flagged as invalid.

  • Chore

    Tightened the connection-snippet helpers.

1.1.1

3 changes

If you are upgrading: Agent-written pages, posts, and templates no longer risk showing invalid content in the block editor. An optional strict mode under Safety controls can reject bad block markup outright.

  • •

    AI agents that write pages, posts, or templates are now steered to keep block styling in the block attributes instead of inline CSS, the mistake that made blocks show "unexpected or invalid content" in the editor.

  • •

    Block markup is checked before it is saved, and anything that would break in the editor is flagged back to the agent to fix on its next try.

  • •

    A new strict option under Safety controls rejects a write outright when its block markup would be invalid, off by default so existing sites are unchanged.

1.1.0

6 changes

If you are upgrading: Bridge abilities from your other plugins as governed MCP tools, all opt-in and off by default, plus refreshed branding.

  • •

    Bridge abilities from your other plugins: any active plugin that registers abilities through the WordPress Abilities API can now be exposed as a governed MCP tool, opt-in per ability and off by default, on a new "Abilities from other plugins" screen grouped by the source plugin.

  • •

    Turn a whole plugin's abilities on or off at once, with each source plugin's name shown in title case.

  • •

    Bridged abilities run under the full governance layer: a capability re-check on every call, rate limiting, and the same audit log as the built-in catalog.

  • •

    Added a WP-CLI catalog exporter, wp aafm catalog export, that lists a site's discoverable abilities as JSON.

  • •

    Refreshed the branding with a new icon, banner, and a matching admin menu mark.

  • •

    Added a WordPress Playground blueprint so the plugin page can offer a one-click live preview.

1.0.0

8 changes

If you are upgrading: First public release.

  • •

    Initial release.

  • •

    153 governed abilities: 83 across WordPress core (reads and guarded writes for posts, pages, terms, comments, media, users, post meta, revisions, blocks, templates, and site structure, plus a search that spans every post type) and 70 from auto-detected integrations for WooCommerce, Advanced Custom Fields, Yoast, Rank Math, and All in One SEO.

  • •

    Built on the WordPress Abilities API and the official MCP Adapter, with no custom transport.

  • •

    Connect over OAuth in the browser, or with a least-privilege Application Password user.

  • •

    Everything off by default, with two-layer capability gating and per-connection tool filtering.

  • •

    Optional safety controls: rate limit, IP allowlist, force-to-draft, and title-length cap.

  • •

    Audit log that records every call, denied attempts included.

  • •

    Guided connection screen with endpoint diagnostics.

Every entry on this page is copied word for word from the Changelog section of the plugin's own readme.txt, and the dates are the release tags in the source repository. Nothing here is a summary. If you would rather read it at the source, the plugin page on WordPress.org and the repository both carry the same history.