I’m just gonna post these as I come across them: “The MCP can’t fill a new attribute on existing options”
So it can create a new attribute but not add any value to the attribute if attempting to add a value to an attribute that already exists?
Have you tried feeding it a CSV file with ensuring existing display matches the original display? I could imagine it might be that the MCP may not have all data necessary to perform action on correct existing options.
Yes:
The available option-set write tools are:
- create_option_set — creates a set.
- create_option_attribute — adds an attribute.
- create_option — adds an option.
You can’t reorder them either.
Great, if its added we’ll start using it. Thank you!
One more:
Claude is complaining it can’t tick “Include errors in response and allow workflow actions to continue” for API calls
That’s a problem then since those should be ticked by default
Posted this in another thread but hoping someone sees it:
When I connect, the MCP gets access to every app on my account, not just the one I’m working on. I have 16 apps and only want the AI touching one of them. The manual’s only advice is to “name the app you mean in your prompt,” which isn’t a real safeguard. Right now I’m relying on a check I set up on my end that blocks calls to the other apps. It works, but I’d much rather Bubble enforced it.
What I’d love is for each app to have its own MCP connection, set up from that app’s settings. That connection would only work on that app and couldn’t see anything else on my account.
As it stands, one wrong app name, whether it’s the AI’s mistake or a typo in my prompt, is all it takes for it to make changes to an app I never meant it to touch
Being able to access all apps is necessary if you want to prompt “make a mobile app from my web app.”
Are you theorycrafting or have you actually experienced problems with this? From my experience frontier models (Opus 5.5 especially) just “get it.”
I haven’t had an actual problem with it, but I don’t think a safeguard should depend on whether something has already gone wrong. Opus 5.5 is very good, but an instruction in a prompt can still get lost in a long session/large context. A scoped connection means it doesn’t matter if that happens
We should have a choice: let me scope a connection to one app, or to a specific set of apps,
when that’s all I need. Anyone who wants account wide access can keep it.
I’ve been using it with Claude the last few days to refresh an internal app we made for leave booking, appraisals, time tracking, etc. - it is phenomenal. I am blown away with how capable it is, how it is able to intuit my intentions. It has spotted errors in our logic, redesigned the UI, improved security, suggested features… unbelievably good. thank you
@lindsay.esterman Small bug + fix (I reported to fede as well)
Another little quirk, the MCP can’t edit a searchbox’s search, so claude told me to delete a constraint manually
Hi, some feedback on the MCP sign-in (Claude Code as the client, mcp.bubble.io/mcp, public OAuth client).
Since about Oct 28 we have to re-authorize every morning. A refresh attempted after more than about 10 h without use now fails with invalid_grant (Invalid refresh_token): 3 of 3 attempts (after 10.9 h, 13.8 h and 14.4 h of inactivity), while refreshes within about 6 h still work. In our client-side logs, between Oct 7 and Oct 27 the same kind of refresh (after 10 to 27 h of inactivity) was never rejected (14 of 15 succeeded, none failed). So it looks like the refresh token lifetime or inactivity timeout was shortened around Oct 27-28.
Two questions: (1) is that intended? (2) could the refresh token stay valid longer, or use a sliding window renewed on each successful refresh?
A second, smaller point: refresh tokens seem to be single-use, so when two sessions of the same client refresh within seconds of each other, the second one is rejected and the client drops its stored login for everyone. A short grace period for the previous refresh token would make that much less disruptive.
Thanks!
Thanks! I’m sharing with the team so they are aware
Edit update: the team is working on pushing changes that should address this problems!
My MCP client uses a self-hosted CIMD document. It worked until about two days ago. Now every sign-in fails with:
{“error”:“invalid_client”,“error_description”:“Client metadata document at https:///client.json not accepted: its host is not one client metadata is accepted from”}
- The document hasn’t changed and is served correctly.
- Only a few domains pass the check (claude.ai, chatgpt.com, cursor.com, vscode.dev…).
- Token refresh fails with the same error, so existing connections are broken too.
Is this intended? If so, how can a third-party client get approved, either with a document hosted under mcp.bubble.io/oauth/clients/ or with our domain added to the list?
This is breaking a production integration.
Thanks!
This is the result of recent security work the team shipped. They are currently evaluating how to get back to a state where you can continue doing what you were doing
An absolute resounding round of applause. You may have well and truly changed my business’s trajectory with this. Building my ideas quicker than imaginable is not without deep appreciation. There’s one thing to have an idea in your own sector, but to have the ability to act on them so well and so quickly is something I cannot thank you enough for ![]()
Yeah it’s enough to give me psychosis.
Updating this thread linking to the latest news:
I cannot believe Bubble MCP has been here for a month now! The amount of work I’ve managed to get done in this time is *insane*
I’ve spent five years and over 5,000 hours building my app on Bubble (It’s large and complex). I’d planned to start beta testing in February 2027 with only some of the first-stage features ready. Now I’m on track to start next month, with all of them finished. Somewhere around 1 year’s worth of work in 1 month!
Before MCP I was screenshotting issues into ChatGPT over and over. It’s absolutely amazing now to just be able to say ‘go and have a look’.
Anyway, the point of this is to relay my appreciation and enthusiasm. Thank you thank you thank you Bubble for existing in the first place; as a non-coder with huge ambition you already gave me a way to create my dream, and now with MCP it’s like… supersonic.