Terminal commands

bud and bloom come with a global install and work without an MCP client.

Sign in

bud auth login --url https://bud.example.com
bloom auth login --url https://bloom.example.com

The command prints a link and a request code, opens the browser and waits until you approve or deny. --no-browser only prints the link. --code uses code mode where the operator enabled it. No token or code is ever passed as an argument.

bud auth login --url https://bud.client.example.com --profile client
bud auth status
bud auth profile list
bud auth profile default client
bud auth logout --profile client

Run a tool

Every resource tool is a command: its name without the product prefix, split at underscores. Input fields are options with hyphens for underscores.

bud runs list --limit 5
bud runs stats --days 7 --suite smoke
bloom requirements get --requirement-id 12
bloom docs get by ref --project-ref PRJ --kind-slug requirements --doc-id-str PRJ-REQ-001
bud runs stats --help

Numbers and booleans are parsed; object and array fields take JSON; --input <file> or --input - gives the whole input as a JSON object. The tool’s input schema checks the input before a request is sent. Results print as JSON; errors go to standard error with exit code 1.

In CI

BUD_URL=https://bud.example.com BUD_TOKEN="$BUD_TOKEN" bud runs stats --days 1 > stats.json

A token works for its lifetime only (30 minutes by default), which suits a single CI job.