Understand Flowmo’s WordPress connection, read-only discovery, ACF/layout inspection, field comparison, and guarded change workflow—and distinguish the in-product Agent tools from the standalone f0 MCP tool list.
Where: Open a website project with its WordPress connection configured, then use the Flowmo AI Assistant’s WordPress/CMS tools. — Ask to inspect a connected WordPress site or compare a mapped field.
Before you start
- Use the website project that owns the WordPress connection; the tools are project-scoped.
- The connected account must have the appropriate WordPress permissions. Full layout reads and ACF catalog access may require the Flowmo companion, administrator authority, or a current compatible plugin.
- This article describes the registered in-product Agent tools. The standalone f0 MCP server’s current tools/list does not include the wp_* declarations; check your client’s discovered tools before assuming external MCP access.
Key ideas
- Connection checks do not reveal secrets: wp_get_connection checks the existing project connection and authenticated read health. It does not return passwords or create a WordPress site.
- Capability discovery is read-only: wp_discover_capabilities reports available REST resources and support for ACF, blocks, widgets, the Abilities API, or the Flowmo companion. wp_discover_atomic inspects installed Atomic schemas and import limits; neither installs or changes site content.
- Read the exact target before comparing: wp_list_resources discovers paginated entries; wp_read_resource reads one exact entry and its available editable schema; wp_read_layout reads recursive block and Elementor widget instances plus revision hashes when the companion supports them. Missing or unsupported data remains unknown rather than being guessed.
- Comparison is advisory; plans are bound to exact state: wp_compare compares explicitly mapped local CMS fields with an exact remote target. wp_plan_changes creates one exact ACF, block, or widget operation bound to the revision hash returned by the read. Planning does not modify the site.
- Remote apply is isolated and gated: wp_apply_changes accepts only a previously returned actor/project-bound plan, only when the server is configured for an isolated nonproduction installation. Production applies are disabled. Use an idempotency key and inspect state after an uncertain outcome.
Steps
- In the connected website project, check the existing connection with wp_get_connection; never paste credentials into a prompt or expect this tool to create a site.
- Call wp_discover_capabilities and, when working with Atomic, wp_discover_atomic to learn what the specific installation supports.
- Read the needed ACF schema or exact post/layout using wp_read_acf_catalog, wp_list_resources, wp_read_resource, or wp_read_layout. Preserve returned IDs and revision hashes.
- Use wp_compare with explicit collection, entry, target, and field mappings to review differences. Treat the result as advisory, not as a sync operation.
- If a change is needed and supported, create one wp_plan_changes operation using the exact latest document hash and target instance. Review the proposed patch before applying.
- Apply only through wp_apply_changes when the configured target is an isolated nonproduction site. Reuse the idempotency key for a known retry; if the outcome is unknown, read the target again before doing anything else.
- If using an external MCP client, confirm that its tools/list actually contains the wp_* tools; do not infer availability from this Help Center article or the in-product Assistant.
WordPress tool map
- wp_get_connection — inspect the project connection and authenticated read health.
- wp_discover_capabilities — discover supported REST, ACF, block, widget, and companion features.
- wp_discover_atomic — read installed Elementor Core Atomic schemas and import constraints.
- wp_read_acf_catalog — read accessible ACF group/field schemas and registered PRO field types; it never reads entry values or registers fields.
- wp_list_resources / wp_read_resource / wp_read_layout — list entries, inspect one entry, and inspect exact recursive layout instances.
- wp_compare — advisory comparison of explicitly mapped local and remote fields.
- wp_plan_changes — prepare exactly one hash-bound ACF/block/widget patch; no remote write occurs.
- wp_apply_changes — apply a previously approved plan only to an isolated nonproduction site; production is disabled.
Standalone MCP availability
The f0 MCP server currently publishes dashboard workspace tools and the generated Flowgen tool catalog. These wp_* Agent declarations are registered in the in-product Flowmo AI Assistant, but are not currently included in the standalone f0 MCP server’s tools/list. Help search/indexing documents the capability; it does not make an absent MCP tool callable. A connected host should verify with its own tool discovery.