respira · one builder, twelve page builders
the page renders. or it does not.
i'm Mihai. i build Respira from Brașov, alone. it gives coding agents safe, structured access to live WordPress sites across twelve page builders. this page is a synthetic lab exercising every Divi 5 module the simplified-settings layer touches.
three things respira refuses to compromise on
privacy first
telemetry collects metadata only. never prompts, never tool arguments, never your content. opt out with one env var.
builder native
edits land in Divi, Elementor, Bricks, WPBakery, Beaver, Oxygen, Brizy, Breakdance, Thrive, Visual Composer, Gutenberg, Uncode.
dogfooded first
every release is run on the Respira Studio environment before the tag is cut. if a tool surprises you, the founder has already seen the surprise.
respira reads, writes, snapshots
respira talks to your WordPress install over the REST API. it detects the active page builder, parses the native format, and writes edits that the builder can re-render. every destructive operation goes through a snapshot. nothing is poked in wp_postmeta behind your back.
- read once, write once, snapshot always
- twelve builders, one mental model
- privacy is a hard line, not a courtesy
stop pasting shortcodes by hand
install the plugin, paste a token, point your agent at the site. respira does the rest.
respira, by the numbers
%
page builders supported
%
Divi 5 modules registered
%
people on the team
pricing, plainly
Free
for tryingMaker
for shippingrules of engagement
- always run get_builder_info before structural edits
- always snapshot before destructive ops
- never write to wp_postmeta directly
- always pass site_id per call in multi-site
three values, three tabs
respira collects telemetry as metadata only. site UUID, plugin version, builder names, agent type, write counts, locale. never prompts. never tool arguments. never tool results. never WordPress content. never customer URLs without explicit opt-in.
edits land in the page builder's native format. parseable by the builder, reversible by the snapshot system. never a wall of opaque code that breaks the visual editor.
aggregate numbers are exact. per-client numbers are defensible approximations from tool-call attribution. never invented precision. show the work when asked.
FAQ
is this safe for production sites?
yes. every destructive op routes through a snapshot. you can roll back in one click from the WordPress admin.
which page builders are supported?
twelve. Divi, Elementor, Bricks, WPBakery, Beaver Builder, Oxygen, Brizy, Breakdance, Thrive Architect, Visual Composer, Gutenberg, Uncode. each with its own native format adapter.
can i opt out of telemetry?
RESPIRA_USAGE_OPT_OUT=1 in your wp-config and collection stops at the source. no setting in the dashboard to bypass.
do agents need API keys?
yes. each agent is provisioned a scoped key from your WordPress admin. revocable per agent, per device.
what shipped recently
plugin v7.0.36
multisite-aware site detection. divi 5 inline schemas for the top 10 modules. approval-token round-trip on every delete.
MCP server v6.14.2
conservative block registration. divi5_mode auto-flip when payload contains native divi/* blocks.
install in one line
$ npx -y @respira/wordpress-mcp-server \ --install-config \ --client claude-code \ --install-token
respira · Brașov · mihai@respira.press · the breath continues