Works with SAR · beta
Crocoblock's dynamic content plugin: custom post types, Custom Content Types, relations and options pages. With SAR, ChatGPT or Claude can work with JetEngine on your site: drafts first, and your approval before anything goes live.
A few of the tools it uses, with what each one needs from you.
Add an item to a JetEngine Custom Content Type (beta) through JetEngine's own item handler, which runs its own checks and hooks: values by field name, each checked by its field's type (as wordpress_get_cct_item or wordpress_jetengine_overview describe them).
Change fields of one Custom Content Type item, or its status (publish or draft), through JetEngine's own item handler (beta).
Link or unlink items through a JetEngine relation (beta), with JetEngine's own relation calls: mode replace (the object's links become exactly ids; [] removes all), add or remove, on side children (object_id is the parent) or parents (object_id is the child).
What this site's JetEngine defines (beta): its active modules, post types and taxonomies with their meta fields, Custom Content Types (with item counts), relations (parent and child objects such as posts::product or cct::agents, one_to_one / one_to_many / many_to_many), Query Builder queries, options pages (storage default or separate) and meta boxes, each field with its type, label and options; and whether JetEngine's own MCP server is on (an AI connection outside SAR's approvals and undo: mention it to the user).
The items of one JetEngine Custom Content Type (beta), newest first, masked on the site like form entries: names as first name and initial, emails and phones shortened, addresses left out, free text with emails and phones hidden; option values, switches, numbers, dates and media ids as they are.
One Custom Content Type item, masked as in wordpress_list_cct_items, with the type's fields described (type, options, what each takes) and its wp-admin link.
Copy one into ChatGPT or Claude and fill in the brackets.
What does JetEngine define on this site: post types, Custom Content Types, relations and options pages?
List the latest [10] items of the CCT [content type] and tell me which have empty fields.
Change the [field] of the [content type] item [item] to [value]; I'll approve it in SAR.
Link the [post] to these [items] through the relation [relation name], and show me the links first.
No password to hand over.
Add the SAR Intelligence plugin to the WordPress site where JetEngine is active.
In SAR, add the site under Connections and approve it on WordPress's own screen. Allow changes when you are ready.
Add SAR to ChatGPT or Claude and ask in your own words, or start from a prompt above.
Tested prompts for whole jobs.
The tools that come with JetEngine, as your AI app sees them.
| Tool | What it does | Reads or changes | Approval | Status |
|---|---|---|---|---|
wordpress_jetengine_overviewJetEngine overview | What this site's JetEngine defines (beta): its active modules, post types and taxonomies with their meta fields, Custom Content Types (with item counts), relations (parent and child objects such as posts::product or cct::agents, one_to_one / one_to_many / many_to_many), Query Builder queries, options pages (storage default or separate) and meta boxes, each field with its type, label and options; and whether JetEngine's own MCP server is on (an AI connection outside SAR's approvals and undo: mention it to the user).Needs: JetEngine | Reads | None | Beta |
wordpress_list_cct_itemsJetEngine CCT items | The items of one JetEngine Custom Content Type (beta), newest first, masked on the site like form entries: names as first name and initial, emails and phones shortened, addresses left out, free text with emails and phones hidden; option values, switches, numbers, dates and media ids as they are.Needs: JetEngine | Reads | None | Beta |
wordpress_get_cct_itemA JetEngine CCT item | One Custom Content Type item, masked as in wordpress_list_cct_items, with the type's fields described (type, options, what each takes) and its wp-admin link.Needs: JetEngine | Reads | None | Beta |
wordpress_create_cct_itemNew JetEngine CCT item | Add an item to a JetEngine Custom Content Type (beta) through JetEngine's own item handler, which runs its own checks and hooks: values by field name, each checked by its field's type (as wordpress_get_cct_item or wordpress_jetengine_overview describe them).Needs: JetEngine | Changes | Depends on the change | Beta |
wordpress_update_cct_itemChange a JetEngine CCT item | Change fields of one Custom Content Type item, or its status (publish or draft), through JetEngine's own item handler (beta).Needs: JetEngine | Changes | Approval | Beta |
wordpress_get_related_itemsJetEngine related items | The items one object is linked to through a JetEngine relation (beta): side children (object_id is the parent, the default) or parents (object_id is the child), with post and term titles; a user is shown by id only.Needs: JetEngine | Reads | None | Beta |
wordpress_set_relation_linksChange JetEngine relation links | Link or unlink items through a JetEngine relation (beta), with JetEngine's own relation calls: mode replace (the object's links become exactly ids; [] removes all), add or remove, on side children (object_id is the parent) or parents (object_id is the child).Needs: JetEngine | Changes | Approval | Beta |
wordpress_get_jetengine_optionsA JetEngine options page | One JetEngine options page (beta): its fields (type, label, options, what each takes), how it stores them (default: one option for the page; separate: an option per field) and their values, secrets hidden and addresses masked.Needs: JetEngine | Reads | None | Beta |
wordpress_update_jetengine_optionsChange a JetEngine options page | Change values of a JetEngine options page (beta) through the page's own save, in either storage mode: each value checked by its field's type; fields left out keep theirs; fields named like secrets (keys, tokens, passwords) are never changed.Needs: JetEngine | Changes | Approval | Beta |
wordpress_get_post_metaCustom fields of a post | Every custom field (post meta) of a post, page or product, with secrets hidden, and which SAR may change. | Reads | None | Beta |
wordpress_set_post_metaSet a custom field | Set or delete one custom field of a post, page or product. | Changes | Approval once live | Beta |
Beta: tested against a stand-in for this product, not yet on a real site.
Install the plugin, add SAR to your AI and ask your first question within minutes. No card needed.