Hey there
I built a tool that lets you create an MCP server for your Bubble app.
Once your MCP is set up and you’ve added the endpoints you need, you get a server URL that you can plug directly into Claude or ChatGPT as a custom connector.
From there, you can query your Bubble app in natural language, directly from Claude or GPT.
Some use cases I’m currently exploring with this setup:
Data audits on existing Bubble apps to identify unused fields across multiple data types
Letting non-technical team members (like sales or ops) query client data and run simple analysis
Generating basic insights and graphs from app data without exporting anything
And if you want to understand how it works step by step, I wrote a full guide here
What’s next
The next step is to allow adding Bubble backend workflow endpoints, not just Data API endpoints.
This would make it possible for AI to trigger custom business logic.
Another idea I want to explore is using ChatKit on top of this MCP server, so your Bubble app itself can expose a chat-based UI to interact with custom workflows.
I believe that more and more products will offer chat-based interfaces, not as replacements for UIs, but as an additional layer on top of existing apps.
In that sense, chat becomes both:
a user-facing feature
and an API-like interface for interacting with your product
I’ll keep posting new features and tutorial on this!
But if you have already some use case, it would be great to hear how everybody else is planning to use it
I’ll be making tutorials next, after finishing this feature. Let me know your usecase or if you need some guidance, so I can write about it in the next tutorial!
Added a feature for giving the AI context of the Current User, which will be the bridge for making sure the AI agent respects the privacy rules attached to that user when asking it to retrieve data trigger actions
Next step is to build a demo using all this to build an experience like https://chatkit.world/ where the user can interact both with the UI and Chatkit to perform actions in the app
It’s very similar, but there are a few advantages to using an MCP.
With MCP, the multi-step logic is no longer handled inside Bubble, so you don’t need backend workflows to loop and manage tool calls.
This is because, instead of defining the tools in Bubble, the tools are defined in the MCP itself.
Another benefit is that once you have an MCP, you can connect it to other clients and platforms like ChatGPT or Claude (as connectors), OpenAI’s Agent Builder, etc., without changing your Bubble logic.
@design.agx Honestly, this is a real achievement considering how closed the Bubble ecosystem is. This is exactly what this company should be building, instead of improving their front.
You can set up which backend workflow from Bubble should be triggered when a click in a widget happens
You can also define the payload that it will send to!