AI-Ready Plugin API for GrapesJS

[lexoyo]

Hello

I think it could be useful if GrapesJS had a simple API for plugins to expose their features to AI, so website builders could hook into them and expose them through MCP or other external integrations.

It could be inspired by the WordPress Abilities API - basically one more Backbone-style collection like editor.Abilities.

I'm considering contributing code for this. Do you have any advice or ideas?

@artf would you be open to a PR in that direction?

[GoodPHP]

Yes, nice idea for GrapesJS project

[artf]

That's a good idea @lexoyo, but I think instead of creating new APIs it could be more beneficial to have a simple set of commands defined for that scope in a plugin, eg.

editor.Commands.add('ai:addPage', (e, _, opts) => {
  editor.Pages.add({ name: opts.name, component: opts.html });
});

[lexoyo]

Thanks for the reply

I agree that commands are the right execution layer. My idea is not to replace them, but to add a thin discovery layer on top.

MCP is basically about letting AI agents discover and call tools automatically. For that to work well, tools need at least:

• a clear description (when to use it)
• defined inputs
• a way to list what’s available

Commands handle execution, but they don’t provide structured discovery or metadata by default.

So what I’m proposing is closer to:

• keep using commands internally
• add a simple, standardized way for plugins to declare which commands are “AI-exposed” and describe how they should be used

Would that approach make more sense?

[lexoyo]

here i did a proof of concept as a plugin:
https://github.com/silexlabs/grapesjs-ai-capabilities

i'd be happy to contribute it to the core as i believe AI and nocode are one and the same nowadays :)