WIP: MCP-created component is available in Bricks but missing from Gutenberg despite “Use in block editor” being enabled

Bugs
1

Environment

  • Bricks: 2.4 Beta

  • Bricks Abilities: 1.0.0

  • MCP Adapter: 0.5.0

  • WordPress: 7.0.1

  • Website: Staging environment

  • Component ID: 352188

Description

We created a simple Bricks component through the Bricks MCP/Abilities API.

The component contains:

  • One Image element

  • One connected Image property

  • Block editor support enabled

  • Block category set to media

  • Block icon configured

  • Block preview image configured

The component is available and editable inside the Bricks component library. However, it does not appear as a block in the WordPress/Gutenberg block inserter.

Other existing Bricks components, such as Video, Heading, Gallery, and Text with Image, appear correctly in Gutenberg.

Steps to reproduce

  1. Create a new component using the bricks/create-component MCP ability.

  2. Add one Image element and connect an Image component property.

  3. Enable “Use in block editor”.

  4. Configure the block category, icon, and preview image.

  5. Save the component.

  6. Open or reload a post in the WordPress block editor.

  7. Search for the component in the block inserter.

  8. Rename and re-save the component in the Bricks Builder.

  9. Reload Gutenberg again.

Expected result

The component should appear in the Gutenberg block inserter and be insertable like the other enabled Bricks components.

Actual result

The component exists and works inside Bricks but does not appear in the Gutenberg block inserter.

Renaming the component, saving it again, and fully reloading Gutenberg does not resolve the issue.

Technical findings

We verified that the component is correctly included in the data sent to Gutenberg:

  • blockEditor is set to 1.

  • enabledComponentIds contains 352188.

  • allowedBlockTypes contains bricks-components/352188.

  • A server-side block definition for bricks-components/352188 is generated.

  • The complete component definition, properties, category, icon, and preview image are present in bricksGutenbergData.

  • No Bricks-specific registration error appears in the browser console.

Despite this, the block is missing from the inserter.

A custom allowed_block_types_all filter exists on the site. However, the resulting Gutenberg configuration explicitly contains bricks-components/352188, so the component is not being excluded by the allowlist.

Possible cause

The MCP-created component received the numeric-only ID:

352188

All Bricks components that work correctly in Gutenberg currently have six-character alphabetic IDs, for example:

sbemvx
gmqabx
yzzvkn
rnqcid

This suggests that the Gutenberg component registration may not correctly handle numeric-only component IDs generated through the MCP ability.

Additional note

The component was also renamed and manually re-saved inside Bricks after creation. This did not change its internal ID and did not make it appear in Gutenberg.

3

Hi Simon,
Thanks so much for your report!

I reproduced the issue and added it to our bug tracker.
We’ll update this thread once it’s fixed.

Best regards,
timmse

1 Like