How to Use Claude Desktop to Manage WordPress Content

Most people using Claude for WordPress content have the same workflow: open Claude, write a prompt, get the output, switch to WordPress, paste it in, fix the formatting, add the meta title, set a focus keyphrase, schedule the post.

Then do it again for the next post. And the one after that.

At low volume — say 8 to 10 posts per month — that’s fine. The overhead is annoying but manageable. But if you’re publishing more than that, or if you’re handling multiple sites, the copy-paste workflow becomes a real bottleneck. You spend more time moving content around than you do on the content itself.

There’s a better way. With Claude Desktop connected to your WordPress site via MCP, you can create posts, update content, set SEO metadata, and schedule publishing — all from a single Claude conversation, without touching the WordPress dashboard.

This article covers what that workflow looks like in practice. If you haven’t set up the connection yet, we’ll point you to the setup guide at the end.

What Claude Desktop Can Do With Your WordPress Site

Once the MCP connection is active, Claude has direct access to your WordPress site’s content layer. Here’s what that unlocks:

• Create new posts — Full Gutenberg block format, with title, body, excerpt, categories, and tags set in one step
• Update existing posts — Pull any post by ID or title, edit specific sections, push the changes without touching the editor
• Set Yoast SEO metadata — Focus keyphrase, meta title, meta description — updated via a separate MCP call after post creation
• Schedule posts — Set an exact publish date and time (Claude converts to UTC automatically)
• Search and list posts — Find existing content by keyword, check for duplicate titles before creating something new
• Change post status — Move a draft to scheduled, push something live, or pull it back to draft

None of this requires opening the WordPress dashboard. You describe what you want in plain language, Claude executes the right API calls, and confirms what was done.

The Basic Publishing Workflow

A typical content session with Claude Desktop and WordPress MCP looks like this: you give Claude a topic or a brief, it drafts the post, you review and adjust in the same conversation, then it publishes or schedules directly — no copy-paste, no tab switching.

The whole thing happens inside one Claude Project. That’s important — Projects let you store your voice guide, SEO rules, and content templates as persistent context, so Claude doesn’t need to be re-briefed every session. Every post starts from the same baseline without extra prompting.

Here’s what a typical prompt looks like:

Write a 1,200-word post about how to reduce WooCommerce cart abandonment. 
Use our standard voice guide. Primary keyword: "woocommerce cart abandonment". 
Link to our CRO service page. Schedule it for Tuesday 6am EST.

Claude drafts the post, formats it in Gutenberg blocks, converts 6am EST to 11:00:00 UTC, creates the post, sets the Yoast metadata, and schedules it. One prompt, done.

Creating and Publishing New Posts

When you ask Claude to create a post, it first checks whether a post with the same title already exists — avoiding accidental duplicates. Then it creates the post with the correct status: draft, publish, or future (scheduled).

Categories and tags are set in the same call. Claude accepts plain-language tag names — you don’t need to look up tag IDs or category slugs manually. It resolves them against your site’s taxonomy.

Yoast SEO metadata is a separate MCP call, made right after post creation. The post ID is passed automatically, so there’s nothing extra to track on your end.

Updating Existing Content

Updating is where the workflow really shows its value for content-heavy sites. Instead of opening a post, finding the section you want to change, making the edit, and republishing — you describe the change to Claude and it handles the rest.

Find the post "WooCommerce vs Shopify for Peptide Stores". 
Add an H2 section after the intro about FDA compliance requirements. 
Keep the existing content, just insert the new section.

Claude fetches the post, identifies the insertion point, writes the new section in the correct Gutenberg block format, and pushes the update. The rest of the post is untouched.

One important note: this works cleanly on posts built in Gutenberg. Posts or pages built in Elementor store their content differently — Elementor pages should not be updated via MCP, as it will break the page builder data. Elementor-built pages require a completely different update approach — one that works with the page builder’s data structure rather than around it.

Managing Yoast SEO Without Touching the Dashboard

Setting Yoast SEO fields is a separate operation from creating or updating a post. In the MCP workflow, Claude runs it as a second call immediately after the post is created or updated.

You can set all three fields in a single instruction:

Set Yoast SEO for post ID 37355:
- Focus keyphrase: peptide store chargebacks
- Meta title: Peptide Store Chargebacks: Reduce Your Dispute Rate Below 1% | onPoint Studio
- Meta description: High chargeback rates kill peptide merchant accounts. Here's how to get your dispute rate under 1% and keep your payment processor. (158 chars)

Claude confirms the update with the post ID and the values that were set. If anything looks off, you correct it in the same conversation and re-run the call.

Scheduling Posts in Advance

WordPress stores scheduled post times in UTC. If you tell Claude to schedule a post for “Tuesday at 6am EST,” it converts that to UTC (11:00:00 on the same date) before passing it to the API — so the post goes live at the right time regardless of your server’s timezone setting.

The schedule instruction can be part of the initial create command or a separate update after the fact. Either way, Claude sets the schedule_date parameter in YYYY-MM-DD HH:MM:SS format in UTC — the format WordPress expects.

Tips for Consistent Results

Use a Claude Project for every WordPress site

Store your voice guide, SEO rules, blog post template, and internal link targets inside the Project context. Claude reads these at the start of every session — you get consistent tone, structure, and keyword placement without re-prompting each time.

Be specific about Gutenberg formatting

Claude outputs clean Gutenberg block syntax when you explicitly tell it to. Include a formatting rule in your Project context: “Output all post content in Gutenberg block format using wp:paragraph, wp:heading, wp:list, and wp:code blocks.” Without that instruction, Claude may produce markdown that pastes in as raw text.

Make MCP calls sequential, not simultaneous

Run one MCP operation at a time and wait for confirmation before starting the next. Create the post first, confirm the post ID, then update Yoast — don’t chain them in a single prompt. Chained MCP calls in one prompt can time out or apply the second call to the wrong post.

Know what Claude can’t do via MCP

Image uploads via MCP are unreliable for any real file size — upload featured images manually through the WordPress Media Library, then assign the attachment ID to the post afterward. Claude can tell you the right MCP call to make that assignment once you have the ID. Elementor pages, as noted above, should never be updated through MCP.

Ready to Set This Up?

Everything in this article assumes the MCP connection between Claude Desktop and your WordPress site is already active. If you haven’t done that part yet, the next article walks through it step by step — from enabling the WordPress REST API to the exact claude_desktop_config.json block you need.

Read next: How to Connect Claude Desktop to WordPress via MCP