Server instructions

On initialize, the server explains Bud and Bloom to the MCP client so the model selects the right tools.

EmbedLabs MCP connects to Bloom (PLM: requirements, test cases, suites, campaigns, defects, designs, risks, baselines and traceability) and Bud (test management: products, test runs, results, artifacts, the test catalog and Test Stations). All Bud and Bloom tools are available. Use bud_auth_login or bloom_auth_login, approve the browser link, then call the matching auth_complete tool. When BUD_URL or BLOOM_URL is set, sign-in goes to that instance; otherwise pass your instance URL. A token or an email and password in the environment take precedence. Bloom artefacts are addressed by numeric ID or by human document ID such as PRJ-REQ-001; bloom_search and bloom_docs_get_by_ref resolve a document ID. A Bud test run verifies Bloom requirements: bloom_requirements_link_test_run links a run to a requirement and bud_runs_publish_to_bloom sends a completed run’s report to Bloom. bud_runs_create, bud_runs_update and bud_results_create record CI runs. Bud accepts them only from a Test Station, so a signed-in user always gets a 403. Run known test cases as a custom run instead: find them with bud_catalog_list and queue them with bud_runs_trigger_custom. bud_artifacts_get_content returns text artifacts in pages of max_bytes from offset; check bud_artifacts_info first for size and content type.