What is the mcp-wordpress MCP server?
mcp-wordpress is an MCP server over the WordPress REST API, installed with npx @leonardobora/mcp-wordpress or by cloning the repository. After setting WP_SITE_URL, WP_USERNAME and WP_APP_PASSWORD, it gives an agent 80 tools for pages, posts, media, Gutenberg blocks, classic widgets, menus, taxonomies, revisions and Elementor-authored content.
mcp-wordpress wraps the WordPress REST API in 80 MCP tools, so an agent can manage a site's pages, posts, media, menus and taxonomies the same way a person would through wp-admin.
It also handles Gutenberg block content directly, with block-aware reading and editing, plus a shortcode parser for sites that still rely on shortcodes rather than blocks.
What it changes in your workflow
- An agent reads and edits a page's actual Gutenberg blocks, instead of only overwriting a raw content string.
- Shortcodes get parsed and can be replaced in bulk, across many posts at once.
- Revisions, synced patterns and media are reachable the same way pages and posts are.
- Mutations can run in a dry-run mode first, showing what would change before anything is written.
Setup requirements
| mcp-wordpress | |
|---|---|
| Auth | A WordPress application password, created in the user's own profile |
| Config | WP_SITE_URL, WP_USERNAME, WP_APP_PASSWORD in your client's MCP config |
| Cache | An optional small PHP add-on for flushing common cache plugins |
| Elementor content | Readable and editable as page content through the standard tools |
Who it is for
Best for
- Agents managing WordPress content day to day: posts, pages, media and menus through one server.
- Sites built with Gutenberg blocks that want block-level edits rather than raw HTML overwrites.
- Bulk shortcode or content changes across many posts, checked with a dry run first.
Not for
- Editing a page built in Divi rather than Gutenberg or classic WordPress content needs the DiviOps MCP server, built specifically for Divi 5.
- Driving many different WordPress page builders at once from one server is the wider scope the Respira WordPress MCP server covers across 17 builders.
- Working with Elementor's own page data model directly, rather than through generic post content, is the job the EMCP Proxy connects an agent to.
- Turning an existing Elementor page into native Gutenberg blocks, rather than editing either format in place, is a one-time move that the Elementor to Gutenberg migration skill handles.
Use it with UiChemy
This server edits content on a WordPress site that already exists. For a brand new page from a Figma design, UiChemy Figma to WordPress or AI to WordPress builds the editable Elementor or Gutenberg page first. Click Get Started on uichemy.com.
Connect MCP WordPress Server: Manage Pages, Posts and Blocks to your AI client
npx @leonardobora/mcp-wordpressCreate an application password
In your WordPress user profile, generate a dedicated application password for the agent to use.
Add the server entry
Put the config above in your client's MCP settings, with the three WP_ variables filled in for your site.
Optional cache flushing
Copy the project's small PHP add-on into your must-use plugins location if you want the server to flush cache plugins after a write.
Restart and test
Restart your client and ask it to list your site's most recent posts to confirm the connection works.
Client configuration
{
"mcpServers": {
"wordpress": {
"command": "npx",
"args": ["@leonardobora/mcp-wordpress"],
"env": {
"WP_SITE_URL": "https://your-site.example.com",
"WP_USERNAME": "admin",
"WP_APP_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
}
}
}
}What you can do with it
- 80 REST-backed toolsCovers pages, posts, media, menus, widgets, taxonomies and revisions through the same REST API WordPress itself uses.
- Gutenberg-native block editingReads and writes actual block structures instead of treating a page as one opaque content string.
- Shortcode parserFinds and can replace shortcodes across content, useful for sites moving away from an old shortcode-based layout.
- Elementor content supportElementor-authored pages are reachable through the standard content tools, since their output is still stored as post content.
- Dry-run supportMutating tools can run in a preview mode first, so a bulk edit can be checked before it is applied for real.
- Zero-configuration defaultWith just the three WP_ environment variables set, the server works against a standard WordPress REST API with no extra plugin required.
Tools it exposes
list_posts
Lists posts with filtering by status, author or date, matching the REST API's own query parameters.
get_page
Reads a single page, including its Gutenberg block content.
update_page_blocks
Edits a page's Gutenberg blocks directly, rather than overwriting the whole content string.
create_post
Creates a new post or page with given title, content and status.
list_media
Lists media library items, for finding an asset to attach to a post.
parse_shortcodes
Finds shortcodes used across content and returns their names and attributes.
replace_shortcode
Replaces a shortcode's attributes or swaps it for another, across one or many posts.
list_menus
Lists navigation menus and their items.
list_taxonomies
Lists categories, tags and custom taxonomies along with their terms.
get_revisions
Reads the revision history for a post or page.
dry_run_update
Previews a mutation's effect without writing it, for checking a bulk change before it runs.
flush_cache
Clears supported cache plugins after a content change, using the optional PHP add-on.
Frequently asked questions
What is the mcp-wordpress MCP server?
It is an MCP server over the WordPress REST API, giving an agent 80 tools for pages, posts, media, Gutenberg blocks, menus, taxonomies and revisions on a live WordPress site you control.
How do I install mcp-wordpress?
Run it with npx @leonardobora/mcp-wordpress, or clone the repository and run npm install locally, then set WP_SITE_URL, WP_USERNAME and WP_APP_PASSWORD in your own MCP client's configuration settings before restarting it.
Do I need a plugin installed on WordPress?
No plugin is required for the core REST API tools. An optional small PHP add-on can be copied into the site's must-use plugins location only if you want automatic cache flushing after writes.
Does it work with Gutenberg blocks?
Yes. The server reads and edits a page's actual Gutenberg block structure, so an agent can change one block without overwriting the rest of the page's content or its layout.
Can it edit Elementor pages?
Elementor stores its output as regular WordPress post content, so mcp-wordpress can read and edit that content through its standard tools, though it does not parse Elementor's own internal data format.
What is dry-run mode for?
Several mutating tools accept a dry-run option that previews the change without writing it, which matters most for a bulk shortcode replace or a find-and-replace run across many posts at once.
How do I create an application password for it?
In your WordPress admin, open your user profile, scroll to Application Passwords, name one for the agent and generate it; WordPress shows the password once, so copy it into your config right away.


