Installation and authentication
Once installed, buildprint CLI includes everything you need to build on Bubble apps with AI agents. The MCP server includes resources to do things like review logs and data, whilst the CLI covers app logic.
As a result, Buildprint CLI should be used in collaboration with the MCP server for best results.
Installation
Install via npm using:
npm install -g buildprintGenerate a CLI authentication token
Go to Integrations → CLI.
Click "Generate CLI Token" and create a new CLI token. You can optionally scope it to specific projects.
This is a personal access token. It grants access to any projects in your workspace that you select, including full editing permission on the associated apps (if the collaboration settings on those apps permits Buildprint to edit). Do not share this token with anyone.
Link the CLI
Link your Buildprint CLI with your generated token:
buildprint link <token>A successfully verified token will prints the projects it can access.
Confirming the link worked
Two quick checks:
buildprint project list- will print the apps your token can access.buildprint docs buildprint "getting started"- should return search results from Buildprint's help center.
If either returns an authentication error, re-run buildprint link <token> with a fresh token.
Install MCP server
Buildprint CLI is designed to work with the Buildprint MCP server, not replace it. Your agent can install the Buildprint MCP server by using buildprint mcp install --client <client name>. buildprint mcp --help will provide the useful instructions. This feature comes with many common clients that can be auto-configured by Buildprint itself, but any MCP client is supported.