Complete Guide: Connect WordPress to Claude Desktop with MCP

If you've been following my content automation journey, you know I've been raving about connecting WordPress directly to Claude AI. The time savings have been incredible - a 60% reduction in content creation time. But several people have asked for the actual technical setup guide.

So here it is: the complete, step-by-step guide I wish I had when I started. This is based on my real-world implementation, including all the mistakes I made and how to avoid them.

Fair warning: this is a technical guide. It requires SSH access and some command-line work. But if you've ever set up marketing automation in HubSpot or configured Zapier workflows, you can absolutely handle this.

What You'll Achieve

By the end of this guide, you'll be able to create and edit WordPress blog posts directly from Claude Desktop, upload and manage media files, manage pages and comments, and access your WordPress site from any computer where you're logged into Claude - all through natural language conversation.

Here's what that looks like in practice:

"Create a blog post about the top 5 marketing automation trends for 2025" - Claude creates a full blog post with proper formatting
"Upload this image and add it to my latest post" - Claude handles the entire media workflow
"List my 10 most recent blog posts" - Claude returns your actual posts with titles, dates, and status

Prerequisites

You'll need a WordPress site (self-hosted or managed hosting like Cloudways, Kinsta, or WP Engine), SSH access to your server, WordPress admin access for application passwords, Claude Desktop installed on your computer, and basic terminal/command-line knowledge.

I strongly recommend a Claude Pro account. This allows the MCP connection to work across all your devices automatically. You can technically do this without Pro, but the experience is significantly better with it.

Understanding Your Options

There are two main WordPress MCP solutions, and this confused me initially.

Option 1: Official WordPress MCP Adapter is moving into WordPress Core (version 6.9+). It's future-proof and actively maintained, based on the WordPress Abilities API. However, it's more complex to set up and has limited tools out of the box. Best for developers building custom abilities.

Option 2: Automattic WordPress MCP (Recommended) provides more tools immediately - posts, pages, media, comments, and more. It's easier to install and works great with Claude Desktop's remote proxy. The downside is it will eventually be deprecated in favor of the official adapter. But for content creators who want to start publishing right away, this is the way to go.

Based on real-world testing, I recommend the Automattic WordPress MCP. That's what this guide covers.

Step 1: Install the WordPress Plugin

SSH into your server and navigate to your WordPress plugins directory:

cd ~/applications/your-app-name/public_html/wp-content/plugins

Download the latest release:

wget https://github.com/Automattic/wordpress-mcp/releases/latest/download/wordpress-mcp.zip

Unzip and clean up:

unzip wordpress-mcp.zip
rm wordpress-mcp.zip

Alternatively, download from GitHub Releases and upload through Plugins > Add New > Upload Plugin in your WordPress admin.

After installation, activate the plugin in your WordPress dashboard.

Step 2: Create an Application Password

This is where most people get stuck, so pay close attention. You need an application password - NOT your regular WordPress login password.

Log into WordPress admin
Go to Users > Profile
Scroll to the Application Passwords section
Enter "Claude Desktop" as the password name
Click Add New Application Password
Copy the generated password immediately - it looks something like s9RO q2St 9lEV SESW B31p n7bP
Save it somewhere safe - you won't see it again

Here's where I made my first mistake: you need your actual WordPress login username, not your email address, not your display name, and not the application password name.

To find your username, go to Users > Profile and look for the Username field. If you're unsure, check via SSH:

cd ~/applications/your-app-name/public_html
wp user list --fields=user_login,user_email

Step 3: Configure Claude Desktop

Edit your Claude Desktop configuration file. On macOS:

nano ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows:

notepad %APPDATA%\Claude\claude_desktop_config.json

Use this template:

{
  "mcpServers": {
    "wordpress-site": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://yoursite.com/",
        "WP_API_USERNAME": "your-actual-username",
        "WP_API_PASSWORD": "your application password here"
      }
    }
  }
}

Replace the placeholders: your WordPress URL should include https:// and a trailing slash, use your login username from Step 2, and paste the application password you generated.

Save the file, then completely quit and restart Claude Desktop (Cmd+Q on Mac - don't just close the window).

Step 4: Test Your Connection

Open Claude Desktop and start a new conversation. Look for the MCP icon showing your WordPress server connection.

Test with: "List my 5 most recent blog posts." Claude should return your actual posts with titles, dates, and status.

Then try: "Create a draft blog post titled 'Testing MCP Connection' with a paragraph about how I successfully set up WordPress MCP integration with Claude Desktop."

Check your WordPress admin dashboard for the new draft. If it's there - congratulations, you're connected.

What You Can Do Now

Once connected, you have a full content management toolkit:

Posts: Create, edit, browse, search, and remove posts
Pages: Create, edit, and browse WordPress pages
Media: Upload images/videos/files, browse your library, and manage assets
Comments: View, moderate, and edit comments

You also get access to list_api_functions (discover all available WordPress REST API endpoints) and run_api_function (execute any WordPress REST API call directly).

Practical Workflow Examples

Creating a blog post: "Create a blog post titled '5 Marketing Automation Trends for 2025' with sections on AI-Powered Personalization, Predictive Analytics, Multi-Channel Orchestration, Privacy-First Marketing, and Conversational AI. Make it about 800 words with a professional but conversational tone."

Updating existing content: "Find my post titled 'Marketing Automation Trends' and add a new section at the end about implementing these trends with a 3-step action plan."

Bulk content management: "List all my draft posts from the last 30 days and tell me which ones are ready to publish based on content completeness."

Common Issues and Fixes

401 Error / "Not allowed" - Wrong username or password. Double-check you're using your login username, not email. Generate a fresh application password and update your config.

Environment variables not passed - Verify JSON syntax at jsonlint.com. Ensure the env section is at the same indentation level as command and args. Restart Claude Desktop completely.

Connection failed - Confirm the plugin is activated. Verify your URL includes https:// and a trailing slash. Check if your host's firewall is blocking the connection.

Tools not appearing - Check Claude Desktop logs at ~/Library/Logs/Claude/mcp*.log on macOS. Start a completely new conversation. Click the attachment icon to see available tools.

Troubleshooting Checklist

If things aren't working, go through this systematically: verify the plugin is installed and activated, confirm you generated an application password (not your regular one), make sure you're using the correct login username, validate your JSON syntax, verify your URL format, confirm Claude Desktop was fully restarted, start fresh conversations, check firewall settings, and verify the password was copied without extra spaces.

The Bigger Picture

This WordPress-Claude integration is one piece of what's becoming possible with Model Context Protocol. I've also connected Claude to Google Drive, my file system, and web search capabilities. Combined with my multi-agent AI stack, the ability to have all these tools communicating through natural language is transforming how I work.

For content creators, marketers, and anyone managing a WordPress site, this integration removes massive friction from the publishing process. You go from idea to published post without switching between a dozen applications.

Start small - get the connection working, create your first post, then gradually build more sophisticated workflows. That's exactly what I did, and three months later, I can't imagine going back to the old way of doing things.

This is also a foundational piece of the content systems I built throughout 2025 - infrastructure that compounds in value over time.

Edward Chalupa is a digital marketing specialist and founder of Whtnxt, a digital marketing and automation consultancy. Connect with him on LinkedIn or explore more at echalupa.com.