Title: WPVibe – WordPress MCP Server. Connect Claude, ChatGPT & Any AI Agent via MCP Author: SeedProd Published: 20 d'abril de 2026 Last modified: 6 d'octubre de 2026 --- Cerca extensions ![](https://ps.w.org/vibe-ai/assets/banner-772x250.png?rev=3511042) ![](https://ps.w.org/vibe-ai/assets/icon-256x256.gif?rev=3627788) # WPVibe – WordPress MCP Server. Connect Claude, ChatGPT & Any AI Agent via MCP Per [SeedProd](https://profiles.wordpress.org/seedprod/) [Baixa](https://downloads.wordpress.org/plugin/vibe-ai.1.20.3.zip) * [Detalls](https://ca.wordpress.org/plugins/vibe-ai/#description) * [Ressenyes](https://ca.wordpress.org/plugins/vibe-ai/#reviews) * [Instal·lació](https://ca.wordpress.org/plugins/vibe-ai/#installation) * [Desenvolupament](https://ca.wordpress.org/plugins/vibe-ai/#developers) [Suport](https://wordpress.org/support/plugin/vibe-ai/) ## Descripció Your WordPress site just became MCP-ready. [WPVibe](https://wpvibe.ai/?utm_source=wprepo&utm_medium=link&utm_campaign=liteplugin) is the Model Context Protocol server for WordPress, connecting your self-hosted site to any AI assistant or AI agent that speaks MCP: Claude, ChatGPT, Cursor, Windsurf, OpenCode, and more. No copy-pasting between tabs. No switching between your AI chat and wp-admin. Tell your AI what you want, and it happens on your live WordPress site. #### What People Are Saying * «New WordPress Plugin Safely And Easily Connects AI To Your Website» (Search Engine Journal, July 2026) * «The easiest setup of any AI product for WordPress, period. It’s so click-and- forget, and it absolutely smashes it for what you can do. It’s just mind-blowing.»( Jackson Whelan, WPTuts) * Thousands of WordPress sites connected and over a million WordPress operations performed since launch. #### The Model Context Protocol Server for WordPress WPVibe is a complete MCP server implementation for WordPress. The Model Context Protocol, introduced by Anthropic and now adopted across the AI industry, lets AI assistants discover and call tools on connected services through a standard interface. WPVibe packages every meaningful WordPress operation (content management, media uploads, theme file browsing, REST API access, and plugin abilities) as MCP tools your AI can call. You install this free WordPress plugin, connect your site once, and every MCP-compatible AI client becomes a WordPress co-pilot. The WPVibe WordPress MCP server handles authentication, encrypts credentials with AES-256-GCM, and relays your AI’s tool calls to the WordPress REST API. Your WordPress site, your data, your choice of AI. #### Connect Claude to WordPress WPVibe is the easiest way to connect Claude to WordPress. Use it with Claude Desktop, Claude on the web, or Claude Code in your terminal. Once connected, ask Claude to draft a blog post, schedule an article, reorganize categories, update site settings, or run any WordPress task through conversation. Claude sees your WordPress site through the MCP bridge and responds with direct action, not just suggestions. Connecting Claude to WordPress takes about 30 seconds. Install WPVibe, open the plugin admin, click to authorize, then add the MCP server URL to Claude’s connectors. From that moment, Claude can manage WordPress content, search WordPress files, upload images, and interact with any WordPress plugin that exposes the Abilities API. #### Connect ChatGPT to WordPress WPVibe is the ChatGPT WordPress plugin that actually connects the two systems instead of wrapping an API key. ChatGPT supports MCP servers directly in the web app and the desktop app, so once you add your WPVibe MCP server URL, ChatGPT can read and write to your WordPress site through ordinary conversation. Ask ChatGPT to turn a Google Doc into a WordPress blog post, find and tag every customer who downloaded a specific resource, update your About page in your own writing voice, or bulk-publish a content calendar. ChatGPT handles the language and strategy, WPVibe handles the WordPress REST API calls behind the scenes. WPVibe is also an official connector in the ChatGPT Apps directory. #### Connect Cursor, Windsurf, and Every MCP-Compatible AI Agent WPVibe is not locked to a single AI vendor. Cursor, Windsurf, OpenCode, Claude Code, ChatGPT, Claude, and any other AI agent that supports the Model Context Protocol can connect through the same MCP server URL. One WordPress MCP server, every AI assistant, no integration rewrite when you switch tools. For developers, this means Cursor can edit your WordPress theme files with context- aware suggestions, Claude Code can run WordPress tasks as part of an agentic workflow, and Windsurf can scaffold new WordPress templates. For content creators and agencies, this means whichever AI writes best for your brand can publish directly to your WordPress site through the WPVibe MCP bridge. #### AI-Powered WordPress Content Management via MCP Managing WordPress content through MCP has never been easier. Create blog posts, update pages, upload media, manage categories and tags, all through natural conversation with your AI assistant. Tell Claude to write a draft post about your latest product launch, ask ChatGPT to update your about page, or have Cursor reorganize your blog categories. Your AI handles the REST API calls, so you never touch wp-admin. WPVibe works with every AI client that supports the Model Context Protocol, giving you the freedom to use Claude Desktop, ChatGPT, Cursor, Windsurf, OpenCode, or any future MCP-compatible AI tool for WordPress management. #### WordPress Abilities API Support for MCP WordPress 6.9 introduced the Abilities API, a powerful way for plugins to declare self-describing operations that AI assistants can discover and execute. WPVibe fully supports this WordPress MCP integration. Your AI can discover what abilities your installed plugins expose, inspect their input schemas, and run them directly through natural conversation. This means AI-powered WordPress plugin management works automatically over MCP. If a plugin registers abilities (WPForms, SeedProd, and others are adopting this standard), your AI assistant can interact with it without any custom integration. The WordPress Abilities API and WPVibe together make every compatible plugin MCP- ready. #### WooCommerce, Elementor, Bricks, and Your Other Plugins WPVibe works with the plugins already running your site. For WooCommerce, your AI can review the store, manage products, and bulk-edit prices, stock, and descriptions through conversation, so updating fifty product pages no longer means fifty trips through wp-admin. Page builders get dedicated support. Elementor, Bricks, Breakdance, Beaver Builder, and Divi pages are written through each builder’s own save pipeline, so the result opens in the builder like a hand-built page. Built-in skills cover Gutenberg, Kadence, GeneratePress (including GP Premium Elements), and SeedProd. Other plugins work through their own REST APIs or the WordPress Abilities API, and custom fields (including ACF fields, which are post meta under the hood) are read and written correctly, including on custom post types. #### Safely Edit WordPress Theme Files WPVibe lets your MCP client browse and edit your WordPress theme files safely. Your AI can list files, search file contents, analyze code structure, and make edits through a draft theme workflow. The draft clones the active WordPress theme into a sandbox, makes changes there, and exposes a preview URL so you can see the results before going live. Your live WordPress site is never touched until you explicitly approve and publish. Every file operation runs through WordPress capability checks, a path sandbox scoped to the draft theme, and PHP syntax validation before save. You keep the safety of wp-admin’s file editing guardrails while giving your AI a real place to work. #### WordPress WP-CLI Commands over MCP Run WordPress administration commands through your MCP client. Activate plugins, switch themes, update options, flush caches, query the database, run serialized- data-aware search-replace with a dry run, and more, all via native PHP dispatch with a security-first command allowlist. Everything is emulated through PHP, so it works on shared hosting with no shell and no SSH. Your AI gets a productive WordPress admin surface without the risks of raw command execution. #### Approvals You Can See, and an Audit Log WPVibe does not open your site to the world. Access runs through WordPress’s own encrypted Application Passwords, revocable in one click. When your AI asks for something destructive (deleting a user, mutating the database, uninstalling a plugin), WPVibe pauses and shows an approval panel in the chat with the exact operation, a dry-run preview, and Approve or Decline buttons. Nothing irreversible happens without you. Every sensitive action is recorded in an append-only Approval Log in wp-admin, with the preview you saw and the result. Posts default to draft, deletes go to trash, and theme publishing keeps a backup so you can roll back. #### Smart MCP Notifications on Your WordPress Admin Every change your AI makes over MCP triggers a smart notification in your browser with a direct link to view or edit the updated content. The notification knows whether you are in the WordPress admin or on the frontend and adapts the link, so your workflow is never disrupted while your AI works in the background. #### One-Click WordPress MCP Authorization Connecting your WordPress site to an MCP server should take seconds. No application passwords typed by hand, no API keys copied between tabs: provide your site URL, click the authorization link that appears in your WordPress admin, and approve the connection. Credentials are encrypted with AES-256-GCM and stored securely on Cloudflare- hosted WPVibe servers. One click, done. #### WordPress MCP Server for Every Use Case Whether you are a blogger, a developer building WordPress themes, or an agency managing client sites, WPVibe works through whichever MCP client you already use. **Bloggers and Content Creators** write and publish posts, manage media, organize categories and tags, and update site settings through conversation with Claude, ChatGPT, or any MCP assistant. **WordPress Developers and Designers** browse and edit theme files with a safe draft- preview-publish workflow, or build classic themes from scratch, directly from Cursor, Claude Code, or your favorite MCP client. **Agencies and Site Managers** connect every client site and run updates across all of them from one panel, use the Abilities API to work with installed plugins, and turn on white label mode (free on every plan) so clients see a clean wp-admin while you manage the site through your AI. #### Full WPVibe MCP Server Feature List * One-click WordPress MCP server connection with AES-256 encrypted credential storage and OAuth magic-link sign-in (no passwords typed into chat) * AI content management: posts, pages, media, categories, and tags through conversation, with surgical find-and-replace edits in posts, meta, and options * Fleet updates: update plugins, themes, and WordPress core across every connected site from one panel, with a recheck before and a version verification after each update * WooCommerce management: review the store and bulk-edit products, prices, stock, and descriptions * Page builder integrations: Elementor, Bricks, Breakdance, Beaver Builder, and Divi through each builder’s own save pipeline * Human-in-the-loop approvals with a dry-run preview, plus an append-only Approval Log in wp-admin * Full WordPress REST API and Abilities API access as MCP tools, including custom post types and plugin routes * WP-CLI style commands (plugins, themes, users, comments, options, database) through native PHP dispatch, no shell required * Theme editing with a draft-preview-publish workflow, sandboxed file operations, PHP syntax validation, and a classic theme builder * Media uploads from URLs and Unsplash stock photo search * Works with Claude Desktop, Claude on the web, Claude Code, ChatGPT, Cursor, Windsurf, OpenCode, and any MCP-compatible AI agent * On-demand skills that teach your AI the right approach for each WordPress task, and smart live-reload notifications in wp-admin #### Third-Party Service This plugin connects to the WPVibe service at [wpvibe.ai](https://wpvibe.ai) to relay requests between your AI assistant and your WordPress site over the Model Context Protocol. When you connect your site, a WordPress application password is created and encrypted with AES-256-GCM on WPVibe servers hosted on Cloudflare. All communication between the plugin and the WPVibe MCP service occurs over HTTPS. No data is collected, tracked, or shared with third parties beyond what is necessary to relay your AI assistant’s MCP requests to your WordPress REST API. Your content stays on your WordPress server. On WPVibe’s own authorization page (the Approve screen an authorize link opens), if your site’s REST API answers the approval request with a firewall page or no response, the plugin reports that outcome to the WPVibe service (the HTTP status, whether the answer was a page or JSON, and the security vendor if recognised; never page content) so support can see what blocked the connection. Nothing is reported on a successful approval. * [Privacy Policy](https://wpvibe.ai/privacy/) #### Third-Party Libraries WPVibe bundles two third-party libraries: * **Alpine.js** v3.15.12, MIT License, [https://alpinejs.dev/](https://alpinejs.dev/), included at `starter-themes/classic/assets/js/alpine.min.js`. Used as the interactivity layer (modals, dropdowns, tabs, accordions, sliders) for AI-generated classic themes. Not loaded outside scaffolded themes. * **svg-sanitize** (enshrined/svg-sanitize) v1.0.0 by Daryll Doyle, GPL-2.0-or- later, [https://github.com/darylldoyle/svg-sanitizer](https://github.com/darylldoyle/svg-sanitizer), included at `third-party/svg-sanitize/` with its PHP namespace prefixed so it cannot clash with other plugins that bundle it, such as Safe SVG. Used to clean SVG files before WPVibe writes them to a draft theme or adds them to the Media Library. #### Built by SeedProd WPVibe is built by the team behind [SeedProd](https://www.seedprod.com/?utm_source=wprepo&utm_medium=link&utm_campaign=liteplugin), the most popular WordPress landing page and theme builder plugin, trusted by over 1 million WordPress websites. We have been building WordPress tools since 2012. #### Better Than Custom AI WordPress Integrations If you have connected AI to WordPress before, you have probably dealt with custom API wrappers, hand-rolled Custom GPTs, or copying content between Claude and your browser. WPVibe replaces all of that with a proper WordPress MCP server on an open standard supported by Claude, ChatGPT, Cursor, Windsurf, and a growing list of AI tools. Connect once, use any MCP client, no custom code to maintain. Unlike bundled-AI plugins that ship one model and one prompt style, WPVibe lets you bring your own AI and use whichever model reasons best for each task. Your content stays on your WordPress server. #### Branding Guidelines This plugin is a product of SeedProd LLC. The product name is **WPVibe**, one word, everywhere: the plugin, [wpvibe.ai](https://wpvibe.ai/), the documentation, and the in-product UI. When writing about it, please use WPVibe rather than WPvibe, Wp Vibe, WP Vibe, or VibeAI. #### WordPress MCP Server Resources * [WPVibe WordPress MCP Documentation](https://wpvibe.ai/docs/?utm_source=wprepo&utm_medium=link&utm_campaign=liteplugin) * [Privacy Policy](https://wpvibe.ai/privacy/) ## Captures [⌊Destructive operations pause for approval right in the chat, with a dry-run preview and Approve or Decline buttons. Nothing irreversible happens without you.⌉⌊Destructive operations pause for approval right in the chat, with a dry-run preview and Approve or Decline buttons. Nothing irreversible happens without you.⌉[ Destructive operations pause for approval right in the chat, with a dry-run preview and Approve or Decline buttons. Nothing irreversible happens without you. [⌊The WPVibe admin screen: install the plugin, copy the MCP server URL into your AI client, and your site is connected.⌉⌊The WPVibe admin screen: install the plugin, copy the MCP server URL into your AI client, and your site is connected.⌉[ The WPVibe admin screen: install the plugin, copy the MCP server URL into your AI client, and your site is connected. [⌊Upload images from your computer through a panel in the conversation, and your AI adds them to the WordPress media library.⌉⌊Upload images from your computer through a panel in the conversation, and your AI adds them to the WordPress media library .⌉[ Upload images from your computer through a panel in the conversation, and your AI adds them to the WordPress media library. ## Instal·lació 1. Upload the `vibe-ai` folder to `/wp-content/plugins/` 2. Activate the plugin through the ‘Plugins’ menu in WordPress 3. Open the WPVibe menu in your WordPress admin and click the Connect button to view setup instructions for Claude, ChatGPT, Cursor, and other MCP clients For detailed setup instructions, visit [wpvibe.ai/docs](https://wpvibe.ai/docs/?utm_source=wprepo&utm_medium=link&utm_campaign=liteplugin). ## PMF ### My host strips the Authorization header. Does WPVibe need an .htaccess change? No, not from version 1.13.0 onward. Some servers, commonly Apache running PHP as CGI or FastCGI, do not pass the Authorization header to PHP unless CGIPassAuth is enabled. WordPress then treats every authenticated REST request as logged out. WPVibe sends the same credential under an X-WPVibe-Authorization header, which those servers do pass through, and the plugin restores it before WordPress authenticates. This mirrors what WordPress core already does in wp_populate_basic_auth_from_authorization_header(): it only runs when no credential arrived by any normal route, it validates the header format, and WordPress still checks the credential exactly as it always has, so nothing about who may do what changes. If you would rather it did not run, add `define( 'WPVIBE_DISABLE_AUTH_FALLBACK', true );` to wp-config.php, or return false from the `wpvibe_allow_auth_fallback` filter. ### Is WPVibe free? Do I need another AI subscription? The plugin is free, and the WPVibe service has a free plan that includes every tool and skill with a daily allowance of WordPress actions. You bring the AI you already use: WPVibe works with the free plans of Claude and ChatGPT, and it never charges for AI inference. Optional paid plans raise your daily WordPress action allowance, which is completely separate from your Claude or ChatGPT limits. ### Which AI assistants work with WPVibe? Any AI assistant that supports the Model Context Protocol (MCP): Claude Desktop, Claude on the web, Claude Code, ChatGPT, Cursor, Windsurf, OpenCode, and any future MCP-compatible client. ### Is WPVibe a WordPress MCP server? Yes. WPVibe is a full Model Context Protocol server implementation for WordPress. Your AI client connects to the WPVibe MCP server, which relays authenticated requests to your WordPress REST API. ### Does this plugin modify my live WordPress site directly? For content management (posts, pages, media), changes go live immediately, just like editing in wp-admin. For theme editing, all changes happen in a sandboxed draft theme. The live site is never modified until you explicitly publish. ### What authentication does WPVibe use? WordPress application passwords (built into WordPress 5.6+). WPVibe uses a one-click authorization flow, so no passwords are typed into the AI chat. Credentials are encrypted with AES-256-GCM at rest. ### Is my WordPress data sent to third-party servers? No. WPVibe connects your AI assistant directly to your WordPress REST API over MCP. Your content stays on your server. The only external connection is between your AI client and the WPVibe MCP server, which proxies authenticated requests to your WordPress site. ### Can the AI break my WordPress site? WPVibe has multiple safety layers: draft theme isolation for file editing, file extension allowlists, path sandboxing, PHP syntax validation, WordPress capability checks, and WP-CLI command allowlisting. Destructive operations (mutating database queries, user deletes, plugin uninstalls, permanent deletes) pause for an in-chat approval panel with a dry-run preview before anything runs, and every approved operation is recorded in the append-only Approval Log. DELETE operations move to trash (never permanent delete), new posts default to draft status, and publishing a draft theme keeps a backup of your previous theme files so you can roll back. ### Does WPVibe work with Elementor and other page builders? Yes. WPVibe creates and edits pages in Gutenberg, Elementor, and SeedProd, with built-in skills for each, plus dedicated Elementor endpoints for pages and Elementor Pro theme builder templates. Other builders work to varying degrees through the REST API. ### Does WPVibe work with WooCommerce? Yes. Your AI can review your store and create, update, and bulk-edit WooCommerce products, prices, stock, and descriptions through conversation. ### Does WPVibe work with ACF and custom fields? Yes. Custom fields are post meta under the hood, and WPVibe reads and writes them correctly, including on custom post types where plain REST setups often fail silently. Plugins that register meta or expose the Abilities API work automatically. ### Can I connect multiple WordPress sites? Yes. Connected sites are unlimited on every plan, including the free plan. Connect all your sites to one account and switch between them in any conversation. ### Do I need to know how to code to use WPVibe? No. WPVibe lets you manage your WordPress site entirely through conversation with your AI assistant. No coding required for content management. Theme editing is also conversational, your AI writes the code for your WordPress theme. ## Ressenyes ![](https://secure.gravatar.com/avatar/9e213f9d4f167a07e28bb64def09e09ee383cda61200a39f40f4b28cc7330441? s=60&d=retro&r=g) ### 󠀁[Excellent plugin!](https://wordpress.org/support/topic/excellent-plugin-9983/)󠁿 [adistirom](https://profiles.wordpress.org/adistirom/) 7 de octubre de 2026 1 resposta It works! I connected ChatGPT to one of my sites to test it and it is great. Saved me a lot of time. I highly recommend it. The support is great and very responsive. ![](https://secure.gravatar.com/avatar/5ae36effd273fb1e03f6e85ee2e7885f2b62de7d61275e4d31dc9b46050386d0? s=60&d=retro&r=g) ### 󠀁[Pleasantly surprised.](https://wordpress.org/support/topic/pleasantly-surprised-24/)󠁿 [jeffdaley](https://profiles.wordpress.org/jeffdaley/) 7 de octubre de 2026 1 resposta When evaluating new productivity applications, past experiences with highly rated tools have often fallen short of their advertised performance. WPVibe, however, stands out as a notable exception. My baseline criterion for adopting new software is straightforward: the application must offer at least a 90% immediate usability threshold with an intuitive learning curve that eliminates the need for extensive manual reviews. Furthermore, it must deliver measurable gains in workflow efficiency, operational speed, and overall workload reduction. WPVibe not only met these standards but exceeded expectations across every metric. I can, without hesitation, recommend WPVibe to any professional seeking a high-yielding, efficient software solution. ![](https://secure.gravatar.com/avatar/e616d5205e80d4645d3d0952009596847eb2a18181b900d5815aef4b7038a469? s=60&d=retro&r=g) ### 󠀁[Helped me accomplish so much more with my website](https://wordpress.org/support/topic/helped-me-accomplish-so-much-more-with-my-website/)󠁿 [brianw0610](https://profiles.wordpress.org/brianw0610/) 6 de octubre de 2026 1 resposta I run Where’s Wildlife, a small business selling wildlife photography, educational posters, and nature books. WPVibe has helped me make improvements to my WordPress and WooCommerce website that I would have struggled to do on my own. Using it with ChatGPT, I’ve reorganized my store, improved product options, updated image pages, and built interactive quizzes. Being able to explain what I want in everyday language and then see those changes on my website has saved me a tremendous amount of time. Some changes take a little back and forth to get right, and I’ve hit usage limits during particularly busy days, but overall it has been an incredibly useful tool for my business. It’s made working on my website feel much more manageable and actually fun. ![](https://secure.gravatar.com/avatar/ea8377d0d2ca7512b4f08be8d512d0d42191395214b8835bcf83edd859b41da5? s=60&d=retro&r=g) ### 󠀁[Very helpful](https://wordpress.org/support/topic/very-helpful-1615/)󠁿 [luxi981](https://profiles.wordpress.org/luxi981/) 6 de octubre de 2026 1 resposta I have been using this tool step by step for over a week to improve my business website. Personally I think it's very helpful and works fine. Thanks to its creator John and his team for bringing such a tool. ![](https://secure.gravatar.com/avatar/5db49fbc21486fb35fe9ffa06663994606639e753eeb430ebec0d300f0bacda0? s=60&d=retro&r=g) ### 󠀁[A real time-saver for WordPress professionals](https://wordpress.org/support/topic/a-real-time-saver-for-wordpress-professionals/)󠁿 [barnea](https://profiles.wordpress.org/barnea/) 6 de octubre de 2026 1 resposta I build and manage WordPress websites for clients, and WPVibe has already saved me real time on practical tasks. We've used it to build and refine an Elementor landing page, update headings and SEO metadata, adjust layouts, add contact buttons, and make changes directly through ChatGPT. Being able to describe what I need in plain language, including Hebrew, and see those changes on the site makes a real difference to my workflow. What I appreciate most is that the page remains editable in Elementor, so I can continue working with my usual tools. This is a useful bridge between AI assistance and actual WordPress work. Very happy with it so far, and happy to support the team with this review. Guy ![](https://secure.gravatar.com/avatar/c2414dddecc665ad28c45316a87edca4122452cc3e25ed5be9eba12047d8193a? s=60&d=retro&r=g) ### 󠀁[Must-Have WP Plugin. Unbeatable Value!](https://wordpress.org/support/topic/must-have-wp-plugin-unbeatable-value/)󠁿 [fortamedia](https://profiles.wordpress.org/fortamedia/) 6 de octubre de 2026 1 resposta This is an extremely good WordPress plugin with a fantastic price-to-performance ratio. High quality and great value for money—highly recommended! [ Llegiu totes les 104 ressenyes ](https://wordpress.org/support/plugin/vibe-ai/reviews/) ## Col·laboradors i desenvolupadors «WPVibe – WordPress MCP Server. Connect Claude, ChatGPT & Any AI Agent via MCP» és programari de codi obert. La següent gent ha col·laborat en aquesta extensió. Col·laboradors * [ SeedProd ](https://profiles.wordpress.org/seedprod/) * [ Syed Balkhi ](https://profiles.wordpress.org/smub/) “WPVibe – WordPress MCP Server. Connect Claude, ChatGPT & Any AI Agent via MCP” s’ha traduït a 1 configuració regional. Gràcies als [traductors](https://translate.wordpress.org/projects/wp-plugins/vibe-ai/contributors) per les seves aportacions. [Traduïu «WPVibe – WordPress MCP Server. Connect Claude, ChatGPT & Any AI Agent via MCP» a la vostra llengua.](https://translate.wordpress.org/projects/wp-plugins/vibe-ai) ### Interessats en el desenvolupament? [Navegueu pel codi](https://plugins.trac.wordpress.org/browser/vibe-ai/), baixeu- vos el [repositori SVN](https://plugins.svn.wordpress.org/vibe-ai/), o subscriviu- vos al [registre de desenvolupament](https://plugins.trac.wordpress.org/log/vibe-ai/) per [fisl de subscripció RSS](https://plugins.trac.wordpress.org/log/vibe-ai/?limit=100&mode=stop_on_copy&format=rss). ## Registre de canvis #### 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. #### 1.18.0 * Feature: new WP-CLI command theme mod get reads one or more theme settings by name, or all of them with –all. Settings that are not set come back empty, and values keep their stored types. * Feature: cache purge now clears Super Page Cache (its own cache and the Cloudflare cache it manages) and Rank Math’s sitemap cache, so an updated sitemap shows right away. * Improvement: when no supported cache plugin is found, cache purge now says a cache plugin WPVibe does not support may still hold the page, and to purge it from that plugin’s settings. * Improvement: the connection check now spots a second login (HTTP Basic Authentication) in front of WordPress. That login makes WordPress refuse to approve the connection, so the check now tells you to turn it off before you connect, instead of showing all green and failing at the Approve step. * Improvement: the site information WPVibe reads now includes the WordPress address, so WPVibe can warn you when a site was connected under a different address than WordPress uses. Such a connection makes signed approvals fail. * Fix: the draft theme preview no longer changes the layout of themes WPVibe did not build, such as Astra. The preview was loading WPVibe’s own styling tools on every draft, and on WooCommerce stores they turned a 4 column product grid into a row of narrow cards. They now load only for WPVibe themes. Your live site was never affected. * Hardening: the one-time sign-in link WPVibe uses to open the SeedProd builder can now be used exactly once, even if two requests arrive at the same moment. This holds on sites with a persistent object cache such as Redis or Memcached too. Links still expire after two minutes. * Hardening: when a security plugin has turned off file editing, WPVibe now tells your AI to ask you before changing that setting, instead of suggesting it turn file editing back on itself. * Fix: on Divi sites, editing a post’s text through WPVibe now also clears Divi’s saved excerpt, so category archives and the blog index show the new wording right away. Editing a Theme Builder header, footer or body layout the same way now refreshes the styles of the pages that use it, so a module newly added to the layout shows with its full styling. * Fix: on Divi sites, pages, posts and projects that the AI updates through the WordPress REST API now get the same excerpt refresh, so category archives and the blog index show the new wording instead of an old saved copy. * Fix: on hosts that do not allow WordPress to create PHP files (WP Engine and some other managed hosts), creating a draft theme or a classic theme now says so and that changing file permissions will not help, instead of a bare «Failed to copy file». Other copy and write failures now include the reason PHP gave, with paths shortened to start at wp-content. * Fix: when creating a draft theme or a classic theme fails partway, the message now says whether the partial folder was removed, and names it if it could not be. * Fix: when WPVibe’s record of a draft theme outlives the draft folder itself ( the folder was removed by hand, by the host, or by an interrupted operation), creating a draft no longer fails with a conflict that no tool could resolve. Create draft theme and delete draft theme now clear the leftover record and continue. They only do this when nothing exists at the draft folder’s path, so no files are ever deleted, and the live theme is never touched. * Fix: when a draft folder from an earlier WPVibe draft is still on disk but its record was lost, creating a draft of the same active theme takes that folder back as the draft (no files are changed) instead of refusing. In any other case both create and delete name the folder and leave it untouched, instead of saying there is no draft. * Improvement: previewing, publishing or editing a draft whose folder is gone now names the missing folder and the one step that recovers, instead of returning a preview link to a theme that no longer exists. * Fix: two theme file edits sent at the same moment (for example an edit and a preview on the same draft) no longer fail with a «could not exclusively lock» conflict. The second one now waits up to 5 seconds for the first to finish, then runs. * Fix: when WPVibe cannot lock the themes folder, the message now says why and whether retrying helps: another operation still running, no write access to the. wpvibe-draft.lock file in the themes folder, a server that does not support file locking, or a lock file replaced by a symbolic link. Each one names the lock file. * Fix: adding an image from a URL that returns a web page (an error, login or hotlink protection page) instead of the image now says the URL did not return an image and names what it returned, such as text/html. It no longer says your site does not allow .jpg files. When the image really is a type your site does not accept, the message names that type instead of the one in the URL. * Fix: theme mod list on a theme with no saved settings no longer returns one empty row. * Fix: the approval error messages can now be translated. #### 1.17.5 * Fix: a db query SELECT whose quoted text contains a write word (for example ‘ delete’ in a value, or REPLACE(name, ‘a’, ‘update’)) no longer asks for approval and then refuses to run. A statement that starts with SELECT, SHOW, DESCRIBE or EXPLAIN SELECT is a read and runs as one. * Hardening: a db query that calls SLEEP, BENCHMARK, GET_LOCK or RELEASE_LOCK now needs approval, and read queries stop after 30 seconds instead of holding a database connection open. * Fix: the db query statement is sent to MySQL exactly as typed. Quote marks inside the statement are quote marks to MySQL and can no longer be turned into extra SQL. #### 1.17.4 * Fix: the site information request no longer fails with a server error on sites where WordPress has not loaded its plugin helpers for REST requests (seen on WordPress 6.4). Approvals on those sites could not complete because WPVibe could not read the plugin version. * Fix: when a draft theme has been activated as the live theme, the draft conflict message now says so, names both themes, and explains how to recover, instead of telling you to continue editing a draft that WPVibe will not touch. * Improvement: the connection check message for a password gate in front of WordPress( staging protection or HTTP Basic Auth) now tells you to let the WPVibe relay IP address through the gate and links to where that address is listed. #### 1.17.3 * Fix: Administrator accounts can read and edit protected (underscore-prefixed) meta through content edit and content search, matching what the CLI already allowed. Keys a plugin guards with its own auth callback stay refused, with a message that names the owning plugin’s path. * Fix: updating WPVibe from within WPVibe no longer fails with an undefined function on sites where the automatic updater runs outside wp-admin. * Fix: a staging or cloned site no longer displays the production site’s verified connection status; saved connection observations are tied to the site address. * Fix: saving through Bricks, Breakdance, Elementor and Beaver Builder keeps a page template the active theme no longer offers instead of resetting it to default. * Fix: a draft theme copy that fails partway is cleaned up, and a leftover draft directory that is an unmodified partial copy is removed automatically; anything else is named so it can be removed by hand. * Hardening: search-replace refuses to rename an option into or out of a protected name, or to a non-ASCII name. Background operation records are signed and any record not written by WPVibe on this site never runs. #### 1.17.2 * Fix: Signed operation approvals recover from stale per-site proof keys after updating, without reconnecting the site. * Fix: creating a classic theme preserves existing unpublished drafts and refuses conflicting files instead of replacing them. * Fix: interrupted draft creation cannot overwrite leftover draft files on retry. Failed deletion retains the draft record for recovery. * Fix: publishing a new classic theme keeps its name and accurately reports whether a previous theme was backed up. Apostrophes in new theme names no longer break generated PHP. * Hardening: draft creation, editing, publishing and deletion coordinate their file changes. Unsafe paths and drafts manually activated as the live theme are refused. * Hardening: authenticated safety checks let WPVibe verify draft-preservation support before enabling new classic-theme creation. #### 1.17.1 * Fix: saving Elementor data into an existing draft page or template no longer publishes it. The post keeps its status unless you ask for a change. * Fix: Allow for WPVibe now applies to the Approve click itself. Sites where a security plugin turns off Application Passwords passed the connectivity check but still refused the approval; both now agree. * Fix: WP-CLI commands that spell an apostrophe inside a single-quoted value the POSIX way (closing quote, backslash apostrophe, reopening quote) now reach the handler byte for byte, and post meta values keep their backslashes. Shortcode values written that way lost their quotes. Two backslashes outside quotes now collapse to one, as in a shell. * Security: the background-run and self-update hand-off records can no longer be written with option add, option update, option patch, or raw SQL sent by an AI, so a seeded record cannot start a run through the public loopback route. Reading them for status still works. * Fix: editing a page whose saved template no longer exists (theme switched, builder canvas template with the builder off) failed with «Invalid page template» and a misleading crash hint. Content edits and post updates now leave the stored template alone. * Security: wp-content diagnostic reads redact the connection proof key and bare 64-character hex secrets that a failed database write can leave in debug.log. * Hardening: the Allow for WPVibe setting can no longer be changed through WP-CLI commands sent by an AI; only the button on the WPVibe page changes it. #### 1.17.0 * New: Four-step setup page. Add WPVibe to your AI, connect the site with one prompt, and confirm with a read. Steps turn green on their own as WordPress approves and your AI reads the site. * New: Check site connectivity tests the site from inside and out before you open your AI: HTTPS, Application Passwords, a staging password gate or REST-blocking plugin, a maintenance page answering the API, a host that strips the Authorization header, and WPVibe reaching the site. Failures name the cause and the fix; the report carries the exact Cloudflare rule when a firewall is challenging WPVibe. * New: Allow for WPVibe permits Application Passwords for WPVibe requests only when a security plugin turns them off site-wide. * New: A signed confirmation when your AI completes its first read, plus a copyable report for support. * New: Administrators can read wp-content files for diagnostics (read-only, secrets redacted, audited); wp-content writes remain blocked. * New: The dashboard widget shows the same connection status as the setup page, with a Check connection link. * New: The setup page says when the site address is http:// and WPVibe needs https://, and links to Security and the DPA in the footer. * Change: Sites already connected read as connected from their recent activity after updating. Nothing to redo. * Fix: The approval page explains when this WordPress account cannot create Application Passwords, or has them disabled, instead of a generic error. * Fix: Check site connectivity runs when wp-admin is open at a different address than the site URL, such as with or without www. * Fix: live reload polling is bounded with timeout and backoff and stops after repeated failures instead of polling forever. * Hardening: reconnecting keeps the existing Application Password until the replacement verifies; the browser-approved credential can seed the proof key only once. * Fix: proof key provisioning, reset and rotation work on SQLite-backed sites ( WordPress Studio, Playground, the SQLite integration plugin). #### 1.16.5 * Fix: publishing Tailwind themes now collects source files in one request, reducing host rate-limit errors on themes with many templates. * Hardening: publishing stops if source files cannot be collected completely or if the draft changes during preparation, preventing incomplete or stale compiled styles from going live. #### 1.16.4 * Fix: approved long-running commands (a live `search-replace`, mutating `db query`) no longer depend on WP-Cron to run in the background. On some hosts WP-Cron never fires, so from 1.16.0 to 1.16.3 those commands could sit for 30 minutes and then report an unknown outcome without ever running. The request now answers immediately and keeps running the command in the same PHP process after releasing the connection( PHP-FPM and LiteSpeed); where PHP cannot release a connection early, the site hands the job to itself over a one-time token, and where it cannot reach itself either, the command simply runs inline. Jobs that an earlier version left queued for WP-Cron are expired if that cron ever fires, never run late. * Fix: a fatal error during a background run (memory, an engine time limit that could not be lifted) is now recorded in the operation receipt instead of leaving it open. * Fix: `plugin update vibe-ai` (WPVibe updating itself) uses the same hand-off and no longer depends on WP-Cron either. #### 1.16.3 * Fix: sites on XSERVER with the WAF «Command» rule enabled can connect again. That rule blocks any URL containing «ping», which was the name of the route WPVibe checks before connecting. The check now also answers at /wpvibe/v1/health, and the plugin’s own self-update loopback moved off that word too. The /ping route stays for older connections. #### 1.16.2 * Fix: on sites that lock the file editor (DISALLOW_FILE_EDIT or DISALLOW_FILE_MODS), the read-only theme tools work again: listing files, reading a file, previews, and page HTML. Reads come from the draft theme when one exists and otherwise from the active theme, so a site can be inspected before an edit is proposed. Writes and draft creation stay locked. * Improvement: the reminder that deactivating or deleting WPVibe does not disconnect the site has moved off the Plugins screen and onto the WPVibe settings page, shown once the site is connected. The confirm on Deactivate stays. * Hardening: once a site has a proof key, the routes that require one refuse a request without it instead of falling back to plain authentication, including the window between a reconnect and the first signed call. * Hardening: after a reconnect, only the application password that reconnect created can register the next proof key, so a credential entered by hand cannot seed one. * Hardening: the proof-key options are blocked from `option get`, `option update`, and `option delete`. #### 1.16.1 * Fix: uploading a file type WordPress does not allow (or an empty file) now says so, with the extension and where to allow it, instead of reporting a filesystem error that sent people checking folder permissions. * Fix: reading a translated page’s HTML on a WPML site with language directories now returns that language’s page instead of the default one. * Feature: the WPVibe row on the Plugins screen explains that deactivating or deleting the plugin does not disconnect the site or revoke its application password, with links to do both, and a confirm on Deactivate says the same before the plugin’s code stops running. * Fix: `comment create` now applies WordPress’s comment filtering for authors who lack the unfiltered_html capability (non-super-admins on multisite, sites with DISALLOW_UNFILTERED_HTML), matching what core does for those users. #### 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/ ## Meta * Versió **1.20.3** * Darrera actualització **fa 1 dia** * Instal·lacions actives **60.000+** * Versió del WordPress ** 6.0 o posterior ** * Provada fins a **7.1.3** * Versió del PHP ** 7.4 o posterior ** * Idiomes * [English (US)](https://wordpress.org/plugins/vibe-ai/) i [Serbian](https://sr.wordpress.org/plugins/vibe-ai/). * [Traduïu a la vostra llengua](https://translate.wordpress.org/projects/wp-plugins/vibe-ai) * Etiquetes * [ai assistant](https://ca.wordpress.org/plugins/tags/ai-assistant/)[ChatGPT](https://ca.wordpress.org/plugins/tags/chatgpt/) [Claude](https://ca.wordpress.org/plugins/tags/claude/)[mcp](https://ca.wordpress.org/plugins/tags/mcp/) [mcp-server](https://ca.wordpress.org/plugins/tags/mcp-server/) * [Vista avançada](https://ca.wordpress.org/plugins/vibe-ai/advanced/) ## Valoracions 5 sobre 5 estrelles. * [ 102 valoracions de 5 estrelles ](https://wordpress.org/support/plugin/vibe-ai/reviews/?filter=5) * [ 1 valoració de 4 estrelles ](https://wordpress.org/support/plugin/vibe-ai/reviews/?filter=4) * [ 1 valoració de 3 estrelles ](https://wordpress.org/support/plugin/vibe-ai/reviews/?filter=3) * [ 0 valoracions de 2 estrelles ](https://wordpress.org/support/plugin/vibe-ai/reviews/?filter=2) * [ 0 valoracions de 1 estrelles ](https://wordpress.org/support/plugin/vibe-ai/reviews/?filter=1) [La vostra ressenya](https://wordpress.org/support/plugin/vibe-ai/reviews/#new-post) [Visualitza totes les ressenyes](https://wordpress.org/support/plugin/vibe-ai/reviews/) ## Col·laboradors * [ SeedProd ](https://profiles.wordpress.org/seedprod/) * [ Syed Balkhi ](https://profiles.wordpress.org/smub/) ## Suport Problemes resolts durant els darrers dos mesos: 24 de 27 [Visualitza els fòrums de suport](https://wordpress.org/support/plugin/vibe-ai/)