A WordPress AI writer alternative — bring your own AI
The “AI for WordPress” plugin shelf is crowded — Jetpack AI, Yoast AI, Rank Math Content AI, AIomatic, Bertha, GetGenie, and a long tail behind them. They all install into wp-admin and put an AI button next to the post you’re editing. That’s a real workflow, and for a lot of people it’s the right one. This page lays out where it fits, where it doesn’t, and what a bring-your-own-AI alternative looks like.
What the plugin shelf is actually good at
Sitting inside the admin. That’s the honest pitch. You install the plugin, paste a key (or pay the vendor’s subscription), and there’s now a “write with AI” or “improve this paragraph” button in the Block Editor next to the post you’re already writing. For a non-technical writer who lives in wp-admin and just wants a generate-or-rewrite button in their composer, that’s a low-friction, defensible answer.
Some of these plugins are also good at narrow jobs: Yoast and Rank Math’s AI features are tuned for SEO titles and meta descriptions, Jetpack AI is integrated cleanly with the Block Editor, AIomatic and similar bulk-content plugins do automated posting from feeds. None of that is fake. If your workflow is “I’m in the editor, I want a button,” the shelf delivers.
Where the plugin shelf gets thin
It’s mostly closed-loop. Three things tend to bite once you try to use it for serious editorial work across a real site:
- Pay per article, often via the vendor’s model. Most plugins meter usage — credits, words per month, posts per month — on top of whatever you already pay for WordPress hosting and any other AI subscriptions. You end up paying twice for the same tokens.
- One model, no choice. The plugin picks the model. You don’t get to point Claude at it because you trust Claude’s writing more, or run a Gemini pass because it’s better at one specific job. You take what’s wired in.
- One post at a time, no view of the rest of the site. This is the real one. The AI button in the editor only sees the post that’s open. It has no idea what else is on the site, can’t cross-reference your other posts, can’t insert internal links to articles it doesn’t know exist, and can’t run a sweep across the archive. It writes in a vacuum.
The third point is why most “AI for WordPress” content reads the way it does — generic, untethered, vaguely on-topic. The model doesn’t have the rest of your site to ground itself in.
The alternative: bring your own AI to a folder
Specter takes the opposite approach. It’s a native macOS app that does two-way sync between WordPress and a folder of plain markdown files. It has no AI of its own and charges no per-article fees. Instead, it turns your entire site — every post and page — into .md files in a folder on your Mac. The AI you already use, whether that’s Claude, ChatGPT, Gemini, Copilot, or something local, can then read and edit the folder like any other set of text files.
That changes what AI does on your WordPress site in a few specific ways:
- The AI sees the whole site, not one post. Hand the folder to Claude and ask it to insert internal links to relevant articles — it can actually do that, because the relevant articles are sitting next to the one being edited. (Full Claude workflow here.)
- You pick the model. Any AI that can read files. Switch between them per job. Run a refresh pass with one, a tone pass with another.
- You pay your AI vendor once, not the AI vendor plus a plugin reseller. Specter is a flat $99/year. No per-article credits, no token markup.
- You edit existing posts as easily as new ones. (See use-AI-to-edit-posts.) Most plugins are tuned for generating new content; the folder model treats “improve the 400 posts you already have” as the natural case.
- You can run a sweep. Bulk operations across the archive — meta description refreshes, heading cleanup, taxonomy normalization — are trivial once content is a folder. (Bulk SEO guide.)
A human still reviews the diff before anything publishes. Specter’s dry-run preview shows exactly which posts will be created, updated, or flagged as a conflict before a single byte reaches your live site.
A fair comparison
| ”AI for WordPress” plugins | Specter | |
|---|---|---|
| Where it lives | In wp-admin, next to the post | Native Mac app + a folder + your AI |
| Which AI | The plugin’s chosen model | Any AI you bring |
| Scope per request | One post at a time | The whole site, as a folder |
| Pricing | Per-article credits or vendor sub | $99/year flat |
| New vs. existing posts | Mostly tuned for generation | Round-trips existing posts cleanly |
| Bulk operations | Rare, limited | Native — that’s the point |
| Best for | Non-technical writer in the editor | Operator improving an existing site at scale |
When each one wins
If you’re a solo writer or a small team that lives in the WordPress admin, doesn’t want a Mac in the loop, and just wants a generate-and-improve button inside the composer — the plugin shelf is genuinely easier. It puts AI where you already are, with no new app to install and no folder to manage.
If you have an existing site with content worth improving, you already pay for Claude or ChatGPT, you’d rather not stack another subscription, and you want AI that can see more than one post at a time — the bring-your-own-AI model wins. You stop paying twice for the same tokens, you stop accepting whatever model the plugin happened to wire in, and you get a workflow where the AI can actually reference the rest of your site instead of writing into a vacuum.
That’s the whole frame. The plugin shelf isn’t wrong; it’s just optimized for a different job. If you’ve outgrown one-post-at-a-time AI buttons, the alternative is a folder, your AI, and a sync that keeps WordPress honest.