MCP creating "broken" parameters

Follow-up to this topic.

Turns out this is a pretty easy fix on Bubble’s end.

The Bubble MCP writes API workflow parameters in a layout the editor can’t display. The MCP’s create_event and set_workflow_item_properties describe APIEvent parameters as {: {key, value, optional, is_list, in_url}}, so workflows built through it store {“attending”: {…}, “date”: {…}}.

The editor stores {“0”: {…}, “1”: {…}}. Its Parameters panel shows each name-keyed parameter as a blank card with an error mark.

The workflows run correctly and check_node_issues reports nothing. Please make the MCP write the editor’s layout (and correct the tool description), make the editor read or convert name-keyed lists (including the Schedule API workflow step and the Data tab’s Bulk dialog), and make the issue checks agree.

@fede.bubble

If only there was a way to let an agent speak Bubble fluently :joy:

Stop stunting on the rest of us George!!!

Side note it’s funny that Opus 5.5 just fixed the bug itself by rewriting everything correctly, so this is officially the first time Bubble doesn’t technically need to fix a bug because it can be fixed by the end user.

To be fair Buildprint went through these issues too

There’s a whole class of issues the issue checker won’t flag because it’s built to flag stuff the editor lets you build. It doesn’t flag [this invalid JSON] because prior to MCP/Buildprint, there was never really a case in which people would arbitrarily write JSON to an app, but now there is.

They can be nasty because if you get lazy and don’t check the editor, they lie there quietly

lol you should know by now he only posts if it’s about buildprint :laughing:

Have you submitted a bug report? I can ask the MCP team to pick it up from the queue. I’ll also flag this thread to them :+1:

Update here @randomanon, the MCP team is working on pushing a fix