Most WordPress integrations stop at creating a post. This one carries the rest of the job - the media library, the taxonomy tidy-up, the bulk edits and the user accounts - which is where the afternoon actually goes.
A bridge between an MCP client and a WordPress site, working through the WordPress REST API rather than the database. It authenticates with an application password and then offers tools covering posts, drafts, media, taxonomies and user accounts.
- A site connected with an application password, and a reachability check before anything is attempted
- The full post lifecycle: create, edit, read with revisions, list with filters, schedule, clone, bulk-edit, trash, restore and delete
- Raw text converted into WordPress-ready HTML, and drafts saved locally and reloaded while a piece is still being worked on
- Media library work: upload from a local path or a URL, list and search it, fix titles, captions and alt text, set a featured image, delete in bulk
- Image compression through an external optimiser, which takes its own key
- Categories and tags created, renamed, merged, deleted and assigned across many posts at once, plus a view of every taxonomy the site has, custom ones included
- User accounts listed, created, updated and disabled
A WordPress site with the REST API reachable, and an application password for a user who holds the rights you intend to use - the tools inherit that user's role, so a contributor account will not publish. Node, then point your client at the built server. Image optimisation calls an external service, which takes its own key.