Command Center Overview

The Command Center dashboard can be found by following the WordPress Dashboard > Crocoblock > Command Center path.

Before accessing the Command Center itself, an OpenAI API key should be added. This key can be created in the OpenAI account settings. 

The API key will be stored as an encrypted string, so it can’t be retrieved directly from the database.

Once the API key is pasted, the “Set API Key” button should be clicked to proceed to the Command Center itself.

After the Command Center opens, one will see the chat window and additional settings on the side.

The additional information that helps the AI agent perform more accurately can be added in the Add Context section. The available options are: “Add JetEngine Configuration Context,” “Add Website Configuration Context,” and “Add Allowed Macros Context.”

Clicking any option opens a corresponding settings pop-up.

JetEngine Configuration Context

If the “Add JetEngine Configuration Context” option is clicked, the relevant JetEngine structures can be specified in the pop-up. 

By default, the AI agent has access to all the available JetEngine content: 

• Post Types; 
• Taxonomies; 
• Meta Boxes; 
• Options Pages; 
• Query Builder;
• Relations; 
• Custom Content Types; 
• Rest API Endpoints; 
• Glossaries.

Some of the options can be deactivated if not needed.

Once the required options are selected, the changes can be saved by pressing the “Provide Selected Context” button.

Website Configuration Context

Clicking the “Add Website Configuration Context” option opens a pop-up where the relevant website-level content can be specified. 

By default, the AI agent has access to the following: 

• Post Types; 
• Taxonomies; 
• Plugins.

Some of the options can be deactivated if not needed.

Once all the required options are selected, the changes can be saved by pressing the “Provide Selected Context” button.

Allowed Macros Context

Pressing the “Add Allowed Macros Context” option opens a pop-up that allows defining which macros the AI agent is allowed to use.

Below the Add Context section, the Registered Tools/Resources can be found. By clicking each of them, their descriptions and the parameter list are opened.

Each pop-up displays the technical specification of an AI tool: its purpose and required parameters. This information is used by the AI agent to call JetEngine functions with valid arguments and create or modify site structures.

Add Custom Post Type

The Add Custom Content Type tool can be used to register a new Custom Content Type. 

All required parameters can be reviewed in the pop-up.

Get JetEngine Configuration

The Get JetEngine Configuration resource allows retrieving an overview of JetEngine configuration in a JSON format. It provides information about post types, taxonomies, meta boxes, options pages, queries, relations, Custom Content Types, REST API endpoints, and glossaries.

Specific configuration parts can be selected for retrieval.

Get Website Config

The Get Website Config resource can be used to retrieve information about the website’s configuration in JSON format. Details such as registered post types, taxonomies, and active plugins can be requested, with the available configuration sections indicated in the pop-up.

Get JetEngine Macros

The Get JetEngine Macros resource can be used to retrieve all available JetEngine macros, including their arguments and usage examples, for AI-assisted tooling.

Add Glossary

The Add Glossary tool can be used to register a new JetEngine glossary with manually provided options. At least one field object containing both a value and a label must be provided.

Manage JetEngine Modules

The Manage JetEngine Modules tool can be used to list active JetEngine modules or to activate/deactivate them.

Add Listing Grid Item

The Add Listing Grid Item tool can be used to create a JetEngine Listing Item linked to an existing Query Builder query. The tool analyses the query results (posts, terms, users, comments) and generates a starter layout that matches the detected data context.

Add Custom Post Type

The Add Custom Post Type tool registers a new Custom Post Type (CPT). The post type name should be provided inside “general_settings.name”. The slug will be generated from the name if it is omitted.

Additional settings such as labels, advanced options, meta fields, and admin columns can be configured as needed.

Add Meta Box

The Add Meta Box tool can be used to create a JetEngine Meta Box with custom fields. The “general_settings.name” should always be provided, and the fields in “meta_fields” described. 

When configuration options imply visibility rules, the required conditions are enabled automatically.

Add Taxonomy

The Add Taxonomy tool registers a new taxonomy in JetEngine. The taxonomy name should be defined in “general_settings.name” and attached to one or more post types via “general_settings.object_type”.

Optional labels, advanced settings, and term meta fields can also be configured.

Add Query

The Add Query tool registers a new Query for the Query Builder and returns data in a standardized format. 

For “query_type”: “sql”, “query_args” must contain a non-empty SQL string. For other types, “query_args” must contain the appropriate query arguments (“WP_Query-style” for posts, terms, users, etc.). 

This tool shouldn’t be called if “query_args” cannot be provided. The missing details should be specified first. 

Valid examples:

 SQL: {“name”:”Recent orders”,”query_type”:”sql”,”query_args”:{“sql”:”SELECT * FROM wp_posts WHERE post_type=’shop_order’ LIMIT 10″}}. Posts: {“name”:”Latest posts”,”query_type”:”posts”,”query_args”:{“post_type”:”post”,”posts_per_page”:5}} 

Invalid example (will be rejected):

{“name”:”Latest posts”,”query_type”:”posts”} ← missing query_args. 

Macros supported: 

Macros from the conversation context should be used for contextual params (IDs, user, dates). Macros should be put everywhere possible to make queries dynamic.

Next, one can select the language model from the corresponding dropdown field. The chosen model affects both the quality of responses and the cost of usage.

By default, the “gpt-5-mini” model is set, as it has proven to be optimal in terms of price-quality ratio. Changing the model triggers an automatic clearing of all previous context (not the visual chat history in the window, but specifically the context stored on the OpenAI side).

The “Save & Clear Context” button next to the language model dropdown saves the chat but clears the set context.

The “Reset API connection” button deletes the API key (resets the Command Center to its initial state).

The garbage bin-shaped button deletes the context and the conversation.

As an example, we enter the “Create a glossary of property types: townhouses, houses, garages, duplex, apartments.” request in the chat textarea and press “Send Message”.

After the request is processed, the result is shown. As we have asked the AI agent to create a glossary, it shows the following result:

“Tool Result: tool-add-glossary

{

  "success": true,

  "item_id": 21,

  "glossary_settings_url": "https://ld.crocoblock.com/documentation/wp-admin/admin.php?page=jet-engine#glossaries",

  "notices": []

}

I created a manual glossary named "Property types" with the property-type entries you requested.

What I did

Added a glossary titled: Property types

Added these entries:

value: townhouses — label: Townhouses

value: houses — label: Houses

value: garages — label: Garages

value: duplex — label: Duplex

value: apartments — label: Apartments

Details and next steps

The glossary was created successfully (ID: 21).

You can use these glossary values in listings, meta fields, filters, and forms that accept glossary sources.

If you want a different default selection, different labels, or additional entries (e.g., "studio", "penthouse"), tell me which changes you want and I’ll update it.

If you’d like, I can now:

Add this glossary as a field source in a specific form or listing,

Create a filter or dropdown using these options,

Edit any label or set a default checked item.

Tell me which next action you prefer, or request edits to the glossary.”

If needed, further adjustments can be added by asking the agent with the proper request.

Now, the glossary can be checked in the WordPress Dashboard > JetEngine > Glossaries directory.

The agent mentioned the glossary with the ID “21”, and it now appears in the Glossaries list.

The Name is set to “Property Types”, Data Source to “Set items manually,” and the needed options are added to the glossary.

If one of the items is opened, its settings can be checked: Field Value, Field Label, and Is checked (selected). 

These settings can be changed right in this directory if needed. If any changes are made, the “Save” button should be clicked to save them.

Also, check our How to Use MCP Server with VS Code + GitHub Copilot to find out more about allowing external AI applications to connect to your WordPress website.