Buildkite MCP server
MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors. Connect your AI agents to Buildkite with enterprise-grade governance, observability, and control through Mintive Gateway.
Tools included with Buildkite MCP
access_token
Get information about the current API access token including its scopes and UUID
create_build
Trigger a new build on a Buildkite pipeline for a specific commit and branch, with optional environment variables, me...
create_pipeline
Set up a new CI/CD pipeline in Buildkite with YAML configuration, repository connection, and cluster assignment
current_user
Get details about the user account that owns the API token, including name, email, avatar, and account creation date
get_artifact
Get detailed information about a specific artifact including its metadata, file size, SHA-1 hash, and download URL
get_build
Get detailed information about a specific build including its jobs, timing, and execution details
get_build_test_engine_runs
Get test engine runs data for a specific build in Buildkite. This can be used to look up Test Runs.
get_cluster
Get detailed information about a specific cluster including its name, description, default queue, and configuration
get_cluster_queue
Get detailed information about a specific queue including its key, description, dispatch status, and hosted agent con...
get_failed_executions
Get failed test executions for a specific test run in Buildkite Test Engine. Optionally get the expanded failure deta...
get_logs_info
Get metadata and statistics about the Parquet log file. 📊 RECOMMENDED as first step - check file size before reading ...
get_pipeline
Get detailed information about a specific pipeline including its configuration, steps, environment variables, and bui...
get_test
Get a specific test in Buildkite Test Engine. This provides additional metadata for failed test executions
get_test_run
Get a specific test run in Buildkite Test Engine
list_annotations
List all annotations for a build, including their context, style (success/info/warning/error), rendered HTML content,...
list_artifacts
List all artifacts for a build across all jobs, including file details, paths, sizes, MIME types, and download URLs
list_builds
List all builds for a pipeline with their status, commit information, and metadata
list_cluster_queues
List all queues in a cluster with their keys, descriptions, dispatch status, and agent configuration
list_clusters
List all clusters in an organization with their names, descriptions, default queues, and creation details
list_pipelines
List all pipelines in an organization with their basic details, build counts, and current status
Showing 20 of 28 tools
Works with every major client
Why Mintive gateway
Centralized governance
One-click deployment
OAuth + SSO enforcement
Host stdio servers on Mint instead of running locally
Observability and control
Enterprise hardening
Supports shared and per-user auth
Granular tool access control
FAQs
Yes. Mintive Gateway is SOC 2 compliant and uses OAuth-based authentication for all Buildkite MCP interactions.
ChatGPT, Claude, Claude Code, and any MCP-compatible client.
Schedule a demo to receive Mintive Gateway credentials and configuration details for connecting your AI client to the Buildkite MCP Server.
The Model Context Protocol (MCP) is an open standard that lets AI models connect to external tools and data sources through a single, secure interface—the "USB-C for AI."
Access is managed centrally in Mintive Gateway. Administrators can grant, suspend, or revoke connections and control authentication through identity-based policies.
Mint provides usage dashboards and audit logs for monitoring authentication, tool invocations, and connection activity.
No. Mint supports OAuth authentication and delegated token marshalling, allowing secure, automatic credential handling without manual entry.
Yes. Integrate Mint with Okta or another identity provider to enable role-based access. Map teams or groups to Virtual MCPs (VMCPs) for structured permissions.
Yes. Teams can define VMCPs with custom tool prompts, configurations, and behavior tailored to their workflows.
Yes. You can bring your own MCP servers and manage them through Mint with governance and security controls.
Create a Mintive app in Okta, upload the metadata XML, map groups to roles, and verify the connection.
Mint detects and notifies administrators of changes to tool definitions and descriptions, including new tools, renamed tools, removals, and updates to metadata.
Yes. Each invocation is logged with timestamp, user identity, and client metadata for traceable auditing.