Block MCP
The WordPress AI connector that just works. Your AI agents can edit your posts and pages at the block level, making surgical, reliable changes without breaking your layout.
Free & open source · MIT licensed · Works with Claude, Cursor, and any MCP client
This is the easiest way to have AI edit your WordPress content.
Don’t let all the technical details below scare you. Download the free plugin, install it, go to Settings, click on Block MCP, and follow the steps.
Here’s an article showing you the complete setup flow.
Still have any questions? Ask support.
I would love for you to use this because it’s changed how I use WordPress, and I’m confident it will for you, too.
Edit individual blocks, not whole posts
Read, insert, update, delete, move, duplicate, wrap, and replace blocks one at a time. Your AI agent fixes a single paragraph without rewriting—and risking—the entire page.
- Surgical edits: change one heading, swap a CTA button, add a row to a comparison table.
- Persistent block IDs that survive edits, so an agent can plan and execute across multiple turns.
- Built-in search by text or block type—no regex over rendered HTML.
Everything your AI agent needs to edit WordPress safely
Block MCP exposes a post as a structured tree of blocks instead of one big blob of HTML—so your agent understands your content the moment it connects, and changes just work the way you want them to.
- Block-level editing: insert, update, move, duplicate, wrap, and replace—one block at a time.
- Persistent block IDs: stable references let an agent plan and execute changes across turns without re-reading the post.
- Atomic batch edits: apply up to 50 changes in a single revision—if one fails, none of them touch the post.
- Smart auto-updates: change a heading from H2 to H3 and the markup follows automatically.
- Per-site block preferences: steer the agent toward your favorite blocks and away from anything you’ve deprecated.
- One-click undo: every edit is revision-backed, so you can roll back any change, any time.
- Yoast SEO built in: read and write titles, meta descriptions, focus keywords, canonical URLs, and schema.
- No broken blocks: block markup is preserved exactly—posts still open cleanly in the editor afterward.
How it compares to the WordPress REST API
Most WordPress automation—including other MCP servers—ultimately writes through the standard REST API, which treats a post as one big blob of HTML. That’s fine for publishing a finished draft, but it falls apart fast when an AI agent needs to make small, targeted edits to an existing page. Here’s what changes when the agent can work at the block level instead.
| What the agent can do | Standard WP REST API | Block MCP |
|---|---|---|
| Edit one heading without touching the rest of the page | ❌ Rewrites the entire page on every edit | ✅ Updates just the one heading |
| Make 5 edits in a row without re-sending the whole page each time | ❌ Sends the full page body 5× | ✅ Sends only what changed |
| Find which block contains “Pricing” without scanning rendered HTML | ❌ No structured search—the agent has to regex through HTML | ✅ Built-in search by text or block type |
| Stop legacy or deprecated blocks from being saved in the first place | ❌ No block-aware validation; deprecated blocks save without warning | ✅ Server rejects legacy blocks and suggests modern replacements |
| Edit a page and have it still open cleanly in the block editor afterward | ❌ Edits as raw HTML—expect many blocks flagged “This block contains unexpected or invalid content” because the original block markers got stripped | ✅ Block markup is preserved exactly |
| Keep editing the right block after adding or removing other blocks above it | ❌ Has to re-read the whole page after each edit | ✅ The agent keeps working without re-reading |
| Fix several typos across one page in a single revision | ❌ Multiple round-trips and revisions cluttering history | ✅ One update_blocks call, one revision, atomic—partial failure rolls back the whole batch |
We tested it. Only Block MCP worked every time.
We put Claude in front of popular WordPress MCP servers and gave it one instruction: “change the H2 heading ‘Code samples’ to H3,” then reopened the page to inspect it. 27 runs total—3 servers × 3 models (Haiku, Sonnet, Opus) × 3 runs each.
| Model | Block MCP | AI Engine Pro | InstaWP/mcp-wp |
|---|---|---|---|
| Haiku | ✅ 3 / 3 · 10s avg | ⚠️ 2 / 3 · 44s avg | ❌ 0 / 3 · 20s avg |
| Sonnet | ✅ 3 / 3 · 9s avg | ✅ 3 / 3 · 14s avg | ❌ 0 / 3 · 36s avg |
| Opus | ✅ 3 / 3 · 9s avg | ✅ 3 / 3 · 13s avg | ⚠️ 2 / 3 · 38s avg |
| Total | ✅ 9 / 9 | 8 / 9 | 2 / 9 |
Only Block MCP succeeded reliably across every model. The full, reproducible benchmark script is in the README—run it against your own site.
Free. Open source. Easy.
Don’t know what an MCP is? Don’t worry: install the free connector plugin and it will guide you from there.
Block-level read & write for any Gutenberg post or page, with atomic batch edits, persistent block IDs, and one-click undo.
- Edit individual blocks, not whole posts
- Per-site block preferences and built-in Yoast SEO support
- Works with Claude, Cursor, and any MCP client
- MIT licensed — use it on every site you build
Have more questions?
A few common questions about what Block MCP does and how to get started.
You must log in to submit a review.