WPVibe connects your self-hosted WordPress site directly to the AI tools you already use, such as Cursor, Claude, ChatGPT, etc., with no second AI subscription—posts, media, SEO, WooCommerce, and even the theme file, all in plain English.
We tested it, providing an unedited, non-affiliated, non-sponsored, raw, and honest first look.
Key Takeaways
- WPVibe connects AI tools such as Cursor, Claude, and ChatGPT to self-hosted WordPress through an MCP server.
- It can help manage WordPress content, media, WooCommerce, plugins, themes, site health, and other tasks through plain-language requests.
- In testing, WPVibe created 50 unique WooCommerce coupons and built draft landing pages with Gutenberg and Elementor.
- The WPVibe plugin adds deeper access for tasks such as theme edits, file operations, WP-CLI-style commands, and fuller site diagnostics.
- Drafts, approvals, and review steps help keep AI-generated changes under human control before they reach a live site.
WPVibe—First Look Video
What WPVibe Brings to WordPress
While a WPVibe plugin is available, at its core, WPVibe is an MCP server that sits between your AI tool and your WordPress site. In plain English, it gives your chosen AI client access to WordPress actions that would otherwise require logging in, clicking through menus, working with files, or running commands.
The team behind WPVibe includes John Turner (Founder) and Syed Balkhi (CEO), the same team behind SeedProd, which will be familiar to plenty of WordPress users.
The product pitch is straightforward: work with WordPress through a normal AI conversation. That can mean asking your AI to create content, review plugins, build a page, add media, inspect site health, create coupons, or make theme changes.
WPVibe includes a fairly broad toolkit:
- A full MCP toolkit for WordPress actions
- More than 40 WP-CLI-style commands
- REST API support for posts, pages, media, and other WordPress content
- Theme-building tools for classic themes
- Gutenberg block validation
- Site intelligence for plugins, themes, PHP, site health, and performance
- Google Lighthouse page audits
- Read-only database queries and search-and-replace operations
- Code snippets through WPCode
- Media support, including Unsplash search and WordPress media library uploads
- Support for switching among multiple connected WordPress sites
The official WPVibe site also frames the product around permissions, audit logs, and guardrails. That matters. Giving an AI access to a live WordPress site without a review step would be a non-starter for many agencies and site owners.
The Cookbook Is Where the Ideas Start Flowing
The WPVibe cookbook is a growing collection of tested prompts and workflows. Think of it as a recipe library for getting real work done instead of starting every AI request from a blank chat box.
Recipes are grouped by use case, including admin tasks, content, inspection, maintenance, marketing, and more. There are also plugin-specific areas for tools such as Beaver Builder, Divi, Elementor, LifterLMS, SeedProd, WooCommerce, and WPForms.
That structure makes sense. Most of us don’t wake up thinking, “I need to use an MCP server today.” We think, “I need 50 coupon codes,” or, “I need a landing page draft,” or, “I need to see what plugins are active across this client site.”
WPVibe turns those jobs into repeatable prompts.
The cookbook is not only about saving time. It gives you a tested starting point, which is helpful when you know the result you need but don’t yet know the best way to ask an AI for it.
The collection should get more useful as it grows. The team also provides a way to request recipes, which is a smart move. Agencies and freelancers tend to repeat the same work across many sites. A useful recipe can become part of a real production workflow.
Connecting WPVibe to Cursor
We used Cursor for this first look. Cursor is only one option, but it made the connection process easy to follow.
The WPVibe documentation provides an MCP server URL. Inside Cursor, we opened the command palette, searched for the MCP tools settings, added a new remote MCP server, and pasted in the WPVibe URL.
After that, Cursor showed that authentication was required. The sign-in flow used an email address and a verification code. Once authenticated, WPVibe appeared inside Cursor with a list of available tools and actions.
The next step was connecting a WordPress site.
We asked Cursor to load the WPVibe skill for connecting a site, then we provided the site URL. WPVibe returned an approval link, which you had to open while logged into the WordPress admin area.
WordPress then displayed a permission screen asking whether WPVibe could connect to the account. After approving the request, the site was connected.
The connection summary was useful right away. Cursor could see the WordPress version, PHP version, active theme, and installed plugins. That alone can remove a lot of unnecessary back-and-forth when you are managing multiple sites.
For agency work, the ability to switch between connected sites in the same AI conversation could be a major time saver. You can switch between approved sites and keep your workflow in one place, rather than logging in and out of multiple dashboards.
The WPVibe Plugin Adds Deeper Access
WPVibe’s plugin is not required for every task. Core WordPress REST API operations can work through WordPress itself.
The plugin becomes more important when you want deeper functionality, including theme draft workflows, file operations, editable fields, WP-CLI-style commands, and fuller site diagnostics. We installed it before testing so there would be fewer limits during the walkthrough.
This distinction is worth keeping in mind if you are evaluating WPVibe for a client site. Basic content and REST-driven work may not need the plugin. More involved management and theme work likely will.
It’s also helpful that the product is not trying to force everyone into one AI app. Your team can continue using the client you already prefer, as long as it supports the connection method that WPVibe uses.
Creating 50 WooCommerce Coupons in One Request
The first recipe we tested was for WooCommerce coupons.
The WooCommerce site started with no coupons. We pasted a cookbook prompt into Cursor and asked it to create a batch of 50 single-use coupons. The request used the IWP- prefix, gave each coupon a 20% discount, set a $50 minimum purchase, and added an expiration date of August 31, 2026.
Cursor first checked that the WooCommerce Coupons API was available. It then created the coupons in batches.
A refresh of the WooCommerce Coupons screen showed all 50 new codes. Each had the requested prefix and unique ending.
This is the type of task that shows why WPVibe can be useful for store owners and agencies. Creating one coupon in WooCommerce is easy. Creating 50 unique, single-use codes with the same rules is not difficult, but it is tedious. It also creates plenty of room for a manual mistake.
There was one important limitation in the response: core WooCommerce supports an expiration date, but not a future activation date for coupons. If you need coupon codes that cannot be used until a future date, you will need an extension that supports scheduling.
That is a good example of what we want AI tools to do. The AI should not pretend it can complete something WordPress or WooCommerce does not support. It should tell you what is possible, then give you the next best path.
Building a Gutenberg Landing Page as a Draft
Next, we tested a block editor (Gutenberg) page build on a site using the WordPress Twenty Twenty-Five theme.
The recipe asks what kind of page you want, the title, and the content sections. We used Cursor’s Plan mode rather than jumping straight into execution. Plan mode lets the AI ask follow-up questions and show the intended scope before it makes changes.
We asked for a newsletter landing page called “WP Vibe Newsletter.” The requested layout included an intro, a three-column features section, and a call-to-action button.
WPVibe checked the active theme and then used the Twenty Twenty-Five design tokens, including the theme’s available typography, colors, and spacing options. It created the page as a draft, not a published page.
That workflow is important. You can review the plan, refine the prompt, preview the result, and publish only when you are comfortable with it.
The page included the requested structure and showed up in WordPress as a draft. It also used standard Gutenberg blocks rather than trying to inject unrelated markup.
We did see an “unexpected or invalid content” warning in the block editor after opening the page. The front-end output still displayed properly, but that is something we would inspect before publishing on a production site. Gutenberg block validation can be picky, and a clean front-end preview should not be the only review step.
Draft mode provides you a practical safety net, but it does not remove the need for human review. You still need to check the page, test the links, and make sure the content fits the site.
The test also showed why prompt quality matters. The first prompt was intentionally light on detail. The page came together fast, but it was still a basic draft. Add your real offer, audience, copy direction, design references, brand colors, form URL, and conversion goal, and the AI has far better material to work with.
Elementor Builds Start With the Free Widget Set
We also tested a landing page build with Elementor, using another WPVibe recipe.
The process was similar. In Plan mode, Cursor asked what the page was for, whether we wanted to supply the copy or have it generate a polished demo, and which brand color direction it should use.
We chose a realistic demo page, asked it to generate the content, and selected a modern blue color direction. WPVibe created a draft for an Elementor landing page with a hero area, feature sections, pricing, and a closing call to action.
The page opened normally in Elementor. It used containers and native Elementor widgets, which is important because the layout remains editable after creation. You are not stuck with a static output that needs to be rebuilt by hand.
One detail came up when reviewing the pricing area. The page did not use Elementor Pro’s dedicated pricing table widget. Instead, it built a pricing layout using more general Elementor elements.
The reason was clear once we asked: the recipe was designed around widgets available in the free version of Elementor. The dedicated pricing table is an Elementor Pro widget, and the AI treated it as out of scope unless asked to use Pro components.
That is not a WPVibe failure. It is a prompt detail.
If your site uses Elementor Pro and you want Pro widgets, say so. A better request would include a line such as, “Use Elementor Pro widgets where they are the best fit, including the pricing table widget.”
AI work gets better when we are explicit about the tools, plugins, design rules, and site requirements that matter. We also like asking the AI to identify questions we have not considered before it begins the build.
Draft-First Workflows Are the Right Call
The biggest concern with AI site management is obvious. What happens when the AI gets something wrong?
WPVibe has taken a draft-first approach. Theme edits can happen in an isolated draft clone. Content can be created as a draft. Destructive actions can require approval. The system also provides interactive panels for approving actions and alerts when an AI has made a change.
The same thinking shows up in areas such as read-only database queries and validated Gutenberg block output. WPVibe is giving the AI useful access, but it is not treating a production website like a sandbox.
For agencies, this should be part of the appeal. You can use AI to reduce repetitive work while still controlling its publishing access across client sites.
There is still a process to follow:
- Provide the AI with clear context and a defined task.
- Review the plan when the task is more involved.
- Preview drafts and inspect the WordPress editor output.
- Test forms, links, mobile layouts, and store behavior.
- Publish only after the work meets your standards.
Pricing, Documentation, and Product Maturity
WPVibe was in early access pricing during the first look. The stated plan was for paid subscriptions to move to usage-based tiers later, while current subscribers would transition to an equivalent tier at the same price.
If you are considering it, review the current plan details directly before making a decision. Early access pricing and product features can change as a product matures.
The documentation was one of the better parts of the experience. It includes AI client setup steps, connection instructions, and explanations of when the WPVibe plugin is needed.
We could not locate a public changelog during the review. A changelog that covers plugin updates, platform changes, and new cookbook recipes would help agencies and power users track what is new.
For those who want to inspect how the project is built and updated, WPVibe has a public GitHub repository.
When AI Stops Writing and Starts Running WordPress
WPVibe is what happens when your AI stops writing about WordPress and starts running it.
The draft-first guardrails are what make it practical. AI moves fast; production WordPress sites still need a human in the loop. Every significant change stays in draft or requires approval before it ever reaches visitors.
If you manage multiple sites, run an agency, or still burn hours every week on the same admin, content, and maintenance work, WPVibe is the missing link that finally lets the AI you already pay for actually operate WordPress.
Frequently Asked Questions About WPVibe
What Is WPVibe?
WPVibe is an MCP server that connects AI clients such as Cursor, Claude, and ChatGPT to self-hosted WordPress sites. It lets users request WordPress tasks through an AI conversation instead of completing every action manually in the WordPress dashboard.
Does WPVibe Require a WordPress Plugin?
Not for every task. Basic content operations that use the WordPress REST API can work without the plugin, while deeper functions such as theme drafts, file operations, editable fields, WP-CLI-style commands, and expanded diagnostics require the plugin.
What Can WPVibe Do in WordPress?
WPVibe can work with posts, pages, media, plugins, themes, WooCommerce, site health, performance checks, code snippets, and selected database tasks. In testing, it created 50 single-use WooCommerce coupons and built draft landing pages for Gutenberg and Elementor.
Can WPVibe Publish Changes Directly to a Live Site?
WPVibe supports draft-first workflows and approval steps for significant changes. Users should still review drafts, inspect editor output, test links and forms, check mobile layouts, and confirm store behavior before publishing.
Which AI Tools Work With WPVibe?
The review tested WPVibe with Cursor. The product is designed to work with the AI client a user already prefers, as long as that client supports the connection method used by WPVibe.