Installation and authentication

The buildprint CLI gives agents a local editing workspace for Bubble app logic. It works best alongside the Buildprint MCP server: use the CLI for app files, checks, sync, and apply; use MCP tools for runtime data, logs, workload metrics, and hosted Bubble tooling.

Install the CLI

Install the global CLI with npm:

npm install -g buildprint
buildprint --version

To check for a newer version later:

buildprint update --check
buildprint update

If your shell still runs an older binary after updating, restart the terminal or run hash -r.

Create a CLI token

In Buildprint, open Agent > Integrations > CLI and generate a CLI token. You can scope the token to specific projects.

Treat this token like a password. It grants access to the projects in scope and can edit the associated Bubble apps when the app permissions allow Buildprint to edit. Do not paste it into public chats, commit it to a repo, or share it with someone else.

Link the CLI

Link the CLI once on each machine:

buildprint link <token>

A successful link verifies the token, stores local auth for the Buildprint API, and prints the projects the token can access.

Two quick checks:

buildprint project list
buildprint docs buildprint "getting started"

If either command returns an auth error, generate a fresh token and run buildprint link <token> again.

Start from the playbook

After linking, print the local agent playbook:

buildprint quickstart

It summarizes the workspace layout, the usual sync -> edit -> check -> apply loop, and the command conventions agents should follow.

Install the MCP server in an AI client

Buildprint MCP complements the CLI. Install it into a supported local client with:

buildprint mcp install --client codex

Supported client selectors are cursor, codex, claude-code, claude-desktop, opencode, and all. Useful flags:

• --client <clients> selects one or more clients, for example cursor,codex.

• --dry-run previews config files without creating a token or writing files.

• --json prints machine-readable install details.

• --name <serverName> changes the MCP server name. The default is buildprint.

• --token <token> uses an existing MCP bearer token instead of creating a new one.

Example:

buildprint mcp install --client cursor,codex --dry-run

Login as a Bubble user for browser tests

buildprint login creates run-as-user cookies for Agent Browser. Run it inside a branch workspace, or pass the app and branch explicitly:

buildprint login [email protected]
buildprint login [email protected] --app my-app --branch test
buildprint login [email protected] --app my-app --version test --session my-app
buildprint login [email protected] --no-browser

By default the command tries to install cookies into agent-browser. If that fails, it prints the exact fallback agent-browser cookies set commands.