Your WordPress, editable by your agents.
We deploy a WordPress MCP server on your infrastructure so your agents can read the whole site, draft and update posts, fix SEO metadata and upload media — with publishing behind your approval.
What our clients say
Four artifacts, not a slide deck
Everything is deployed on your side and stays yours — including the source.
A running MCP server
Connected to your site through the WordPress REST API with application passwords, deployed on your infrastructure and versioned in your repository.
The tool set your agents call
Search, read and list on any post type; create and update posts, pages, SEO metadata, media and taxonomies — including the WPML and Yoast fields the default API leaves out.
The publish gate
Agents write drafts. Publishing is a separate, explicit permission, logged and reversible — so nothing reaches your readers without a human saying yes.
Playbooks that use it
Bulk metadata fixes, internal-link repairs and content refreshes turned into prompts your editors can run without touching the admin.
Two weeks, in three steps
Access, application passwords and a map of your post types, taxonomies and plugins. We connect read-only against a staging copy.
Tool set built around your actual content model, including the plugin fields that matter and the ones that must never be touched.
Draft writes enabled, publish gate configured, playbooks handed over and a working session with whoever runs the blog.
Four things. If you have them, we start this week.
This is the whole list. We ask for it up front so nobody spends a meeting finding out the project cannot start.
- A WordPress site with the REST API reachable and an admin who can issue application passwords
- A staging copy, or permission to work against drafts on production
- One person who knows which plugins own which fields
- A decision on who may publish, and whether an agent ever can
It pays for itself within 10 months, or we keep working for free.
We agree on the numbers the accelerator has to move before we start, and we measure them against your own site. If it has not paid for itself in ten months, we keep working on it at no extra cost until it does.
Questions we get before the first call
Can an agent publish to my live site by accident?
No. Agents write drafts by default and publishing is a separate permission. If you never grant it, nothing an agent writes reaches a reader without a person approving it.
Does it work with our page builder?
It works with what the REST API exposes, and we extend it for the fields your plugins own — including builders that store their layout as serialized data. We map that in week one, before writing anything.
What about multilingual sites?
WPML translation relationships are part of the field map. An agent that updates one language can be told to leave the others alone, or to keep them in sync — your call, made explicitly.
Should we just migrate off WordPress instead?
Sometimes. That is the WordPress → Astro accelerator, and the honest answer depends on your traffic, your plugins and your team. The diagnosis tells you which of the two is worth doing.
Want to see it against your own site?
A free diagnosis: we look at your content model and your plugins, tell you what an agent could and could not do with them, and you decide from there.
