MCP server
What closes itOne npx away
npx @respira/wordpress-mcp-server, a token, and your agent has the site.
Already building with AI
Add WordPress to the stack you already build with.
Your agent writes code, opens PRs and moves tickets. The one thing it cannot do is edit the WordPress site safely. That is the piece this fills.
- An MCP server
- it composes with the others you run
- 250+ tools and abilities
- on every core plan
- 55 skills
- ready-made jobs you can run or edit
The part of the loop that used to break
You type
Update the hero on the shop page: bigger headline, green CTA, add the trust badge.
- 1Reads the page through Respira and sees the builder's own structure
- 2Writes the new section in that builder's format, on a duplicate
- 3Returns a preview URL your agent can hand straight back to you
What you get
No copy-paste step, no "now go into wp-admin and do this bit by hand". The conversation does not break.
Respira is one server among several. Pull a frame from Figma, write it into WordPress, open the PR, close the ticket, in one pass.
Where the flow used to stop
- The agent writes WordPress code it cannot apply
- You copy-paste into a builder that reformats it
- Official tooling speaks blocks and nothing else
- The site is the one surface outside the loop
What closes it
- The agent writes to the site directly, on a duplicate
- Native output for 17 builders, not pasted HTML
- Snapshots and approvals, so speed does not mean risk
- Composes with your other MCP servers in one instruction
Everything on this page ships today.
Builder-native writes
It emits Divi modules and Elementor widgets, not a div soup the builder refuses to open.
Idempotent writes
Send the same call id twice on a flaky connection and the second one replays the first result instead of writing twice.
Async jobs
Queue a long operation and poll it, so a big pass does not die on a proxy timeout.
Skills
55 packaged jobs, from an SEO sweep to a Divi migration, that you can read and change.
Rollback
Every write snapshotted, 90 days, per page or per session.
The MCP server
The WordPress MCP that speaks your page builder.
One npx away, then your agent has the site: the tool catalog, both transports, and the builder layer that makes the output native instead of pasted.
- Works with Claude Code, Cursor, Windsurf, ChatGPT and the browser clients
- Composes with the other servers you already run
- Idempotent writes and async jobs, for the calls that should not be repeated or rushed
The CLI
For the parts you would rather script than say.
The WordPress CLI for the agent era. Same safety model, no chat window, and it belongs in the places a conversation does not: CI, migrations, a loop over thirty sites.
- Scriptable access to the same tools the agent calls
- Sensible in CI, where a chat window is not
- The same snapshots and the same approvals underneath
Each of these has a page of its own.
What it costs
Maker is €9 a month for one site, Builder €19 a month for five. The trial is 7 days and takes no card.
The questions people actually ask
Which clients does it work with?
Anything that speaks MCP: Claude Code, Claude Desktop, Cursor, Windsurf, ChatGPT, and the browser clients through WebMCP.
Does it fight my other MCP servers?
No. It is one server among several, and the interesting instructions are the ones that cross them: read a Figma frame, write the section, open the PR.
What stops an agent doing something stupid at 2am?
Duplicate-before-edit by default, snapshots on every write with 90 days of rollback, an approval queue, and site memory rules the plugin enforces regardless of which agent is asking.
Is the output really native?
Yes, and it is the whole point. The page opens in the builder afterwards and edits like a page somebody built by hand.
