How to stop context-switching between your WordPress dashboard and Claude, and manage your entire content workflow through conversation
Node.js installed — lightweight runtime for the MCP server
WordPress Application Password — secure auth method, created in User Profile
Site configuration file — ~/.wp-mcp/wp-sites.json with URL, username, and password
Claude Desktop MCP config — points to local MCP server with correct system path
Use Claude’s analytical and creative capabilities directly on WordPress content — draft posts, analyse SEO, bulk-update metadata, check draft status — without ever opening the WordPress dashboard.
Content workflows meant constant switching between Claude and the WordPress admin. Ask Claude to help draft something, copy text back, manually format in WordPress, review SEO separately, repeat dozens of times per week.
WordPress integrations require plugins or third-party tools on your server. No. MCP servers run locally on your computer. WordPress only needs to have its REST API enabled (built-in since 5.6) and one application password created. Zero modifications to your site’s code, zero plugins, zero security risk.
REST API disabled on host — Some managed WordPress hosts block the REST API by default for security. Every standard MCP setup assumes it's available.
Check hosting dashboard for REST API settings or contact support. The API is core WordPress; hosts sometimes just need it explicitly enabled in their control panel.
Application Passwords blocked by security plugins — Wordfence and similar plugins disable this feature by default, even though it's a native WordPress feature.
Check your security plugin settings. Find 'Application Passwords' or 'REST API' configuration and enable it for your user. Create the password once it's enabled.
Wrong path in Claude Desktop config — Using a placeholder path instead of your actual username causes silent connection failure with no error message.
Always use your actual system username from **whoami** (Mac) or **echo %USERNAME%** (Windows). Wrong path = immediate disconnect when Claude starts.
List posts by status, date, or content — see drafts, scheduled, published instantly
Create and update posts directly — no copy-paste, full formatting support
Analyse SEO — get recommendations before publishing
Bulk operations — add tags, update categories, manage metadata across posts
Test the REST API first — before wasting time on configuration, verify you can reach /wp-json/ from your browser. Know your host’s security posture upfront; REST API blocks and Application Password restrictions are host-specific, not WordPress bugs. Use a staging site first if you have one. And always verify your system username exactly with whoami/echo %USERNAME% — configuration fails silently on path mismatches.