WordPress + AI series · Connector update · View all parts
Originally set up with Vibe AI in Part 1 — this is why I switched.
This series started by connecting WordPress to an AI assistant over MCP using the Vibe AI plugin. It worked, and it got the whole workflow off the ground. But as I leaned on it harder — drafting posts, uploading media, writing Yoast fields — the friction added up, and I eventually moved to a different WordPress MCP connector: the free easy-mcp-ai plugin. This is an honest account of why I switched, what actually changed, and where Vibe AI is still a perfectly reasonable choice.
This is a dogfooding update, not a takedown. Both plugins do the same core job — they expose your WordPress site to an MCP client so an AI tool can manage content. The difference is in how they do it, and which trade-offs you feel once you use one every day.
Where I started: Vibe AI
Vibe AI is a hosted MCP connector. Your site talks to it, and your AI client talks to it too, with the Vibe service sitting in the middle as a remote endpoint. Part 1 of this series walks through that exact setup, and I still think it is a fine on-ramp. The guided configuration is approachable, and you are connected within minutes.
For light, occasional use, none of what follows will bother you. The friction I ran into only showed up once the connector became part of a daily publishing routine.
The friction that built up
Three things slowly wore on me. First, rate limits: longer editing sessions would bump into usage ceilings, which is exactly when you least want to stop. Second, the remote session would expire mid-flow, and a previously working sequence of calls would suddenly start returning 403s until I re-authenticated. Third, some operations would simply hang and time out around the 300-second mark, turning a quick edit into a guessing game about whether the change had landed.
To be fair, one of the specific errors I hit was later fixed by the plugin’s maker — credit where it is due. But by the time the fix arrived, I had already gone looking for a connector with a different architecture, because the deeper issue was the hosted, in-the-middle model itself, not any single bug.
Why easy-mcp-ai became my WordPress MCP connector
easy-mcp-ai takes a different shape: it runs as a native plugin on the site itself and exposes a single MCP endpoint straight from WordPress. There is no third-party service holding a session in the middle. Your AI client connects directly to your own domain.
That architecture is the whole reason the switch stuck. It is free, has no rate limits, and is noticeably faster, because requests are not making an extra hop through a hosted broker. The plugin also exposes explicit, typed operations — separate tools for creating a post, updating meta, uploading media, and so on — instead of one generic pipe, which makes each call more predictable.
The practical result: longer sessions stopped hitting walls, the mysterious mid-session 403s disappeared, and edits that used to hang now return quickly. Nothing about the AI side changed — only the connector underneath it.
This is about the connector, not the AI
One point worth making, because it is easy to miss: the connector is independent of which assistant you point at it. MCP is a standard, so the same WordPress endpoint can serve whatever MCP-capable client you use — a cloud assistant, a local agent running on your own machine, or both at once.
In my own setup, the same easy-mcp-ai endpoint now answers to more than one client. That portability is a quiet but real benefit of a self-hosted connector: you are not tied to one vendor’s hosted bridge, and switching or adding an AI client does not mean reconfiguring your site.
Is Vibe AI still worth it?
Yes, for the right user. If you want the gentlest possible start, a guided setup, and you are not running heavy daily automation, Vibe AI is a legitimate choice — and its maker is clearly maintaining it. The series did not begin with it by accident.
easy-mcp-ai suits the other end of the spectrum: someone who wants a self-hosted, unlimited, faster connector and does not mind that it is a little more bare-bones. For a site I manage almost entirely through MCP, that fit was obvious. Your priorities decide which trade-off is the right one.
Conclusion
The Vibe AI setup from Part 1 still works, and I have left that article standing as the historical starting point. But the connector I actually run today is easy-mcp-ai, for three plain reasons: it is free, it has no rate limits, and it is faster because it lives on the site instead of behind a hosted broker. If you are choosing a WordPress MCP connector for serious, everyday use, that is the trade-off I would weigh first.
John Lock
Liked this? There's more where it came from.
Get our digest — articles worth your time, no spam, unsubscribe in one click.
Subscribe to Factnetize →
