Buildkite
MCPBuildkite runs the pipelines that build and ship your code. Antimetal reads builds and logs to find which one shipped the change behind a failure.
#What Antimetal does with Buildkite
- Read pipelines, builds, and job status
- Retrieve build logs for failed steps
- Find which build deployed a given change
- Check agent and queue health when builds stall
#Connecting Buildkite
-
Open Integrations in the Antimetal dashboard
Go to Integrations in the Antimetal dashboard and find Buildkite.
-
Authorize Antimetal in Buildkite
Click Connect and follow the prompt. Depending on the tool this is either an OAuth handoff or a read-only credential you generate in Buildkite and paste into Antimetal.
-
Confirm the connection
Once Buildkite shows as connected, Antimetal begins pulling from it during investigations. No further configuration is required.
#Permissions and access
Antimetal connects over MCP with read-only access and performs no write operations. The exact scopes depend on the credential you issue in the vendor tool — grant read access only.
All tenant data is processed in isolated environments. See security and compliance for details.
Contact us via Slack or at support@antimetal.com.
Related integrations
Search your codebase for the root cause.
Pipeline logs, flaky test detection, and config analysis.
Manage GitOps applications, syncs, and rollout status.