Respira 6.6.0
54 Advanced Custom Fields tools. Every field type, every ACF Pro surface, snapshot-backed, dry-run previewable, license-tier gated. Works on approximately 2 million WordPress sites that use ACF today.
What shipped
One new PHP class, one new MCP tool file, one detection hook, one data-driven dispatcher. No breaking changes, no migrations, no new infrastructure. If ACF is already installed on your site, every tool below is available the moment you upgrade.
Field operations
18 toolsReads and writes for every ACF field value. Plus field-group management: create, update, clone, export, import. Validation and search across the entire field definition surface.
acf_get_fieldacf_get_fieldsacf_update_fieldacf_update_fieldsacf_delete_fieldacf_list_field_groupsacf_get_field_groupacf_create_field_groupacf_update_field_groupacf_delete_field_groupacf_export_field_groupacf_import_field_groupacf_clone_field_groupacf_validate_fieldacf_get_field_objectacf_search_fieldsacf_bulk_get_fieldsacf_compare_fields ACF Pro: Repeaters, flexible content, galleries
18 toolsRow-level and layout-level ops for ACF Pro’s composable field types. Returns `PRO_FEATURE_REQUIRED` on free ACF installs with a remediation hint pointing at the tool the agent should use instead.
acf_get_repeateracf_get_repeater_rowacf_add_repeater_rowacf_update_repeater_rowacf_delete_repeater_rowacf_reorder_repeateracf_count_repeater_rowsacf_get_flexible_contentacf_get_flexible_layoutacf_add_flexible_layoutacf_update_flexible_layoutacf_delete_flexible_layoutacf_reorder_flexible_layoutsacf_get_galleryacf_update_galleryacf_add_to_galleryacf_remove_from_galleryacf_reorder_gallery ACF Pro: Options pages
8 toolsSite-wide settings stored on ACF options pages. Read a single option or all options. Bulk-update. Register a new options page at runtime.
acf_list_options_pagesacf_get_optionacf_get_optionsacf_update_optionacf_update_optionsacf_delete_optionacf_create_options_pageacf_export_options Relationships & post objects
6 toolsFollow relationships in either direction. The reverse-relationship tool answers "which posts point at me" in one call. User-profile ACF fields are first-class alongside post-scoped fields.
acf_get_relationshipacf_update_relationshipacf_get_reverse_relationshipsacf_get_post_objectacf_get_user_fieldacf_update_user_field Terms & bulk
4 toolsRead/write ACF fields on taxonomy terms. Copy field values between posts with `clone_fields`. Apply the same update across up to 500 posts with `bulk_update_fields` (requires Builder tier).
acf_get_term_fieldacf_update_term_fieldacf_clone_fieldsacf_bulk_update_fields Safety model
Every ACF write is wrapped with the same safety envelope Respira applies to every other builder-native tool. ACF is not a special case.
Snapshot before + after
Every write captures a before_edit and after_edit snapshot via the existing Respira snapshot engine. Roll back any ACF change with `respira_restore_snapshot`.
dry_run on every write
Pass `dry_run: true` to any ACF write tool and the response returns the intended change without touching the database. Agents can preview bulk updates before committing.
Per-tier scope gating
Reads on Lite, writes on Maker, bulk operations on Builder. The PHP handler enforces each gate independently; the backend issues the matching scope on the API key based on the user’s plan.
Audit log entry per call
Every invocation writes to `wp_respira_audit_log` with action, resource type, resource ID, and timestamp. Query the log to see exactly what the agent did.
Example workflows
Update a product spec sheet across 100 products
Agent reads all products matching a SKU pattern, diffs their spec_sheet ACF field against a single source of truth, then routes the 100 writes through `acf_bulk_update_fields` in a single call. Each product gets its own before/after snapshot. One approval entry covers the batch.
respira_acf_bulk_update_fields({
post_ids: product_ids,
fields: {
warranty_months: 24,
country_of_origin: 'Portugal'
}
}) Migrate a field group from staging to production
Export the full field group on staging, import it on production, verify by comparing a sample post’s values between the two sites. No WordPress admin needed.
// On staging
const group = await acf_export_field_group({ group_key: 'group_hero' })
// On production
await acf_import_field_group({ json: group })
// Verify
await acf_compare_fields({
post_id_a: 123, post_id_b: 456,
field_keys: ['hero_title', 'hero_subtitle']
}) Bulk update team bios from a CSV
Read the CSV locally via `respira exec`, then loop through user IDs calling `acf_update_user_field` with the new bios. Each update is audit-logged, so ops can trace the full set from the admin later.
for (const row of csv) {
await acf_update_user_field({
user_id: row.id,
field_key: 'user_bio',
value: row.bio
})
} License tiers
| Tier | ACF access |
|---|---|
| Anonymous | None. ACF tools require a connected site. |
| Lite | All ACF reads (get_field, list_field_groups, search_fields, compare_fields, etc.). |
| Maker | All reads plus single-post writes (update_field, update_fields, delete_field, add/update repeater rows, gallery edits, etc.). |
| Builder | Everything on Maker plus bulk operations (clone_fields, bulk_update_fields up to 500 posts at once). |
| Studio | Everything on Builder plus higher quotas and priority support. |
Upgrading
Respira v6.6.0 is an additive release. Upgrade in place from any 6.x version. No migrations run, no data is rewritten, no existing API key scopes change. ACF tools register themselves on the next request if ACF is installed and active on the site. Non-ACF sites see zero behavioural difference.
The MCP server (v6.6.0) and the WordPress plugin (v6.6.0) are versioned together. You do not need to downgrade the plugin to keep using an older MCP server \u2014 the plugin is backward compatible with every MCP release in the 6.x line.
What ships next
The v6.6 release lays the groundwork for the public tools catalog at respira.press/tools \u2014 a filterable index of all 234 Respira tools across 22 categories with license badges, safety indicators, and Abilities API comparison. The catalog page ships in the v6.6.x patch line; the catalog data itself is already generated and versioned with this release.
You're not the only one talking to WordPress.
The Respira community is where agency owners debug Divi migrations at 11pm, where vibe coders swap prompts that actually ship, and where the roadmap gets written out loud. Breathe with us.