Configuration

Every setting has a Bud and a Bloom form. Set only the product you use.

Variable	Meaning
BUD_URL, BLOOM_URL	Instance URL. Alone, it fixes where browser sign-in goes.
BUD_TOKEN, BLOOM_TOKEN	An access token of the instance. Valid for its lifetime only, 30 minutes by default; not renewed.
BUD_EMAIL + BUD_PASSWORD, BLOOM_EMAIL + BLOOM_PASSWORD	Sign in lazily through the instance’s /api/auth/login. Both must be set.
BUD_PROFILE, BLOOM_PROFILE	The browser sign-in profile to use; otherwise the default profile.

Precedence: a token wins over an email and password, which win over browser sign-in. While a token or password is set for a product, its auth_login tool returns an error. Setting only one of email and password stops the server with an error.

# browser sign-in to fixed URLs (recommended)
BUD_URL=https://bud.example.com
BLOOM_URL=https://bloom.example.com

Tool behaviour worth knowing

• Every tool carries a title and readOnlyHint; tools that change data also carry destructiveHint, true for updates and deletes.
• bloom_projects_create takes a prefix of exactly three letters; Bloom builds IDs such as PRJ-REQ-001 from it.
• Path segments such as project_ref, kind_slug, doc_id_str and identifier are validated: an empty value, . or .. returns an error without a request.
• bud_artifacts_get_content pages text artifacts with offset and max_bytes (default 65536, at most 1048576) and returns next_offset; binary artifacts return metadata only.
• Every request carries User-Agent: embedlabs-mcp/<version>, so the instance’s audit log shows which calls came from MCP.