Connect via MCP

Buildprint MCP lets you connect a supported AI client such as Cursor, Claude Code, Claude, OpenCode, or ChatGPT to your Buildprint workspace so the client can use Buildprint's read-only MCP tools against your Bubble apps.

Before you start

• Connect your Bubble app to Buildprint and complete ownership verification first. See Connecting your Bubble app.

• Make sure the Buildprint collaborator has the Bubble permissions you want Buildprint to read.

• Use an AI client that supports remote HTTP MCP servers, connectors, or apps.

• Treat your MCP server URL like a secret. Anyone with the URL can use that server until you revoke it.

Create your MCP server URL

1. In Buildprint, open Integrations > MCP.

2. Click Create MCP server.

3. Choose whether the server should access all projects in the workspace or only selected projects.

4. Copy the generated MCP server URL.

The MCP server URL is workspace-specific and scoped to the projects you selected when you created it. Create separate URLs if you want different scopes or want to revoke one client without affecting another.

Install it in your AI client

Cursor

Use Buildprint's Add to Cursor button from the MCP dialog, or follow Cursor's MCP install guide and paste your generated HTTP MCP server URL.

Claude Code

Run this command in your terminal, replacing YOUR_MCP_SERVER_URL with the URL you copied from Buildprint:

claude mcp add --transport http buildprint YOUR_MCP_SERVER_URL

If Claude Code does not pick it up immediately, restart the app and check Claude Code's MCP docs.

Claude, OpenCode, ChatGPT, and other clients

Paste the generated MCP server URL into the client's MCP, connectors, or apps settings. If the client asks for JSON config, use:

{
  "mcpServers": {
    "buildprint": {
      "type": "http",
      "url": "YOUR_MCP_SERVER_URL"
    }
  }
}

Reference docs: Claude, OpenCode, ChatGPT.

What Buildprint MCP is good for

• Searching Buildprint docs and project metadata.

• Inspecting Bubble app structure, versions, logs, and synced data through Buildprint's MCP tools.

• Debugging issues, understanding workflows, comparing versions, and investigating production problems without opening Bubble manually.

Current limitations

• No editing via personal MCP servers: the MCP servers created from Agent -> Integrations -> MCP are currently read-only.

• No official setup support for third-party MCP clients: we do not offer hands-on support for configuring Cursor, Claude, ChatGPT, OpenCode, or other client-side MCP installations.

• No guarantees: Buildprint is beta software. We do not guarantee uptime, stability, compatibility, or behavior for Buildprint itself or for any third-party MCP client.

• Project scope still applies: the MCP server can only access the projects selected when the token was created.

• Bubble permissions still apply: Buildprint cannot exceed the collaborator permissions granted in Bubble.

• Sensitive values remain protected: Buildprint does not expose Bubble private API connector values or plugin secrets through MCP.

Troubleshooting

• The server works for some apps but not others: make sure the project is included in the token scope and that ownership verification is complete.

• Logs or data tools fail: check the Bubble collaborator permissions for logs, data, and version access.

• Your client cannot add the server: some clients do not support remote HTTP MCP servers, or their install flow may have changed. Follow the latest client docs linked above.

• You need to remove access: revoke the MCP server from Agent -> Integrations -> MCP and create a new one.

Related guides: Permissions and data safety, Support guidelines.