Share this post using the buttons provided below:
A few months ago I watched a YouTube video from some German engineers showing how to connect Claude to WordPress with nothing more than a user account and an app password. It worked, and it cost me nothing extra. Then the official WordPress connectors for Claude arrived, and my setup stopped working.
This month I finally had time to pick it up again. This post is also the test. Claude is saving it into WordPress as a draft through the setup I describe below, and I will tell you at the end how it went.
Why I did not want another API bill
I spend most of my days building things for clients, so my own blog kept slipping down the list. When I finally had a moment to revisit my blogging plan, one rule was fixed: no extra API costs. The Claude API is billed by usage. I already pay for Claude, and I wanted the connection to work through the plan I have, not add a second bill on top.
So I searched online, browsed the WordPress plugin directory, and talked it through with Claude.
What I looked at before choosing
A few options came up. WP MCP Ultimate lives only on GitHub, and I could find no feedback from other users on whether it was any good. I also looked at WP Vibe and at an MCP plugin from ThemeIsle. Claude suggested a few more as well.
I picked Easy MCP AI for three reasons. It was easy to install. The plugin’s website explains the connection in detail. And it is free, with no price tiers that I could find. The plugin page on WordPress.org calls it a free WordPress MCP server plugin that includes all of its tools. It also says the plugin never calls an AI model itself, so it adds no AI bill of its own. One catch: if you plug in outside SEO tools such as Semrush or Ahrefs, you pay those providers through your own accounts.
How I connect Claude to WordPress
My old setup gave Claude a Contributor account on each of my sites, with an app password. Easy MCP AI needs at least the Author role, so I raised every Claude account to Author. The old app passwords did not work with the new method. I deleted them from my project notes and made fresh credentials for each site. They now live in a password manager and not in any file.
Then I installed Easy MCP AI on each site and followed the connection steps on the plugin’s website. Last, I opened the plugin settings on every site and switched on one option: Force draft on create. With that on, anything Claude creates is saved as a draft.

Why the limited account and the draft setting matter
I could have connected Claude with my admin login. That would give it access to everything the plugin can do, including deleting posts. A dedicated account with limited access is the safer choice.
In WordPress, an Author can write and edit their own posts, and by default can publish them too. That is why the draft setting matters. With it on, new posts are saved as drafts, and my instructions to Claude say it never publishes. I review everything and press publish myself.
The goal is not to hand the work over. The goal is to write faster and make publishing easier.
How this post was written
I did not type this from a blank page. Claude interviewed me by voice, ten questions, one at a time, and wrote from my answers. It works from a set of markdown files I have built about my business, my voice and my rules, so it stays close to what I would say. I ran a few small tests before this one. If you like seeing how I use Claude in my own work, I have written about building an automated Canva workflow with Claude and about catching outdated website copy with Claude.
What I check before I publish
Every draft goes through three checks. First, it has to pass the human test. It should read like I wrote it, and I give Claude a clear list of AI words and habits to stay away from. Second, it has to match what we agreed in the interview, with the structure I expect. If there are images, I check that they sit in the right place, are compressed, and have alt text. Third, the SEO has to be built in. I settle the focus keyword before we write anything, so it lands in the H1, the H2s and the image alt text. Doing that up front saves me a lot of time.
What to know before you connect Claude to WordPress
First, this exists. Developers in the Claude and WordPress communities build free tools like this one, and few corners of the internet work that way. Second, it is possible to connect Claude to WordPress without a separate API bill. Third, if the setup sounds too technical, ask a professional to do it. In my estimate it takes about two hours. If you would like help, you can book a free discovery call.
Why this is still my work
I am a functional dyslexic. Before AI, an article like this took me a couple of days. Now Claude understands my voice and works inside the files I have set up, so it stays true to my vision and my brand. That makes regular writing possible for me.
Artists have always worked this way once they reach a certain level. Michelangelo and da Vinci did not do everything themselves. They had assistants and apprentices under them, and they gave the instructions. I now have an AI assistant that I instruct to work inside limits I am comfortable with. I know from my record as a working creative what meets the expectations of a client and an audience, and I check the work against that before it goes out.
Just because it is AI does not mean it is not mine.
My verdict after the first draft
It works. I gave Claude the instructions, it wrote the post, and it saved it as a draft under the Claude AI account, with all the settings we had already put in place. All that was left for me to do was change the post’s author from Claude to myself, then read it through.
Claude went a step further than I expected. It told me a few things to be aware of, and it also flagged where its own assumptions had been wrong. The main one was Rank Math. Claude assumed the SEO integration was already switched on. It turns out I still need to enable that from a setting first, which I will try for the next round of posts. For this one, Claude handed me the Rank Math metadata directly: the focus keyword, the meta description and the post title. I just copied and pasted those into the Rank Math section myself.
What Claude did not do for me was the featured image or the screenshots inside the post. It did give me prompts with suggested graphics and suggested images, which sped up that part of the process.
All in all, I think this is an exceptional tool and a really cool workflow. If you are a single user with one website, it is pretty easy to set up and implement. For me, with several sites and a lot of technical builds and project files behind them, it took a little longer. But it was all done in the spirit of showing you that this is possible, and how to do it.
Feel free to have a look at Easy MCP AI for yourself, and drop a comment if you have questions. As mentioned earlier, I am available via a free discovery call if you would like to chat about getting this set up.
Share this post using the buttons provided below:


