How to Publish & Manage Blog Posts on WordPress Using MCP Express

WordPress MCP allows you to publish and manage blog posts by typing a request to an AI client instead of clicking around the dashboard. You connect your site once with an application password, and from there, a tool like Claude can create drafts, edit posts, and hit publish directly through the WordPress REST API.

This guide explains what MCP is in a WordPress context and walks you through a full WordPress MCP setup so you can manage your blog in a single conversation. If you’re already building out an AI-assisted WordPress stack, this tool fits right into it.

Quick Summary

MCP, short for Model Context Protocol, is an open standard that lets AI clients talk to outside tools and data. Applied to WordPress, an MCP server sits between your AI client and your site’s REST API. It takes a plain-language request, like “publish my latest draft,” and turns it into a real API call.

Setup always begins with a WordPress application password. From there, you connect a WordPress MCP server, either self-hosted or through a managed platform, then link your AI client to it. Once connected, you can publish and manage posts without touching the dashboard.

What Is MCP in the WordPress Context?

MCP is short for Model Context Protocol. Anthropic released it as an open standard for linking AI models to external tools, data sources, and applications. You can read the full spec in Anthropic’s docs for MCP.

In a WordPress context, MCP works as a bridge with two parts:

• MCP client: the AI tool you talk to, like Claude.
• MCP server: a service that receives your request, converts it into a call to the WordPress REST API, and returns the result.

When you say, “Create a post about our new feature and publish it,” the MCP server turns that into a POST request to your site’s /wp/v2/posts endpoint. There is nothing exotic going on. This is the same REST API that powers the block editor and hundreds of plugins. MCP simply provides an AI client with an organized, permission-aware way to call it.

Before we get into the details, note that WordPress itself does not ship an MCP server. What we have is a suite of separate tools, some open source, some hosted, that connect to the REST API in their own way. 

As a worked example, we will use the hosted WordPress MCP server, MCP Express, because it is quick to set up and requires no terminal. If you want to run the server yourself, there are other tools like InstaWP’s mcp-wp and Rnaga’s wp-mcp that are self-hosted.

What You Can Do with WordPress MCP

When you’re connected, you can do more than write. The same connection handles the entire lifecycle of a post. And this is where WordPress MCP earns its place in a daily workflow. It also fits naturally with the kind of tasks people already hand to AI tools inside WordPress.

Here’s what the connection covers:

• Publishing: draft a new post from a prompt and publish it, or save it as a draft for review.
• Editing: pull up an existing post and change a heading, a paragraph, or the whole body.
• Reading: Ask for your latest post, or fetch a specific one by its slug.
• Managing: update or delete posts without opening the editor.

The pattern is the same across all of these. You describe what you want in plain language, the AI client reads or writes through the REST API, and you confirm the result. Managing WordPress using MCP turns a series of dashboard clicks into a single sentence. That’s the core appeal of WordPress MCP for anyone publishing often.

What You Need Before You Start

Three things:

• An AI client. Claude works through both the web app and the desktop app. This guide uses Claude.
• An MCP server or platform. We’ll use MCP Express, since it’s free to start and needs no local setup.
• Your WordPress details. Your site URL, your username, and an application password (we generate this in Step 1).

Estimated time: about five minutes from signup to your first working request.

How to Set Up WordPress MCP: Step by Step

The exact screens differ between WordPress MCP tools, but the overall flow, application password, connecting a server, and linking your client are the same everywhere.

Step 1: Generate an Application Password in WordPress

The application password is what allows the MCP server to authenticate without using your real login.

1. Log in to your WordPress dashboard.
2. Go to Users > Profile.
3. Scroll to the Application Passwords section.
4. Enter a name, like “wordpressmcp,” so you can identify it later.
5. Click Add Application Password.
6. Copy the generated password right away. WordPress only shows it once.

If this is a live site, create a separate user with editor permissions and generate the password under that account. That way the connection can only do what an editor can do, not everything an admin can.

For more on this feature, WordPress.org has full documentation on application passwords.

Step 2: Create an MCP Server and Add the WordPress Tool

Sign up at MCP Express and open your dashboard. The free tier is enough to follow along and needs no card.

Create a new MCP server, give it a name and a brief description, then go to Add a Tool and search for WordPress. Select it.

Step 3: Enter Your Connection Details

On the WordPress connection screen, fill in three fields:

• Base URL: your site address, like https://yoursite.com/
• Username: the WordPress username tied to your application password
• Password: the application password you copied in Step 1, not your normal login password

Step 4: Choose Which Actions to Allow

This step decides what the AI can actually do on your site. For full publishing and management, enable these six:

• List Posts
• Get Post by Slug
• Create Post
• Update Post
• Publish Post
• Delete Post

If you’d rather keep the AI read-only or draft-only, leave Publish Post and Delete Post switched off. You stay in control of exactly what’s permitted.

Give the tool a clear name and description so the AI understands what it’s for, then create it.

Step 5: Connect Your AI Client

Now link Claude to your MCP server.

1. In Claude, open Settings > Connectors.
2. Click Add, then Add Custom Connector.
3. Set the URL to your MCP Express gateway endpoint.
4. Claude redirects you to MCP Express to complete the OAuth login. Grant access and pick the server you just built.

MCP Express has a detailed OAuth walkthrough if you get stuck on this step. Once it’s connected, you can reach your site from any device where you’re signed in to Claude: laptop, phone, or tablet.

How to Publish a Blog Post Using MCP

Publishing is a conversation when the connection is live. A typical request is like this:

“Write a post called ‘Our Summer Update’ with a short intro about the features we shipped.” Publish it.“

Claude drafts the post through the Create Post action, then publishes it through Publish Post, all without you opening the editor. You can ask it to revise a paragraph first, or save it as a draft instead of publishing, just by saying so.

This works well for straightforward drafting. It isn’t a replacement for editorial review. Read what gets published before it goes live, the same way you’d check anything before it ships.

How to Manage Existing Posts with MCP

Managing WordPress using MCP goes beyond writing new content. With the same six actions enabled, you can:

• Edit: Get my post with the slug ‘summer-update‘ and change the intro to mention the new pricing.
• Audit: “List my last ten posts and tell me which ones haven’t been updated this year.”
• Clean up: “Delete the draft titled ‘Old Test Post.'”

There’s also a Test Tools area in MCP Express where you can manually run any action and see the raw result before trusting it in a real conversation. It’s a handy way to verify a tool is working as expected, publish a post, build a test page, and see the output without going through the AI client first.

Security Best Practices When Using MCP with WordPress

A WordPress MCP connection has write access to your site, which is powerful, so make sure you lock it down properly. Our topic team covers this in more depth in our WordPress security guidance, but the essentials for MCP are:

• Use a dedicated editor-level account for the connection, not your admin login.
• Store the application password securely. It works like a real credential.
• Run your site over HTTPS. WordPress disables application passwords on non-HTTPS sites by default.
• Enable only the actions you need. If the AI never has to delete posts, leave Delete Post off.
• Test new workflows on a staging copy before pointing MCP at production.
• Revoke the application password the moment you stop using a server or client.

Related Guides

• Connecting Claude to WordPress with MCP: A Setup Guide
• 10 Things You Can Automate on WordPress with MCP

Key Takeaways

• WordPress MCP connects an AI client to your site’s REST API via an MCP server, authenticated with an application password.
• Setup takes five steps: generate the password, create a server, enter connection details, select allowed actions, and connect your AI client.
• Enable List, Get, Create, Update, Publish, and Delete posts to have full control to publish and manage.
• All publishing, editing, reading, and deleting of posts works through plain-language WordPress MCP requests.
• Security is based on a limited-permission account, HTTPS, and only enabling the actions you really need.

Conclusion

WordPress MCP turns publishing and content management into something you type a request to do, not something you click through menus to do. It’s the same setup where it matters: generate an application password, connect a server, link your AI client, and test before you depend on it. Once it’s live, running your blog isn’t about keeping up with the dashboard; it’s a conversation.

It gets more complicated when you need to pick the right server, scope permissions correctly, and maintain security, especially across client sites or at scale. If you’re struggling to automate tasks with your WordPress MCP setup, contact us, and we’ll help you build a smoother, safer workflow.

FAQs

What is MCP WordPress?

MCP-WordPress connects an AI client, such as Claude, to a WordPress site using Model Context Protocol. The MCP server acts as a bridge, translating requests in plain language into real REST API actions like creating or publishing a post.

What is WordPress MCP?

WordPress MCP is the same idea, but reversed: applying the Model Context Protocol to WordPress specifically, so an AI client can publish, edit, and manage content without you using wp-admin directly.

What is MCP in a WordPress context?

In a WordPress context, MCP is the connecting layer between an AI client and your site’s REST API. MCP Server authenticates using an application password and translates your requests into API calls.

What is MCP in WordPress?

It’s the standard that lets an AI tool operate your site. Instead of writing custom integrations for the REST API, an MCP server already handles the translation, so your AI client can read, create, and update posts.

How do I use WordPress MCP?

Generate a WordPress application password under Users > Profile, connect an MCP server such as MCP Express, enter your site details, enable the post actions you want, then link your AI client and test it with a simple request before real publishing.

Is MCP WordPress Integration Safe and Secure?

Yes, MCP WordPress integration can be safe and secure when it is implemented with proper authentication and strict permission controls. MCP itself does not provide unlimited access to your website. Instead, it allows AI clients like Claude or ChatGPT to interact with WordPress through an MCP server with defined permissions.