WPVibe for WordPress: What the Live Agent Demo Shows

Can an AI assistant manage a real WordPress site without hand-editing every block and plugin setting? In Andrew Warner's live interview with WPVibe founder John Turner, Claude changes a hero, creates a landing page, repairs a layout problem, adds an exit popup, and drafts a sample course. The useful lesson is the review loop: the first result is not the finished website.

Watch the Live Demo

Credit and disclosure: This is The Next New Thing's interview with WPVibe founder John Turner, presented by Zapier. Product claims and demo outcomes belong to the speakers. Setup, plan, and safety details below are checked against WPVibe's documentation and the WordPress.org plugin listing.

How the Connection Works

WPVibe is not a replacement for WordPress hosting or for Claude or ChatGPT. It combines a WordPress plugin with a hosted Model Context Protocol (MCP) service. The AI assistant calls WPVibe's tools; WPVibe relays authorized actions to the site's WordPress REST API. The service runs with the permissions of the WordPress user who approves the connection, according to its connection guide.

1. Install the free WPVibe plugin on a self-hosted WordPress site and check its connection screen.
2. Add WPVibe in a supported AI client, or use the documented MCP server URL https://mcp.wpvibe.ai/mcp. Follow the client-specific setup guide; availability of custom connectors depends on your AI plan.
3. Sign in to WPVibe, authorize the specific site in wp-admin, and ask the assistant to list connected sites before giving it an editing task.

At 1:39, John describes the browser setup. At 2:15, he shows the MCP path for other clients. Do not paste WordPress passwords into a chat; use the authorization flow and review the account's permissions. WPVibe says the connection uses a revocable WordPress application password, encrypted on its hosted service.

The Landing Page: Fast First Pass, Then Repair

The demo starts with a static hero changed to video. John then asks Claude for a winter-escape landing page with very little direction. The first page has an offer and moving banner, but Andrew notices empty space below the banner. John asks the assistant to remove the site's navigation, add a Christmas countdown, inspect the missing section, and fix the layout. A second pass visibly fills out the page.

At 6:00, they request a 10% exit-intent popup and demonstrate it appearing when the cursor moves toward the browser chrome. That shows an interaction in this test, not that the coupon is valid, that it works on mobile, or that a lead reaches a mailing list. The offer itself is invented for the demo; a real countdown or discount needs an actual deadline and approved terms.

Practical takeaway: give an agent an approved offer, audience, CTA, source images, and constraints. Review the first render in a browser, especially below the fold and at phone width. Ask for targeted corrections rather than treating the first prompt as a launch.

The Membership Course Is a Prototype

At 7:39, John asks Claude to create a short Airbnb-hosting course. The site already has MemberPress with its Courses add-on and LifterLMS installed. Claude creates a course outline and lesson pages, but both speakers acknowledge the content is generic and guessed; a subject expert would have to replace it. In an incognito window, John reaches an enrollment page that says “join for free.” He also asks Claude to remove a page comment.

The demo does not establish a complete paid membership: no checkout, billing webhook, entitlement, cancellation, or protected-lesson audit is shown. Before selling access, test each of those flows as a logged-out visitor and as a paying member. Confirm which course plugin owns the content and access rules; two installed LMS or membership systems can make the responsibilities unclear.

What WordPress Gives You, and What the Video Only Suggests

The main case for this approach is preserving WordPress's existing content, themes, plugins, and hosting instead of rebuilding a site from scratch. That does not make every plugin equally controllable by an agent. The plugin listing names specific page-builder integrations and says other plugins may be reachable through their REST or Abilities APIs. Test the particular plugin and operation you need.

Two useful ideas in the interview remain ideas, not completed integrations:

• Popup to mailing list: John proposes sending a lead through a Zapier webhook to Mailchimp at 6:45. The video does not build or test that workflow.
• Analytics-led edits: John proposes giving an agent a separate analytics connection and WPVibe site access at 12:45. No Google Analytics or Search Console connection, analysis, or measured conversion lift appears in the demo.

John also says changes to a WordPress site remain if a WPVibe subscription ends. That is distinct from continued agent access: the site still needs hosting, its normal plugin licenses, maintenance, and whatever AI or WPVibe plan the owner chooses. Treat generated PHP snippets and theme edits as code changes requiring a backup, review, and rollback plan.

Free Allowance and the Video's Discount

WPVibe's pricing page currently lists a Free tier of 100 tool calls in a rolling 24-hour window, shared across connected sites, with a larger first-week allowance. Paid plans increase that WPVibe allowance; they do not replace a separate AI client's limits. A tool call is a WordPress action, not a full conversation. Check the live page for the current count and prices before planning a large batch.

At 15:09, the video mentions 15% off a year of a paid plan. The supplied links do not include a verifiable code or eligible checkout URL, so treat this as a video offer to confirm at checkout, not a guaranteed site-wide discount.

Before You Let an Agent Change a Live Site

1. Back up and scope access. Test on staging where possible, use a WordPress user with only the necessary capabilities, and keep a rollback path.
2. Know what is a draft. WPVibe documents a sandboxed draft flow for theme-file work, but its plugin FAQ says content and media actions can touch the live site. Confirm status and target before every content edit.
3. Review the actual page. Check factual claims, images and rights, mobile layout, keyboard access, contrast, forms, consent language, and speed.
4. Test the business path. Submit the form, confirm the webhook and mailing-list record, verify the coupon, and test membership as logged-out, free, and paid users.
5. Approve risky actions separately. Review plugin installs, code snippets, user changes, payments, and publishing. Record who approved the change and when.

A Safer First WPVibe Prompt

Use this with a site you own or have permission to manage. It asks for an outline and preview before any live change.

Video Chapters

Sources and Limits

• Primary demo: Andrew Warner with John Turner, plus the transcript supplied for this article. We did not independently access or audit the demo's WordPress site.
• Product documentation: WPVibe setup, connection model, WordPress.org plugin listing and FAQ, and current plan page. These are vendor-controlled sources; actual compatibility and limits should be checked in your environment.
• Editorial distinction: The landing-page corrections, popup appearance, course outline, and free-enrollment screen are visible in the episode. A working email integration, analytics optimization, paid membership, and general time savings are not demonstrated there.