WordPress MCP servers and CLIs compared
Compare WordPress tools for agents: offline posts, drafts from Markdown, safe publishing and setup.
wordpress is a command line and an MCP server for a self-hosted WordPress site: posts and pages, tags and
categories, and the users who write. This page puts it next to the other tools that let an AI agent read and write
WordPress, so you can see which one fits your job. The marks for wordpress come from its first release, its commands
and its source, checked on 19 November 2026 against WordPress 6.9.4 in Docker, not against a live site. They are
checked again at each release. The marks for the other tools come from their own documentation and source, linked in
the table, checked on 19 November 2026. Nothing was signed in to or tested live, and a tool may do more than its pages
say.
The tools:
- wordpress: this tool. Keeps a copy of your posts and pages on your computer, writes drafts on your site, and decides for each action what an agent may do. It signs in with an application password.
- WP-CLI: the official command line for WordPress, the
wpcommand (5,182 stars). It runs on the server, or on your computer against a server over SSH. - MCP Adapter: the official WordPress plugin that turns the site's abilities into MCP tools (1,926 stars). It needs WordPress 6.9 or later, where the Abilities API is part of WordPress. What an agent can do depends on the abilities your plugins make public.
- WordPress.com MCP: the MCP server built into WordPress.com. It also serves self-hosted sites connected through Jetpack.
- claudeus-wp-mcp: the most starred open-source MCP server that calls a site's REST API with an application password (161 stars, changed on 16 March 2026), with 145 tools.
- mcp-wp: InstaWP's MCP server over the REST API with application passwords
(100 stars, changed on 10 September 2026), on npm as
@instawp/mcp-wp.
WordPress lets a program in through an application password, made in the user's profile on a site served over https. It acts with that user's rights. Every tool on this page except WP-CLI and WordPress.com MCP signs in this way. Automattic's earlier plugin, wordpress-mcp, is archived and points to MCP Adapter and WordPress.com MCP, so it is not in the table. Neither are the plugins that add their own MCP server to the site, such as EMCP Tools for Elementor.
✅ yes · 🟡 partly · ❌ no · ➖ not in its documentation · n/a cannot apply
Features
| Task | wordpress | WP-CLI | MCP Adapter | WordPress.com MCP | claudeus-wp-mcp | mcp-wp |
|---|---|---|---|---|---|---|
| Find and read | ||||||
| Read posts and drafts without the internet | ✅ | 🟡 | ❌ | ❌ | ❌ | ❌ |
| Find a post by the words of its title and text | ✅ | ✅ | ➖ | ✅ | ✅ | ✅ |
| One search over posts and the messages and notes of your other tools | 🟡 | ➖ | ➖ | ➖ | ➖ | ➖ |
| Write and publish | ||||||
| Write a draft from a Markdown file | ✅ | 🟡 | 🟡 | 🟡 | ❌ | ✅ |
| Publish a draft, or take a post back to a draft | ✅ | ✅ | 🟡 | ✅ | ✅ | ✅ |
| Schedule a post for a later time | ✅ | ✅ | ➖ | ➖ | ➖ | ➖ |
| Change a post and keep the blocks Markdown cannot hold | ✅ | n/a | ➖ | ➖ | n/a | 🟡 |
| A write stops if the post changed on the site since you read it | ✅ | ➖ | ➖ | ➖ | ➖ | ➖ |
| Upload an image or a file | ❌ | ✅ | ➖ | ✅ | ✅ | ✅ |
| Agents and safety | ||||||
| Let an agent read only | ✅ | 🟡 | ➖ | ✅ | ➖ | ➖ |
| Let an agent write drafts but not publish | ✅ | ➖ | 🟡 | ➖ | ❌ | ❌ |
| Choose for each action: allow, ask or refuse | ✅ | 🟡 | ➖ | 🟡 | ➖ | ➖ |
| A write waits for your confirmation | 🟡 | n/a | ➖ | 🟡 | ❌ | ➖ |
| The password is kept in the system keyring | ✅ | n/a | ❌ | n/a | ❌ | ❌ |
| An agent at a terminal works through commands, without MCP | ✅ | ✅ | n/a | n/a | n/a | n/a |
| Setup | ||||||
| Works with nothing installed on the site | ✅ | 🟡 | ❌ | 🟡 | ✅ | ✅ |
| Works with a WordPress.com site | ❌ | 🟡 | ➖ | ✅ | ➖ | ➖ |
| Several sites, each named in the command | ✅ | ✅ | 🟡 | ✅ | 🟡 | 🟡 |
| Works from ChatGPT or Claude in the browser | 🟡 | n/a | ❌ | ✅ | 🟡 | ❌ |
| Requirement | wordpress | WP-CLI | MCP Adapter | WordPress.com MCP | claudeus-wp-mcp | mcp-wp |
|---|---|---|---|---|---|---|
| Install | npm, Node 22.16+ or 24+ | a PHP file on the server | a plugin on WordPress 6.9+, and npx on your computer for most apps | none: built into WordPress.com | npm or npx, Node 22+ | npx, Node 18+ |
| Licence | Apache-2.0 | MIT | GPL-2.0-or-later | closed service | MIT | GPL-3.0-or-later |
| Price | free | free | free | in every paid WordPress.com plan. Free sites, and Jetpack sites without a Jetpack AI or Complete plan, only until 30 November 2026 | free | free |
Notes on the wordpress column:
- Sign-in. An application password acts with the rights of the WordPress user who made it.
session startreads it from stdin or a hidden prompt, never from an argument. It is kept with its site in the system keyring, or in a private file on a computer without one. See installation. - Without the internet.
synccopies posts and pages with every status, the trash too, with their tags, categories and users, into the WireCat local store. Text is kept as Markdown.posts list,posts searchandposts showread this copy, with--offlinetoo. Your WordPress role decides how much is copied. An Administrator gets everything. An Editor gets every post and page but no users. An Author or Contributor gets part of the posts and no pages, and a Contributor sees only their own posts. - One search. The posts sit in the same local store as the messages, notes and meetings of the other WireCat tools
on the same computer.
posts searchitself finds posts only, so this row is partly. - Drafts and publishing.
posts createalways makes a draft, from a Markdown file or from stdin.posts publishpublishes now, or later with--at-time.posts unpublishtakes a post back to a draft.posts deletemoves a post to the trash, and--allow-deletedeletes it for good. These commands write posts. A page is read from the copy, and is changed only through theapigroup. - Read-only.
WCWP_READ_ONLY=1refuses every write, whatever the settings say. Thereadonlylevel does the same for one key, such aspostsorapi. - Allow, ask or refuse. Each command and each API operation has its key, such as
posts.publishorapi.media-delete, set toallow,ask,readonlyordenyin the settings.mcp serve --permissionmakes a key stricter for one server only. An agent cannot loosen these settings. - Confirmation and publishing over MCP. Every
postswrite isaskby default, andaskasks at a terminal. Over MCP nobody is there to answer, soasklets the agent go ahead, and this row is partly. So by default an agent over MCP can publish.config set permissions.posts.publish denykeeps publishing yours, and the agent still writes drafts.runs listshows each write an agent made. - The post changed on the site. Before a write,
wordpresscompares the post with the copy. If someone changed it on the site since the last sync, the write stops withcontent.conflict. - Blocks. Galleries, columns, embeds and iframes do not survive a trip through Markdown.
posts updatechanges the title, the excerpt, the tags and the status of such a post, and keeps its body. Only--replace-bodywrites the body anyway. - Upload a file. The
apigroup lists media withapi media-listand changes its details withapi media-update. It takes a request body as JSON only, so it cannot send the file itself. - The api group.
wordpress blog apiruns any of the 147wp/v2operations of WordPress 6.9.4, with the same publishing and deleting keys. Installing a plugin, changing the site's settings, users and comments, and changes to templates, widgets, menus and navigation ask by default. WordPress's batch route is never offered, since one batch call would run writes past their keys. Making an application password is never offered either, since WordPress answers with the new password in clear. - WordPress.com. Only self-hosted WordPress 5.7 or later over https. WordPress.com sites sign in with OAuth and are
not supported. The command is
wordpress, notwp, so it lives beside WP-CLI on one computer. - ChatGPT or Claude in the browser.
mcp serve --httpserves the tool behind a tunnel that you set up and keep running yourself, so this row is partly.
When another tool fits better
- WP-CLI: you have a shell on the server and run the site itself: plugins, themes, users, the database, imports of media files. It also works on a WordPress.com site with a paid plan.
- MCP Adapter: your plugins offer abilities you want an agent to use, and you prefer the connection to live on the site. Claude Code reaches it over HTTP with no program of its own on your computer.
- WordPress.com MCP: your site is on WordPress.com, or you want ChatGPT or Claude in the browser with nothing to run on your computer.
- mcp-wp or claudeus-wp-mcp: the agent should upload images, answer comments or change menus and plugins over MCP, with one tool for each job.
If wordpress fits, start with installation. To use it with an agent, see usage.