Custom fields integration
JetEngine AI agent tool reference
JetEngine keeps field definitions in its own registry and post field values as ordinary post meta under the field name. WP MCP exposes both on the plugin-data pair: jetengine-list-fields returns the fields for a post type from JetEngine's registry (layout entries and HTML-only fields skipped), jetengine-get-fields reads a post's values, and jetengine-update-fields writes them. Only keys that are fields of the post's type are read or written, never arbitrary meta. Writes are off until a site opts in, and each one is snapshotted on the post.
JetEngine in plain language: JetEngine MCP.
In practice
How JetEngine work goes with an agent.
JetEngine defines fields in its own registry, through meta boxes and the post types it creates, and stores each value as ordinary post meta under the field name, with checkbox and repeater values held as arrays. WP MCP asks that registry for the fields of a post type, so an agent sees real field names and types before it touches data. Reads and writes are then limited to those fields, never arbitrary meta, and a write that names an unknown field is refused with the list of valid ones.
What JetEngine fields does the Property post type have?
Runs jetengine-list-fields with post_type property. It returns each field's name, title and type from JetEngine's registry, skipping layout entries and html fields, which hold no value. It is a read.
Show me every JetEngine value on post 55.
Runs jetengine-get-fields with only post_id. With no keys given, it reads every value field of the post's type, and a field that has never been saved comes back null.
Set price to 450000 and features to pool and garage on post 55.
Runs jetengine-update-fields after the post is snapshotted. Keys must be fields of the post's type, or the call is refused as unknown_field and nothing is written. It stays disabled until wpmcp_enable_jetengine_write is on.
Change the intro banner on post 55.
If that field is an html type, jetengine-update-fields refuses it as field_not_writable, because it only renders markup and holds no value. Nothing is changed, so there is nothing to undo.
What your AI can do
Real JetEngine operations, every write reversible.
- List JetEngine fields for any post type
- Read a post's JetEngine field values
- Write field values (opt-in), snapshotted and reversible
- Refuse keys that are not fields of the post type
Example prompts
Example JetEngine prompts.
What JetEngine fields does the Property post type have?
Read the price and bedrooms fields on listing 210.
Set the status field to "sold" on these five listings.
Under the hood
The JetEngine calls, under the hood.
plugin-data-read({ operation: "jetengine-list-fields", args: { post_type: "property" } })
plugin-data-write({ operation: "jetengine-update-fields", args: { post_id: 210, fields: { status: "sold" } } }), opt-in; snapshotted
Safety and access
What can be undone on JetEngine, and what costs what.
Recoverable on JetEngine
- jetengine-update-fields snapshots the post, and rollback-operation restores its meta exactly.
- A refused write, whether for an unknown field or an html field, creates no snapshot, since nothing was changed.
JetEngine limits and opt-ins
- Writes are off until a site enables the wpmcp_enable_jetengine_write filter.
- Values are not checked against the field type. Send the shape JetEngine stores, such as an array for a checkbox or a repeater.
- Only post type fields are covered. Listings, queries, relations and non-post data are not part of this integration.
Free or Pro: All three operations are free, on the free plugin-data dispatcher pair that also serves Pods and other plugins. There is no Pro-only operation for JetEngine. The one gate is the write opt-in, wpmcp_enable_jetengine_write, which is separate from the switches for ACF and Meta Box. Reading fields and values works without it.
In the free plugin
The JetEngine integration is in the free plugin.
The core JetEngine tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.
Frequently asked
JetEngine MCP: questions, answered.
In JetEngine, how do I turn writes on?
With the wpmcp_enable_jetengine_write filter, the same opt-in posture as ACF and Meta Box.
Does it include fields on JetEngine's own custom post types?
Yes. The field list comes from JetEngine's registry for the post type, which covers meta boxes attached to it as well as the fields of post types JetEngine itself registers. Ask for the post type slug.
What if JetEngine is deactivated?
The operations stay listed but answer jetengine_inactive, so an agent gets a clear reason rather than a fatal error. Reads and writes both wait until JetEngine is loaded again, and no data is touched in the meantime.
Can the JetEngine integration read or write taxonomy and user fields?
No. The operations take a post type and a post id, so only post fields are reachable. Term, user and options-page data in JetEngine are outside what this integration reads or writes.
How are repeater and checkbox values written?
They are saved as the value you send, through the standard post meta API. WP MCP does not convert them, so send the same structure JetEngine stores. Reading a populated post first with jetengine-get-fields shows the exact shape.
Is there an AI agent for JetEngine?
Yes, through WP MCP rather than JetEngine itself. An agent you choose, such as Claude or Cursor, can list JetEngine fields for any post type. WP MCP is a separate plugin, not a built-in AI feature of JetEngine. On the undo side: jetengine-update-fields snapshots the post, and rollback-operation restores its meta exactly.
Related integrations
More integrations for the same agent.
MCP for ACF & ACF Pro
FreeCustom fields, 5 tools.
MCP for Meta Box
FreeCustom fields, 5 tools.
MCP for Pods
FreeCustom fields, 2 tools.
MCP for Gravity Tables
FreeData tables, 3 tools.
MCP for Elementor
ProPage builders, 14 tools.
MCP for Gutenberg
FreePage builders, 4 tools.
Browse the full Integrations hub, or read more on JetEngine MCP and the WordPress MCP plugin.