How Buildprint works
Buildprint connects AI tools like ChatGPT, Claude, and Cursor to your Bubble app so you can debug, explore, and modify your app using natural language.
What Buildprint does
Buildprint gives AI assistants read-only access to your Bubble app's:
Logs: Search for errors, workflow runs, or API calls.
Database: Query tables, inspect schemas, or find records.
Workflows: Understand how features work or trace logic paths.
You can also use async AI agents to make changes like updating database fields or creating workflows. Buildprint warns you to test changes in a dev environment first.
How it works
Buildprint uses Model Context Protocol (MCP) to bridge your AI client and your Bubble app. When you ask a question, the AI queries Buildprint's API, which retrieves data from Bubble via the collaborator permissions you granted.
Your AI credentials (ChatGPT/Claude tokens) are encrypted and stored in Buildprint's database. Your Bubble app's database data is never stored - Buildprint fetches it on demand.
Buildprint is read-only by default. AI agents can suggest or make changes only if you explicitly enable them.
Key concepts
Workspaces: Organize your team and Bubble projects.
Projects: Each connected Bubble app is a project.
MCP servers: Personal endpoints that link AI clients to your projects.
Async agents: Background tasks that run AI queries or modifications.
What Buildprint doesn't do
Buildprint is in free beta and doesn't guarantee behavior or uptime. It won't:
Automatically modify your live app without your approval.
Store your Bubble database state.
Replace manual testing or version control.
Always test AI-generated changes. Buildprint disclaims liability for errors or data loss.
Use cases
Debugging: "Find all checkout errors in the last 24 hours."
Database exploration: "What tables power the onboarding flow?"
Workflow explanations: "How does the payment workflow work?"
Documentation: Generate schema docs or workflow diagrams.