The official WordPress MCP couldn’t touch my theme. Here’s what WPVibe did

WordPress now has an official MCP adapter, and it is on my site. So is WPVibe. I connected Claude Code to the same site both ways and asked for one small change: an Instagram follow button on my homepage. Only one of them could do it. This is the written version of the reel, with the exact prompt, what happened at each step, and the numbers from my own site.

Get WPVibe free: WPVibe on the WordPress.org plugin repository

Step 1: connect, no passwords

With the free WPVibe plugin installed, I typed one line into Claude Code: Connect my WordPress site https://sebyai.com with WPVibe. It gave me a link. WordPress opened its own Authorize Application screen, I clicked approve, and WPVibe showed “Connection verified”. I never copied a password, a token or a config file.

Step 2: ask in plain English

This is the prompt I used, word for word:

Add a Follow @nikhilsebastian.ai on Instagram button to my homepage hero, linking to https://www.instagram.com/nikhilsebastian.ai/, matching my site's style. Do it as a draft and give me a preview link. Don't publish.

Step 3: it read my theme before touching it

Before writing anything, WPVibe made a draft copy of my theme and read the hero template and its button styles. Then it added the button using the theme’s existing pill-accent style, the same one my other main buttons use, instead of inventing a new look.

It gave me a preview link. The preview bar said it plainly: “Changes are only visible to you. The live site is unaffected.” I checked that as a logged-out visitor, and the live homepage had no button yet.

Step 4: publish, with a safety net I did not ask for

I typed publish. Before going live, WPVibe:

• checked for a recent Duplicator backup and found a completed one from that day,
• kept my previous theme files as a rollback copy,
• flushed the object cache.

Then the button went live. That backup check is the part that won me over. On a live site, that is exactly what I would have done by hand.

The official adapter, same site

The official WordPress MCP Adapter (version 0.7.1 on my site) connects AI agents to the WordPress Abilities API. It can only use the abilities that WordPress and your plugins choose to expose. On my site, that is 51 tools:

• WordPress core: 3, all read-only (site info, user info, environment info)
• Duplicator: 25
• All in One SEO: 13
• WPForms: 6
• WP Mail SMTP: 4

Not one of those 51 can edit a page, a post or my theme. So through the official adapter, the button I just added was not possible.

That is not a knock on the adapter. It is the foundation, and plugins are adding abilities to it every month. It just only does what plugins hand it. WPVibe uses those same abilities first, then fills the gaps with its own tooling: page builders, themes, plugin settings through the plugin’s own logic, and the safety steps around them. That is the difference.

Try it yourself

1. Install WPVibe from WordPress.org (Plugins, Add New, search “WPVibe”).
2. Add the WPVibe connector to Claude Code.
3. Tell Claude “connect my site”, open the link, click approve.
4. Ask for one small change as a draft, and open the preview before you publish.

The free plan includes every tool and skill and as many sites as you want, with a daily limit on tool calls.

Honest notes

• The 51 is from my site on November 1, 2026. Your count depends on which plugins you run and which abilities they register.
• Take a backup before you publish anything on a live site, whichever tool you use.
• If your host has an edge cache, the live change can take a few minutes to show.

WPVibe on WordPress.org: wordpress.org/plugins/vibe-ai

No need to comment or DM me about this one. Everything you need is on this page.