WPVibe – MCP Server for WordPress, works with Claude, ChatGPT & other AI MCP agents

Changelog

1.22.0

• Feature: Your AI can now make several changes to one post, setting or field in a single edit, saved together as one revision. If any change does not match, nothing is saved and your AI is told which one failed.
• Feature: Elementor’s own AI abilities (Elementor 4.3 and later) now work through WPVibe even when Elementor’s MCP setting is off. The setting stays as you left it for everything else, including Elementor’s own MCP connection.
• Feature: Before saving an Elementor page, WPVibe now checks every element with Elementor’s own rules: unique ids, widgets that are installed and active, and Elementor 4 settings in the right shape. A page with problems is not saved, and your AI is told which element to fix. Your AI can also check a page without saving it.
• Feature: WPVibe now keeps your site’s last few PHP fatal errors for 7 days, with the plugin or theme that caused them, so WPVibe can tell why a site fails even when it cannot sign in. It keeps PHP’s own error text, file names inside WordPress, memory use and your WordPress, PHP and active plugin versions: no stack traces, values or request data. The connection check on the WPVibe page shows the latest one.
• Fix: WPVibe connects again on sites running WP 2FA 4.3.0, which blocked Application Password logins for every user with two-factor set up. Only WPVibe’s own password, on a WPVibe request over HTTPS, gets through. WP 2FA’s lockout and every other password stay as they were.
• Fix: When WPVibe’s draft theme record holds a value no draft action accepts, such as “none”, every draft action used to fail. Deleting the draft now clears that record, and only when nothing exists at that path, so no files are deleted.
• Security: Theme delete and update, and their approval preview, now refuse a theme name that is a path (a slash, a backslash, “.” or “..”). Until now an approved theme delete given such a path could remove a folder outside your themes folder.
• Hardening: A search-replace that runs without an approval showing that exact change, such as a fleet run, now leaves out tables that hold code or keys (Code Snippets, Header Footer Code Manager, Wow Coder, WPVibe’s own records and WooCommerce API keys), and never changes a post’s type or a term’s taxonomy. A search-replace you approved still covers them.

1.21.7

• Fix: When your AI tries to delete the folder of a WPVibe draft theme, it is now refused and pointed to discarding the draft instead, so WPVibe is never left pointing at a draft that no longer exists. A publish that moved the draft live but could not restore its theme name no longer leaves that stale draft record behind either.
• Fix: With “Allow for WPVibe” on, the WPVibe page now explains that while a security plugin turns Application Passwords off, only a password WPVibe created gets through. If your account has none yet, it says so and how to connect.
• Fix: On sites where another plugin turns on strict database error reporting, a database query from your AI with a mistake in it now returns the SQL error instead of WordPress’s critical error page, and no longer leaves a read-only transaction or time limit open.

1.21.6

• Fix: wp-admin no longer offers Activate or Live Preview on a WPVibe draft theme, which locked every draft change once active. A switch to a draft from anywhere else puts the site straight back on its theme and says how to preview or publish the draft instead.
• Fix: Asking your AI to search or edit a post that does not exist now says the post does not exist, instead of reporting a missing permission and asking you to reconnect.
• Fix: When Approve is refused because the request is not a plain browser login, the message now names the cause (an Application Password, a server password such as HTTP Basic Auth, or an extra header) and how to get past it.
• Fix: On white-labelled sites with “Dangerously bypass approvals” on, the warning banner now turns it off in place. Your AI can turn the setting off for you too, but never on.
• Fix: When your AI cannot make a draft copy of your theme, it now says why and what to do: a theme the host links in from elsewhere (as on WordPress.com), a link inside the theme, a themes folder WordPress cannot write to, or a draft record the database did not keep. It used to say only that the existing draft was preserved.
• Fix: Connecting a site now tells WPVibe which way WordPress created the connection’s password, to help trace connections that fail.
• Hardening: Before WPVibe first changes a post’s title or content, WordPress keeps a revision of the original, so the first AI edit can be undone. When revisions are off for that post, your AI is told the change cannot be undone.

1.21.5

• Fix: Approve now connects on sites whose REST API address answers “not found”. It retries through the ?rest_route= address, which those sites still answer, and the help notice names the address it tried.
• Fix: The connection check no longer fails on sites running LiteSpeed Cache, which could serve an earlier check’s answer. WPVibe now tells LiteSpeed Cache not to cache it.
• Hardening: A search-replace that runs without an approval showing that exact change, such as a fleet run, now leaves WPCode and Elementor code snippets unchanged and says so. A search-replace you approved still changes them.

1.21.4

• Fix: SeedProd pages your AI saves compile again on sites where other plugins run background tasks, such as Action Scheduler, while the page is saved. The builder sign-in now refuses those requests instead of signing itself out, so the save goes through.
• Fix: WPVibe’s update notices show in wp-admin even when WPVibe is hidden from admins.
• Hardening: The draft theme preview loads Tailwind from the plugin instead of a CDN.
• Security: The readme now explains that requests to your site may pass through WPVibe’s relay servers, and how to report a security issue (security@wpvibe.ai).

1.21.3

• Feature: WPVibe now finds and runs abilities that a plugin offers to AI agents only (marked for MCP but hidden from the REST API), such as those in Fluent Forms, Meta Box, Premium Addons for Elementor and PixelYourSite. Each ability’s own permission check still decides who can run it.
• Fix: Publishing a draft theme no longer rolls back when a maintenance or coming-soon page is on (SeedProd, LightStart, CMP or Maintenance). The publish is kept, and WPVibe tells you to view the site logged in before you turn maintenance off. A real error page still rolls back as before.
• Security: The SeedProd builder sign-in now also limits Super Admins on multisite, accepts only the exact fields the builder sends on each call, refuses file uploads, and views the front end signed out.

1.21.2

• Security: The one-time sign-in WPVibe uses to save a SeedProd page in the builder now only reaches that page’s builder. It can no longer open other admin screens, upload plugins or themes, add users or change settings, it ends after 10 minutes instead of 2 days, and any request outside the builder signs it out.
• Security: On multisite, a site administrator who is not a Super Admin now only reads their own site: database reads, user lookups and network transients stay on that site, and search and replace skips network and other sites’ tables.
• Security: Search and replace now escapes table and column names when it writes, and skips any table whose name is not a plain identifier.
• Hardening: Reading wp-config constants now uses an allowlist of diagnostic settings (paths, debug, cache, memory, multisite), so a credential stored under an unusual name is never returned.
• Hardening: WPVibe only takes back a draft theme folder it created itself. A folder that merely ends in -wpvibe-draft is left alone, including on uninstall.

1.21.1

• Security: The approval log on your site no longer keeps passwords and other secret values from the commands you approved, such as post passwords and the values in a database query. Before, only user passwords were hidden. Approved commands are now logged by their shape.
• Feature: Your AI can read large plugin and theme files a section at a time, up to 1 MB. Before, any source file in wp-content over 64 KB was refused, even for a few lines. The whole file is still checked for secrets, and they are masked before any lines are returned.
• Feature: Beaver Builder pages can be edited one part at a time. Your AI sends only the rows and modules it changed, so it no longer has to pass your whole layout, including form keys such as reCAPTCHA secrets, back through the chat.
• Feature: Your AI can list a post’s categories and tags (wp post term list), look up a single category or tag (wp term get), and read and change term meta (wp term meta).
• Fix: Reading a page’s HTML works on WordPress sites installed in a subfolder (for example example.com/blog). It used to fetch a “page not found” page instead and report success.
• Fix: Beaver Builder saves refuse a module whose internal id does not match its key, which Beaver would otherwise drop or rename while reporting success.

1.21.0

• Security: Pending plugin, theme and WordPress updates can no longer be pointed at a different download through an option change. WordPress’s update records are now read-only to your AI.
• Security: The list of user roles is now protected on every site, including sites with a custom database table prefix and every multisite subsite.
• Security: The draft theme file tools only ever work inside a draft theme WPVibe created, never in your live theme or its parent theme.
• Security: The SeedProd builder sign-in that WPVibe opens to compile your pages can no longer switch on “Dangerously bypass approvals”.
• Security: The approval preview for a database query no longer runs statements the query itself would refuse, such as file reads or queries on protected tables.
• Security: With “Allow for WPVibe” on behind a security plugin that blocks application passwords, only the WPVibe password of an account connected to WPVibe gets through. Other accounts, and the same account’s other application passwords, stay blocked.
• Fix: Draft theme editing works on Windows hosts and local Windows installs (for example Local). Reading, editing and outlining existing files no longer fail with a path error.
• Fix: Your AI can no longer delete the WordPress user WPVibe is connected as, which used to break the connection until you reconnected by hand. It is told to reconnect as another user first.
• Fix: Post meta and user meta writes follow WP-CLI’s –format option. JSON text stored by plugins such as SeedProd and Elementor stays text instead of being turned into an array, and –format=json or –format=plaintext picks either one.
• Fix: User meta saved through WPVibe keeps escaped quotes, so JSON text in user meta stays valid.
• Improvement: option pluck supports –format=json, so your AI can tell true, 1 and “1” apart. Undoing an Astra setting change uses it.

1.20.5

• Security: User meta changes that need your approval can no longer be slipped past it with a key the database treats as the same as a protected one (for example a different letter case, an accent or a hidden character). Keys like that are refused, and a write is refused whenever WPVibe cannot confirm which stored key it would touch. Thanks to Mahesh Bohara (https://github.com/maheshbohara) for reporting it.
• Improvement: WPVibe’s own updates are safer. An update waits while WordPress is running its own background updates, a failed or rolled-back update is always reported as failed (with the reason when the site could not reach itself to check the new version), maintenance mode is cleared if an update is interrupted, and WPVibe records a note whenever it had to switch itself back on.
• Fix: Approved database writes no longer fail with “Multiple SQL statements” when a quoted value contains a semicolon, such as serialized data or CSS. Anything the check cannot read with certainty is still refused.
• Fix: When another plugin or theme crashes while WPVibe saves an edit, administrators see the PHP error with its file, line and the plugin or theme it came from, instead of WordPress’s bare “critical error”. Your AI is told to check whether the change was saved rather than send the same edit again.
• Fix: An upload your site refuses because of its file type (for example an SVG blocked by an SVG plugin) is reported as an unsupported file type with the site’s own message, not as a disk error, so your AI stops retrying it.
• Fix: Menu changes no longer fail on sites whose plugins look up the admin screen when a menu is saved (for example Ocean Extra).
• Fix: The plugin page now names the right Wordfence screen (All Options, Brute Force Protection) for the setting that turns off application passwords.
• Fix: Astra child themes are recognized in the dashboard widget and when WPVibe picks the right Astra tools.
• Improvement: When a site refuses WPVibe’s sign-in, the connection check reports a few more facts about why (whether the server passed the credentials through and whether WordPress’s application password check ran), never the credentials themselves.

1.20.4

• Fix: When WPVibe updates itself, it stays switched on. Before, an update WPVibe ran on its own (from your AI or a fleet job) could leave the plugin deactivated until someone turned it back on. The update now runs the way WordPress’s own background updates do, so WordPress also checks the new version for errors and restores the previous one if it would break the site.
• Improvement: Beaver Builder pages save on Beaver Builder versions before 2.6. When a save hits a PHP error, administrators see the error with its file and line, and a page the failed save created is removed.
• Feature: Bricks header and footer templates built through WPVibe now show on the site. Before, they were saved where Bricks does not read them.
• Improvement: Other plugins can log WPVibe’s activity: the new wpvibe_operation_executed action fires each time an approved operation runs, with the command and the preview you approved.
• Fix: WPVibe’s SeedProd-only login route no longer appears in the plugin’s route list, so AI agents stop calling it on sites without SeedProd.
• Improvement: WPVibe can turn off a WPCode snippet it created, with no approval needed, because turning it off loses nothing and you can turn it back on in WPCode. It can also delete one of its own snippets after you approve it on the approval page (or at once, if you turned on “Dangerously bypass approvals”). A deleted snippet goes to the trash in WPCode, where you can restore it. WPVibe never turns off or deletes snippets you created, and it does not delete one of its own snippets after you changed its code. Turning a snippet off also stops it running when it was moved to the trash while still on, and clears the page caches WPVibe supports.
• Fix: Draft theme previews work on sites that use the SeedProd Website Builder. Before, the preview showed the live SeedProd site instead of the draft. The preview and the publish result say that the live site keeps showing the SeedProd site until the Website Builder is turned off.
• Fix: Preview pages tell hosts, caching plugins and CDNs not to cache them, so a page cache no longer serves a stale preview after an edit.

1.20.3

• Fix: Approved database writes that are long (over about 8 KB) and wrapped in double quotes no longer fail with a syntax error on some hosts.
• Fix: File listings with a name pattern such as *.php now find matching files in every folder, and a pattern used with a folder now matches inside that folder. Before, *.php found only top-level files, and with a folder it found nothing.
• Fix: Saved Site Editor changes on the live theme no longer override a published draft theme by default. Publishing sets aside the live theme’s saved global styles, and its saved templates and template parts that the draft also has. Set-aside changes are kept and can be brought back, and you can ask to keep them instead. Changes saved in the Site Editor during the preview now go live with the theme, unless you keep a live change with the same name. Deleting a draft sets its saved changes aside too.
• Feature: The preview and the publish result warn when the theme’s folder name belongs to a theme on WordPress.org, because a WordPress.org update could replace a custom theme. Adding “Update URI: false” to style.css stops this.

1.20.2

• Fix: Live reload puts much less load on your server. It checks for changes every five seconds instead of every two and a half. When a check times out, every open tab of the site stops checking, so it cannot tie up the server’s PHP workers; reload the page after five minutes to turn live reload back on.
• Fix: When an approved database change fails, the Approval Log now records the error message instead of an empty result, and the change is labelled as a write.

1.20.1

• Improvement: Claude users can add WPVibe from Claude’s connectors directory. The “Add to Claude” button on the WPVibe settings page and a new link in the dashboard widget open the listing. The server address is still there for Claude Code, Cursor and other clients.
• Hardening: Turning on white label mode always asks for approval, even when “Dangerously bypass approvals” is on. White label hides the Approval Log, so a person confirms it each time. Sites that already use white label are not affected.

1.20.0

• Feature: Dangerously bypass approvals. A new per-site checkbox on the WPVibe settings page in wp-admin, off by default. When it’s on, WPVibe asks for no approvals on that site: deletes, SQL, WP-CLI, REST writes, abilities and fleet jobs run right away. Only a logged-in administrator can turn it on or off, from wp-admin. WPVibe’s tools can’t change it. A red banner shows on every admin page while it’s on, and turning it on or off, plus every operation that ran without approval, is recorded in the Approval Log. Code snippets are still saved disabled, so enabling one stays a click in wp-admin.
• Improvement: Fewer SQL prompts. Approving a database row change (UPDATE, INSERT, DELETE or REPLACE) can now cover the rest of your session on that site, for 30 minutes or 25 statements. Schema changes, code snippet tables, WPVibe’s own tables and WooCommerce API keys still ask every time, and remembering stays off on multisite and on databases with triggers, views, stored routines or custom database drop-ins.
• Security: Remembered SQL writes run inside a transaction, and any change to code snippet storage rolls the write back. If the database connection drops mid-write, WPVibe reports an error instead of replaying the statement.
• Security: Database reads now run inside a read-only transaction, so a query that looks like a read can never change data. Reads with unusual quoting that used to be refused now run.
• Fix: Approving a connection no longer fails on sites whose server labels REST answers as HTML. WordPress used to hand back an unreadable password, and the connect link failed with a misleading hint.
• Improvement: The Approval Log header now says it lists approved and bypassed operations.

1.19.2

• Security: WPCode snippets and their storage (the active-snippet cache, the site-wide header and footer scripts, snippet posts) can only change through WPVibe’s code snippet flow, which saves new code disabled for you to review. Content edits and page builder saves that would reach them are refused.
• Security: Raw SQL can no longer write to the users, user meta or options tables, even with approval. WPVibe points the AI to the matching WordPress command instead, which runs WordPress’s own checks.
• Improvement: Fewer approval prompts. Clearing expired transients runs without one, and snippet saves that land disabled no longer ask, because enabling a snippet in wp-admin is the real approval.
• Improvement: A domain migration with search-replace can change the site and home addresses again after approval, with a clear warning. Other protected settings are skipped.
• Fix: WPVibe refuses to activate its own working draft of a theme, which would serve the site without its compiled styles. Uninstalling WPVibe keeps an active draft or backup theme in place.
• Fix: When another plugin or theme prints warnings or errors during a WPVibe request, the response stays clean, so a command that succeeded is no longer reported as a failure.

1.19.1

• Fix: Opening a draft theme preview can no longer crash wp-admin. On some hosts a preview could run out of memory on every admin page until the browser’s site data was cleared, and a broken draft theme could take the whole admin area down with it.
• Fix: Sites whose server garbles the standard login header now connect. WPVibe falls back to its own copy of the header when WordPress can’t read the standard one.
• Fix: Content search answers instead of refusing. Searching a field a post doesn’t have returns 0 matches, list-type fields are searched as text, and short field names like “title” and “content” work.
• Fix: Content edits inside page builder data (for example Elementor) and block settings now escape quotes and special characters safely instead of being refused.
• Improvement: WPVibe can read basic site settings such as the site address, home address, active theme and active plugins. Changing them is still blocked.
• Improvement: When a site has never saved an Application Password, WPVibe now says so, so the connection message can name the cause and offer a fresh connect link.
• Improvement: The connection check no longer claims WordPress accepted the Application Password when it only confirmed the header arrived.
• Improvement: The WPVibe admin page links to reviews on WordPress.org.

1.19.0

• Feature: WPVibe can now add SVG images to your Media Library and write SVG files in a draft theme. Every SVG is cleaned before it is saved, including for administrators: scripts, event handlers, links to other sites, embedded web pages and styles that could load or run anything are removed. A file that cannot be cleaned safely is refused, with a suggestion to use PNG or WebP instead.
• Improvement: SVG uploads are allowed for that one file only. Your site’s own upload settings do not change, so SVG uploads in wp-admin work exactly as before.
• Improvement: SVG images added to the Media Library get their width and height from the file, so they show at the right size in the editor and as featured images.

Older versions

WP.org caps the changelog at 5,000 words. For the full release history back to 1.0.0, see https://wpvibe.ai/changelog/