Secure MCP Server for WordPress
Release Notes

Added block editor editing: 11 abilities to list, find and read the blocks of any page or post, change one block’s text or settings, and insert, replace, move, duplicate and delete blocks, including patterns and synced patterns. Every other block stays exactly as it was, blocks are only placed where they are allowed, and every change saves a revision.

Added menus and navigation: 16 abilities to create, rename and delete menus, add, update, remove and reorder menu items, assign menu locations, and edit block-theme Navigation menus, with undo.

Added widgets and sidebars: 8 abilities to list widget areas and widgets, and add, update, move and delete widgets, including block widgets.

Added shareable preview links: an expiring link lets anyone view a draft without signing in, and can be cancelled at any time.

Added a site overview ability that tells the AI how the site is built (theme, page builder, plugins in use, caches) and which tools it may use.

Page caches, host caches and CDNs are now cleared automatically after every AI change, so changes show straight away.

To keep busy sites fast, the whole page cache is cleared at most once a minute; a changed page is always cleared straight away.

When a tool exists but is not switched on for a user’s role, the AI is now told so, and how to turn it on, instead of “unknown tool”.

The AI is now told when page content it writes would be saved as one Classic block, and how to write it as editable blocks instead.

Fixed REST routes that plugins such as Media File Renamer only offer to signed-in users not being available to AI clients.

Fixed write requests made through the REST API arriving without data in plugins that read the request body as JSON.

REST routes added by another plugin are now picked up without reactivating it, and a route that is not available to the current user is explained instead of returning “No route was found”.

Fixed Kadence headings and buttons failing to insert into an empty column.

Fixed tools that take no inputs failing with “input is not of type object” when an AI client connected directly leaves the input out.

Minor bug fixes in the WordPress MCP Server.

Fixed AI clients being disconnected when a token refresh was interrupted by a timeout or restart. A retried refresh now succeeds instead of forcing a reconnect.

Fixed AI client replies breaking when another plugin prints PHP notices or warnings during MCP and OAuth requests.

The Debug Log now always records failures, even while capture is off, without usernames or IP addresses. Entries carry the gateway’s request ID so a failed call can be traced end to end.

AI clients now get a log reference instead of a broken reply when a tool crashes.

Troubleshooting: a gateway check that could not be completed is now shown as inconclusive instead of a failure on your site.

Minor bug fixes in the WordPress MCP Server.

Fixed AI clients failing to connect, or not seeing a new agent, on sites using LiteSpeed Cache or another page cache. MCP and OAuth responses are no longer cached.

Fixed AI edits removing forms, scripts and styles and dropping backslashes, which broke pages with custom code such as calculators. AI edits to pages, posts, custom content, Elementor, Kadence, Fluent Forms messages and media now follow the same rules as editing by hand: anyone allowed to add HTML there keeps it exactly as written, and markup a user is not allowed to add is refused with a reason instead of being silently removed.

Fixed Kadence block edits damaging links and settings in other blocks on the same page. Pages already affected can be restored from WordPress revisions.

Fixed the Kadence duplicate and delete abilities reporting an error even though the change was made.

Minor bug fixes in the WordPress MCP Server.

Improved the Troubleshooting page to show only likely connection problems.

Minor bug fixes in the WordPress MCP Server.

Added support for REST APIs in the WordPress MCP Server.

Added a Troubleshooting page.

Improved MCP connection reliability with AI providers.

Minor bug fixes in the WordPress MCP Server.

Added theme editing for block themes: templates, template parts, global styles, style variations and patterns.

Added theme file editing: read, search and change theme code in a private draft.

Every theme change now waits in a draft you can preview before it goes live. Before publishing, the site is checked with the draft applied, publishing backs up first, and every change is rolled back automatically if the site breaks.

AI assistants are now told which inputs each tool requires and why a change was refused, including the closest matching text when wording is not found.

Minor bug fixes in the WordPress MCP Server.

Added surgical content editing: change part of the text in a post, a custom field or a setting without rewriting the whole thing.

Added 8 maintenance abilities covering scheduled events, permalinks, caches, and the site error log.

Added Fluent Forms support: 14 abilities for forms, fields, confirmation messages, email notifications and submissions.

Minor bug fixes in the WordPress MCP Server.

Added 34 site administration abilities covering site settings, plugin management, theme details, and update and Site Health checks.

Minor bug fixes in the WordPress MCP Server.

Added SEO post meta update ability for Rank Math.

Added product sale schedule date fields to the WooCommerce abilities.

Security and performance improvements to the MCP connection flow.

Fixed: the health endpoint is no longer cacheable. Page and edge caches (e.g. LiteSpeed, Cloudflare) could previously serve a stale “no agent” state, causing a connected client to report “No agent configured” even after an agent was enabled.

Minor bug fixes in the WordPress MCP Server.

Debug logging framework: a built-in diagnostic log for MCP and OAuth activity.

Minor bug fixes.

Minor bug fixes.

Elementor integration: 10 abilities that let a connected AI client read and edit pages, posts and custom post types built with Elementor. Read a layout’s elements with their text, images and links, filter by widget type or by the text they contain, and render the result to check a change rather than assume it.

Edit Elementor content in place: change the text, image or link of a single element without touching the design. Reading a layout now also reports which text widget holds the article body, so an AI client editing an article no longer has to guess between a caption and the prose.

Edit selected Elementor styling: text and background colour, font size, weight and family, line height, letter spacing, letter casing, alignment, padding and margin — with separate values for tablet or mobile. Limited to those properties on purpose, so it cannot disturb the rest of a design.

Custom post type support: 19 abilities for any registered custom post type, whether it came from CPT UI, JetEngine, ACF or code. Read and edit items and their custom fields, assign taxonomy terms, set the featured image, change status, duplicate, trash and restore. Fields managed by another plugin are reported as read-only rather than being corrupted, and a read now tells you exactly why a field cannot be written.

Media uploads: add files to the media library from a public URL or from supplied file contents, then use the returned attachment ID to set a featured image or fill an image widget. The real file type is checked against the contents rather than the extension, and URL fetches are restricted to public web addresses so the site cannot be used to reach services on its own network.

Duplication now carries a page’s whole appearance — layout, theme settings, taxonomies and featured image — and clears the copy’s canonical URL, which would otherwise tell search engines the original is the real page and keep the duplicate out of search results.

More Yoast fields available to AI clients: breadcrumb title, canonical URL, SEO title, focus keyphrase, social and X/Twitter cards, advanced robots directives, cornerstone content and schema types. Reading a post’s SEO now returns every field that can be written, including the title with its template variables resolved.

Slugs can now be edited on posts, pages and custom post types. Renaming something already published warns that the address has changed, and says plainly when WordPress will not redirect the old one.

Minor bug fixes.

Kadence integration: 17 abilities that let a connected AI client read, edit, and build pages made with Kadence Blocks. Read a page’s full nested block structure by ID or title, get a single block’s settings, and search blocks by type or by the text they contain.

Edit Kadence blocks in place: update text across 16 fields in 9 block types (headings, buttons, info boxes, testimonials, icon lists, image captions, accordion titles), update styling and responsive attributes across all 59 Kadence block types with desktop/tablet/mobile values, and duplicate or delete a block. Duplicates get freshly generated block IDs so styling never collides.

Build layouts: insert rows, columns, headings, images (from the media library by attachment ID), and buttons; create a new draft page pre-built with a row and columns; or build a nested row-and-column structure in a single request.

New abilities to read and set Kadence’s per-page theme layout options.

Kadence edits rewrite only the block you target and leave every other byte of the page identical, so layouts authored in the Kadence editor are preserved. Writes accept an optional page lock so an edit is refused if the page changed since it was last read, and each write returns the previous and new value for verification.

Inserted Kadence markup is generated to match what the Kadence editor itself saves, including the block version marker, so inserted rows and columns get Kadence’s generated CSS and sit side by side as expected. Block types whose markup cannot be reproduced reliably are declined with a message pointing to the duplicate-and-edit route instead of writing markup that would break the page.

Minor bug fixes.

Added a warning, shown across the plugin, when the site is only reachable on localhost — AI clients running elsewhere can’t connect to it until it’s made publicly reachable.

ChatGPT is now shown first when connecting a client, with a direct link to the official plugin listing and clearer, more accurate setup steps.

Refreshed the sign-in (OAuth authorization) screen to match the rest of the plugin’s design.

Fixed the connection dialogs occasionally rendering behind the WordPress admin toolbar.

Fixed a brief flicker on the dashboard when it first loads.

Onboarding UI improvements.

Minor bug fixes.

Added a guided onboarding checklist for new installs: register an agent, add the MCP URL to your AI client, and approve the connection, shown on the dashboard until setup is complete.

Redesigned the role & ability editor as a matrix: abilities are grouped by resource down the left, with every role shown as its own column, so you can compare what each role can do without switching roles one at a time. Includes quick select all / clear controls for an entire role or an entire resource category.

New ability — “Update Page”: edits the title and/or content of an existing page.

Added a bundled abilities library: 260+ ready-to-use, security-reviewed WordPress abilities exposed as MCP tools out of the box. Core content (posts, pages, categories, tags, media, revisions), users & roles, and comments are always available; ability sets for WooCommerce, Advanced Custom Fields, Yoast SEO, Contact Form 7 (with Flamingo), WPForms, and Gravity Forms activate automatically when those plugins are present.

Every bundled ability is capability-gated, carries explicit MCP tool annotations (read-only / destructive / idempotent / open-world), declares full input/output JSON schemas, and is reachable only through the governed MCP endpoint — never the public REST API.

Added a “Test Connection” check that confirms an AI client will actually be able to reach and sign in to your site, run from both your server and an outside vantage so it catches firewall, CDN, and reverse-proxy issues a same-server check would miss. Available on the Connect to AI page and beside Register Agent on the AI Agents screen.

Added a Troubleshooting guide, always available from the toolbar, that explains the common reasons an AI client can’t connect and gives copy-paste Apache/Nginx fixes for each. When a connection test finds an issue, the most likely cause is highlighted automatically.

Security hardening in the bundled abilities: reserved user-meta keys (capabilities, role level, session tokens) can never be read or written through an ability; role grants are limited to roles whose capabilities the caller already holds; and CSV entry exports are neutralized against spreadsheet formula injection.

Reliability on CDN/cached hosts: the OAuth and MCP endpoints (discovery, registration, the MCP transport, and the authentication challenge) now send “Cache-Control: no-store”, so an edge cache or CDN — such as Pantheon’s Varnish, Cloudflare, WP Engine, or Kinsta — can no longer cache and misdeliver these per-request responses, which could otherwise intermittently break AI-client connections.

Fixed the role & ability editor incorrectly flagging object-level abilities (those gated by per-object capabilities such as editing or deleting a specific post or page) as capability conflicts for every role, including Administrator. These capabilities are resolved per request against the target object, so they are no longer shown as conflicts; the runtime permission check is unchanged and was always correct.

Minor fixes and reliability improvements.

Added an execution activity log: a full audit trail of every tool call, filterable by agent, status, or time range, with per-event detail including latency and error context.

Added an activity timeline on the agent overview: the last 5 executions appear inline on each NHI’s overview tab.

Redesigned the dashboard with four focused metrics — Active Agents, Total Executions, Success Rate, and Average Latency — for an at-a-glance view of MCP server health.

Denied and unknown-tool calls are now correctly attributed to the responsible NHI, so the audit log is never missing an agent name.

Clearer role & ability editor: a single Select all / Clear all control (instead of separate All and None buttons), role names shown in each NHI’s summary, and a smoother role & ability layout.

Refined the admin/member view switcher to a clearer segmented control.

Fixed the support form’s country picker so it no longer shifts the page or scrolls unexpectedly when opened.

General UI polish across the NHI Registry and connection screens.

Added a “My AI Access” member view so any logged-in user can see the tools available to their role, with an admin/member view switcher for administrators.

Added a Settings link to the plugin’s row on the Plugins page.

NHI Registry is now role-based: grant abilities to each WordPress role, with live capability-conflict detection. A request receives the abilities its user’s role(s) are granted across all enabled NHIs.

Rebuilt NHI create/edit as full-screen pages (guided create wizard ending in a connection step); removed the cramped modal editor.

Existing NHIs are migrated automatically and keep working; review each one to scope its abilities per role.

Support and deactivation-feedback emails now include the customer’s email address in the subject line.

Added a floating Contact Support button, available throughout the admin app.

Added a Setup Guide link in the toolbar for quick access to the connection guide.

Redesigned the deactivation feedback prompt with a clearer, on-brand layout, guided reason selection, and the option to get help instead of deactivating.

Added NHI Registry: a new admin screen to view and manage all non-human identity (AI client) registrations, including OAuth client details and token status.

Added per-ability toggle to enable or disable individual abilities from being exposed as MCP tools.

Revamped the plugin UI.

Added in-plugin support form and deactivation feedback modal.

Added a remote MCP server endpoint that exposes registered abilities as MCP tools.

Added a self-hosted OAuth 2.1 authorization server with Dynamic Client Registration, PKCE, and discovery metadata so ChatGPT and Claude can connect.

Initial release: read-only viewer for abilities registered through the WordPress Abilities API.