draft-articleLABSCO SUMMARY
Edit a post the way you edit a file: pull it, change lines, sync once.
pull-for-editing opens a post or page as a Markdown document session, read-document shows it with line numbers, and edit-document-line, insert-at-line, replace-lines and search-replace change it in place; sync-to-wordpress then sends every change back as one update, with the formatting converted to HTML for you. Which of the 26 tools a launch exposes depends on the --personality it starts with — contributor, author, editor or administrator — but your WordPress user's own permissions still decide what succeeds, so give the connection an account with exactly the role you want it to have.
What it is
A WordPress content server organised by role: a --personality flag (contributor, author, editor or administrator) decides which of its 26 tools a launch exposes, from drafting and line-by-line editing up to publishing, media, comments and categories.
What you get
- find-posts searches posts and pages in plain language with an intent — edit, review, publish or comment — and suggests the next step for each result
- Drafting and publishing: draft-article, draft-page and edit-draft, submit-for-review and view-editorial-feedback, and — from the author role up — create-article, create-page and publish-workflow to publish now or schedule
- Document sessions: pull-for-editing opens a post or page as Markdown, read-document shows it with line numbers, edit-document-line, insert-at-line, replace-lines, search-replace and edit-document change it, and sync-to-wordpress pushes every change back as one update
- Site management for editor and administrator launches — bulk-content-operations, review-content, moderate-comments and manage-categories, plus manage-all-content for administrators — and manage-media from the author role up
Requirements
A WordPress site and an account on it: WORDPRESS_URL, WORDPRESS_USERNAME and WORDPRESS_APP_PASSWORD, either as environment variables or in a .env file the server looks for in a directory under your home folder or beside itself. Use an Application Password, generated under your profile in WordPress admin, rather than your login password. The server is cloned and run with node, and a setup script writes the credentials file for you. Which tools appear depends on the personality the server is launched with — but your WordPress user's own permissions still decide what actually succeeds, so a role that cannot publish will not publish however the server is configured.
Setup effort
Build from source — git clone https://github.com/aaronsb/wordpress-mcp
USE CASES
01
Publishing a draft you worked out in conversation
Save it with draft-article, then publish it with create-article or schedule it through publish-workflow — or submit it for review if the server runs as a contributor.
02
Fixing something in a published article
Find the post by title, read it back to see what is actually there, and update it by id.
03
Checking what has already been written about a topic
Search by keyword before writing anything new, so a second post does not duplicate an existing one.
26 tools
Listed in project docs. Your client may show a different list.
draft-pageedit-draftsubmit-for-reviewview-editorial-feedbackpull-for-editingread-documentedit-document-lineinsert-at-linereplace-linessearch-replaceedit-documentsync-to-wordpresslist-editing-sessionsclose-editing-sessioncreate-articlecreate-pagepublish-workflowmanage-mediatrash-own-contentbulk-content-operationsmanage-all-contentreview-contentmoderate-commentsmanage-categoriesfind-postsBEFORE YOU INSTALL
What to know first
Tools you get
26 tools named in the project's documentation. The --personality role (contributor, author, editor, administrator) decides which subset a launch exposes.
Requires
- Node.js and npm on PATH
- The WordPress Feature API plugin, active on your WordPress site
- WORDPRESS_APP_PASSWORD in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/aaronsb/wordpress-mcp
cd wordpress-mcp
npm install
npm run setupThe setup wizard asks for your WordPress URL, username and application password, lets you pick a personality, and writes the .env file the server reads
MCP Clients
Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"wordpress-author": {
"command": "node",
"args": [
"<YOUR_PATH_TO_WORDPRESS_MCP>/src/server.js",
"--personality=author"
]
}
}
}The configuration on this page does not set WORDPRESS_APP_PASSWORD; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
