Get the plugin
WP MCP/Integrations/Custom fields

Custom fields integration

MCP for JetEngine

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.

plugin-data-readplugin-data-write

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

Just ask.

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 real calls.

wpmcp, jetengine

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

Frequently asked

Questions, answered.

How do I turn writes on?

With the wpmcp_enable_jetengine_write filter, the same opt-in posture as ACF and Meta Box.

Point your AI at JetEngine.

Release notes, straight to your inbox.

One email per release, what shipped, what's verified, what's production-only. No drip campaigns. Unsubscribe in one click.