Edit WordPress with Claude - Developer Guide

• By Praveen Jha · Updated 2026-10-23 · 11 min read · Developer & MCP tools

Stop hunting through menus for every small change. Connect Claude to your WordPress site once - in about five minutes, for free - then make edits by chatting: write a post, update a page, change a WooCommerce price, clean up drafts.

Time: ~5 minutes Cost: Free Level: Beginner - no code Tool: WPVibe by SeedProd

Who this is for: Developers, site owners and content teams running a self-hosted WordPress site who want a fast, repeatable way to hand routine edits to Claude - with approvals and an undo path built in.

What is inside

1. How it works - the connection in 30 seconds
2. Before you start - prerequisites and limits
3. Steps 1-2 - Install WPVibe and pass connectivity
4. Steps 3-4 - Connect Claude and authorise your site
5. Step 5 - Verify with a read-only test
6. Prompt library - copy-paste prompts that work
7. Safety model - approvals, trash and revoking access
8. Troubleshooting and pre-flight checklist

Read this first: This works on self-hosted WordPress only - a live site on https://. It does not work on WordPress.com free plans, and a site that only runs on your own computer (LocalWP, MAMP) will not connect without extra setup, because WPVibe works through the cloud.

1. How it works - the connection in 30 seconds

Changing one line on a WordPress site usually means logging in, hunting for the right menu and clicking twenty times. After this one-time setup, you tell Claude what to change and it makes the change on your site for you.

The tool that does this is WPVibe, a free plugin from SeedProd - the team behind the SeedProd page builder. It connects Claude to WordPress over MCP (Model Context Protocol), a standard way for AI apps to plug into other tools.

1. You: Type a plain-English instruction in Claude chat.
2. Claude: Picks the right WPVibe tool for the job.
3. WPVibe Connector: Carries the request over MCP via the cloud.
4. WordPress: The WPVibe plugin applies the change on your site.

Four ideas a developer should hold on to

1. No real password in chat

Authorisation creates a WordPress Application Password for WPVibe. You approve it inside WordPress admin - you never type your real password into Claude.

2. Cloud relay, live site required

WPVibe works through the cloud, so the site must be reachable on the public internet over HTTPS. Local-only installs cannot be reached.

3. Drafts by default

New posts are saved as drafts by default. Claude only publishes when you explicitly ask it to.

4. Risky actions pause

Deleting things, changing the database or uninstalling plugins pause for your approval, and you see a preview first.

Mental model: Think of WPVibe as a scoped remote control. Claude can read and edit content through it, but the permission lives in WordPress - and you can revoke it there at any time (see Section 7).

Before you start - prerequisites

Check all four items before you begin. Most setup failures trace back to item 1 or 2.

What will not work

WordPress.com free plans - this setup is for self-hosted WordPress only.

• Local-only sites - LocalWP, MAMP and similar setups will not connect without extra setup, because WPVibe works through the cloud.

Plain http:// sites - HTTPS is required; the connectivity check will flag it.

Team and Enterprise note

On a Claude Team or Enterprise plan, an admin may have to turn WPVibe on first. Ask your workspace admin before troubleshooting a missing connector.

Cost and limits - set expectations early

• The WPVibe plugin is free. Its free plan gives you every tool, with a daily limit on how many actions it runs.
• Paid WPVibe plans raise that daily limit - they do not unlock extra tools.
• It works with Claude's free plan too, and WPVibe never charges you for the AI itself.

Developer tip: Do the first run on a staging site or a low-risk production site, and take a normal backup first. The workflow is reversible for content (trash, drafts), but a backup is still the cheapest insurance before any AI-driven edit session.

Install WPVibe and pass connectivity

Step 1 - Install the WPVibe plugin

1. In your WordPress dashboard, go to Plugins > Add New Plugin.
2. Search for WPVibe.
3. Find "WPVibe - MCP Server for WordPress" by SeedProd and click Install Now. Check the author name - do not install a similarly named plugin.
4. Click Activate.
5. A new WPVibe item appears in the left sidebar. That confirms the plugin is active.

Step 2 - Check site connectivity

1. Click WPVibe in the sidebar.
2. Under Check your connection, click Check site connectivity.
3. Wait for "Site connectivity: Passed" with a green tick. That means WPVibe can reach your site.
4. If it fails, the page tells you the cause and the fix. Fix it and run the check again - do not continue to Claude until this passes.

Usual causes of a failed check: the site is not on HTTPS, a security plugin is blocking Application Passwords, or a firewall is blocking the connection.

Connect Claude and authorise your site

Step 3 - Add WPVibe inside Claude

1. Open the Claude desktop app (or claude.ai).
2. In the sidebar, open Customize > Connectors.
3. Search for WPVibe and click Connect.
4. Enter your email. WPVibe sends you a 6-digit code - you will see it in the email subject line. Type it on the WPVibe page. This creates your free WPVibe account. The code works for 15 minutes; check spam if it does not arrive.
5. Go back to Claude. WPVibe now shows as connected.

Step 4 - Authorise your WordPress site

Start a new chat in Claude and send this, with your own site address:

Copy-ready text

Connect my WordPress site https://yoursite.com using WPVibe.

1. Claude replies with an authorisation link. Open it while you are logged in to your WordPress admin.
2. WordPress shows an approval screen. Click Approve.
3. That creates a WordPress Application Password for WPVibe - so you never type your real password into the chat.
4. Back on the WPVibe page in WordPress, it now says Site connected. The connection is done.

Security check before you click Approve: Confirm the browser is on your own WordPress domain, you opened the link from your own Claude chat, and the request names WPVibe. If any of those do not match, close the tab and start Step 4 again.

Verify first, then use the prompt library

Step 5 - Run the read-only test

Paste this into Claude. It is the same prompt the WPVibe page shows you - use it before any edit, because it changes nothing.

Copy-ready text

Use WPVibe to read my site at https://yoursite.com (the site_info tool).
Tell me the site name and address it returns. If it fails, show me the
error and what to do next. Do not change anything.

If Claude comes back with your site name and address, it is all working. The last step on the WPVibe page turns green by itself.

Prompt library - swap in your own topic, product or page names

Prompting habits that save rework: Name the exact page, post or product. Say "save as draft" when you want to review first. For bulk changes, ask Claude to list what it will change before it changes it.

Safety model - approvals, trash and revoking

Handing an AI edit access to a live site is reasonable only if you know exactly where the brakes are. WPVibe has three.

Approvals for risky actions

Risky actions like deleting things, changing the database or uninstalling plugins pause for your approval, and you see a preview first. Read the preview - do not approve on autopilot.

Trash, not permanent delete

Anything deleted goes to the trash, so you can get it back. Check the trash promptly if an edit session touched content you did not expect.

Drafts by default

New posts are saved as drafts by default. Claude only publishes when you ask it to - so "publish it" in a prompt is a deliberate instruction, not boilerplate.

Scoped credential

Access runs on a dedicated Application Password, separate from your real login password. Revoking it does not change your password or lock you out.

How to cut access completely

Do both steps. Deactivating the plugin on its own does not disconnect the site, so do not stop there.

1. In WordPress, revoke the WPVibe Application Password under Users > Profile > Application Passwords.
2. Remove the site from your WPVibe account.

Good practice for teams

• Connect with a dedicated admin workflow and record who holds the WPVibe account email - that inbox receives the sign-in codes.
• Review Application Passwords periodically under Users > Profile, and revoke any you no longer recognise.
• Keep the "verify read-only first" step in your runbook whenever a new site or a new team member is connected.
• For client sites, agree in writing what Claude may publish directly and what must stay in draft for review.

Troubleshooting and pre-flight checklist

Pre-flight checklist - tick before every new site

• [ ] Site is self-hosted WordPress 6.0+, live, on HTTPS
• [ ] I have the admin login and a recent backup
• [ ] WPVibe plugin installed (by SeedProd) and activated
• [ ] Connectivity check shows "Passed" with a green tick
• [ ] WPVibe connector connected in Claude (Customize > Connectors)
• [ ] Site authorised via the approval screen - status: "Site connected"
• [ ] Read-only site_info test returned the correct name and address
• [ ] I know how to revoke: Users > Profile > Application Passwords

Quick reference

Related pages

• Free AI guides (Resources)
• Learn AI
• Contact Praveen