Anything can create a WordPress post over the REST API; the interesting half here is the stage before that — wireframes, design tokens and a site hierarchy that later calls build against, so a request like 'redesign the homepage' has something to be consistent with. The live preview with per-change approval is the right safety model for tools that write to a production site. Do generate a fresh application password for it, and rotate any key you find pre-filled in a setup guide.
A hosted WordPress automation platform reached over MCP. It connects to your site through the WordPress REST API using an application password, and splits its tools into three stages: planning a site, building it, and auditing what was built.
- Planning before building — business plan and design-document tools, wireframes, design tokens, a theme picker, a full site hierarchy and a sitemap generator
- Execution against the live site — content management for pages, posts and custom post types, theme customisation and management, menus, widgets, the media library, users, and site settings
- A build tool that takes a whole site from the plan, and a modification planner that documents a change before applying it
- WooCommerce management for stores
- Analysis after the fact — design analyzer, content audit, SEO manager, user-journey mapping, navigation optimiser and form analysis
- Three ways to drive it: prebuilt workflows, a custom workflow builder that sequences tools, or calling a single tool directly
- A live preview that shows changes as they are made, with approve, modify or reject on each one
A WordPress site with admin access, and an application password generated under Users > Profile — the platform authenticates with that rather than your main password. Connect the site in the dashboard by entering its URL, your username and the application password. Clients reach the hosted server through the Smithery CLI with your own API key. Self-hosting is possible from this repository with `npm install` and `npm start`; that path needs `TANUKIMCP_MASTER_KEY` for API access and `OPENAI_API_KEY` for the AI features, with `PORT`, `REQUIRE_API_KEY` and `HEADLESS` as optional settings.
One command plus a key — npx @smithery/cli run @tanuki/wordpress-mcp, then supply credentials